cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
dkbollig
Frequent Visitor

Power App Component Framework with ArcGis Embed

Hey All

 

I have been working to see if I can create an embed of an arcgis map but I find I am having a hard time with typescript errors. For example when using the typescript library of arcgis-js-api it --  "Can't resolve 'esri/Maps'".  I have attached a standard html / javascript implementation example. 

 

https://codepen.io/dkbollig/pen/WNNyWzm?&editable=true&editors=100

 

Thanks for any help on this.

21 REPLIES 21

Many thanks Derek - it'd be great to have some code that we know "should" work!

Yes it all works very nicely in the npm test harness.

I've tried a public web map on arcgis.com, and a private map on our own IWA-secured portal. Again, both work in the test harness.

I haven't used codepen but will think about what I can share and how!

Does this code work in your situation?  @aventham77 

 

import { IInputs, IOutputs } from "./generated/ManifestTypes";
import DataSetInterfaces = ComponentFramework.PropertyHelper.DataSetApi;
import { any } from "prop-types";
import { watchFile } from "fs";
import { setDefaultOptions, loadModules } from "esri-loader";
import { METHODS } from "http";
type DataSet = ComponentFramework.PropertyTypes.DataSet;

export class TerritoryViewComponent
  implements ComponentFramework.StandardControl<IInputs, IOutputs> {
  private _context: ComponentFramework.Context<IInputs>;
  map: __esri.Map;
  mapView: __esri.MapView;
  private _mapContainer: HTMLDivElement;
  private _longitude: string;
  private _latitude: string;
  private contextObj: ComponentFramework.Context<IInputs>;

  /**
   * Empty constructor.
   */
  constructor() {}

  /**
   * Used to initialize the control instance. Controls can kick off remote server calls and other initialization actions here.
   * Data-set values are not initialized here, use updateView.
   * @param context The entire property bag available to control via Context Object; It contains values as set up by the customizer mapped to property names defined in the manifest, as well as utility functions.
   * @param notifyOutputChanged A callback method to alert the framework that the control has new outputs ready to be retrieved asynchronously.
   * @param state A piece of data that persists in one session for a single user. Can be set at any point in a controls life cycle by calling 'setControlState' in the Mode interface.
   * @param container If a control is marked control-type='standard', it will receive an empty div element within which it can render its content.
   */
  public init(
    context: ComponentFramework.Context<IInputs>,
    notifyOutputChanged: () => void,
    state: ComponentFramework.Dictionary,
    container: HTMLDivElement
  ) {
    // Add control initialization code
   
    this._mapContainer = document.createElement("div");
    this._mapContainer.setAttribute("id", "mapNode");
    this._mapContainer.setAttribute("style", "height:80vh;");

    container.append(this._mapContainer);

    this._context = context;
    this._context.parameters.dataSet.paging.setPageSize(10000);
  }

  private PageLoaded(context: ComponentFramework.Context<IInputs>): void {
    this._longitude = this._context.parameters.longitude.raw as string;
    this._latitude = this._context.parameters.latitude.raw as string;
    console.log("page loaded");
    console.log(typeof jQuery);

    if (context.parameters.dataSet.loading) {
      context.parameters.dataSet.paging.setPageSize(5000);
      console.log(context.parameters.dataSet.sortedRecordIds.length);
      return;
    }

    if (context.parameters.dataSet.paging.hasNextPage) {
      context.parameters.dataSet.paging.loadNextPage();
    } else {
      try {
        const options = {
          // tell Dojo where to load other packages
          dojoConfig: {
            async: true,
            isDebug: true,
            parseOnLoad: false,
            packages: [
              {
                name: "jquery",
                location:
                  "https://www.crmdynint.com/Scripts/jquery-2.1.1.js?v=1.3",
                main: "jquery-2.1.1",
              },
            ],
          },
        };
        setDefaultOptions({ css: true });
        loadModules(
          [
            "esri/Map",
            "esri/views/MapView",
            "esri/WebMap",
            "esri/layers/FeatureLayer",
            "esri/widgets/Search",
            "esri/widgets/Fullscreen",
            "esri/widgets/Legend",
            // "esri/widgets/TimeSlider",
            // "esri/views/layers/FeatureLayerView",
            // "esri/views/2d/layers/features/tileRenderers/SymbolTileRenderer",
            // "moment/moment",
            // "esri/support/arcadeUtils",
            "esri/widgets/LayerList",
            "esri/layers/GraphicsLayer",
            "esri/Graphic",
            "esri/PopupTemplate",
          ],
          options
        )
          .then(
            ([
              Map,
              MapView,
              WebMap,
              FeatureLayer,
              Search,
              Fullscreen,
              Legend,
              TimeSlider,
              LayerList,
              GraphicsLayer,
              Graphic,
              PopupTemplate,
            ]) => {
              // then we load a web map from an id

              // Paste the url into a browser's address bar to download and view the attributes
              // in the CSV file. These attributes include:
              // * mag - magnitude
              // * type - earthquake or other event such as nuclear test
              // * place - location of the event
              // * time - the time of the event
              var template = {
                title: "{NAME}",
              };

              var acretemplate = {
                title: "{NAME} , {STATE_NAME}",
                content: [
                  {
                    type: "fields",
                    fieldInfos: [
                      {
                        fieldName: "SUM_ACRES",
                        label: "Total Corn Acres",
                        format: {
                          digitSeparator: true,
                          places: 0,
                        },
                      },
                    ],
                  },
                ],
              };

              const dealerlabelClass = {
                // autocasts as new LabelClass()
                symbol: {
                  type: "text", // autocasts as new TextSymbol()
                  color: "black",
                  haloColor: "black",
                  font: {
                    // autocast as new Font()
                    family: "Playfair Display",
                    size: 10,
                    weight: "bold",
                  },
                },
                labelPlacement: "above-center",
                labelExpressionInfo: {
                  expression: "$feature.NAME",
                },
              };

              var corn_acres = new FeatureLayer({
                url:
                  "https://utility.arcgis.com/usrsvcs/servers/a3e76e21469940df8580dcc9fcb72dcd/rest/services/2018_Corn_Acres/FeatureServer",
                popupTemplate: acretemplate,
              });

              var map = new Map({
                basemap: "hybrid",
                layers: [corn_acres],
              });

              var view = new MapView({
                container: "mapNode",
                center: [263, 43],
                zoom: 6,
                map: map,
              });
              var legend = new Legend({
                view: view,
                layerInfos: [
                  {
                    layer: corn_acres,
                    title: "Corn Acres per Square Miles",
                  },
                ],
              });
              view.ui.add(legend, "bottom-left");
              var searchWidget = new Search({
                view: view,
              });

              view.ui.add(searchWidget, {
                position: "top-right",
              });

              var fullscreen = new Fullscreen({
                view: view,
              });
              view.ui.add(fullscreen, "top-right");

              var dataSet = context.parameters.dataSet;

              view.when(function () {
                var layerList = new LayerList({
                  view: view,
                });

                view.ui.add(layerList, "bottom-left");
              });
            }
          )
          .catch((err) => {
            // handle any errors
            console.error(err);
          });
      } catch {
        console.log;
      }
    }
  }

  /**
   * Called when any value in the property bag has changed. This includes field values, data-sets, global values such as container height and width, offline status, control metadata values such as label, visible, etc.
   * @param context The entire property bag available to control via Context Object; It contains values as set up by the customizer mapped to names defined in the manifest, as well as utility functions
   */
  public updateView(context: ComponentFramework.Context<IInputs>): void {
    // Add code to update control view
    this.PageLoaded(this._context);
  }

  /**
   * It is called by the framework prior to a control receiving new data.
   * @returns an object based on nomenclature defined in manifest, expecting object[s] for property marked as “bound” or “output”
   */
  public getOutputs(): IOutputs {
    return {};
  }

  /**
   * Called when the control is to be removed from the DOM tree. Controls should use this call for cleanup.
   * i.e. cancelling any pending remote calls, removing listeners, etc.
   */
  public destroy(): void {
    // Add code to cleanup control if necessary
  }
}

Hi @dkbollig - many thanks for sharing your code!

I'll definitely give this a whirl; I have a couple of questions though if you don't mind...

After an initial skim through, I'm not immediately clear on why you need to bring the jQuery package in - could you explain that?

Is this code working in an actual PowerApp? If so, hearty congratulations to you as that feels like a real breakthrough from where I'm sitting!

Did you find that basing the mapview on a webmap didn't work for you, or did you just switch to this approach out of preference?

Unfortunately, I'm having the same experience with the code you posted @dkbollig - it all runs well in the test harness, but when I import the built component and add it into an actual PowerApp, I just end up with an empty map object, with no layers loaded.

My suspicion is that some sort of security restriction is preventing the ESRI JS API from making any "fetch" requests.

Hey Andy

 

Would you be using a model driven app or a canvas app?

 

I have been using the model driven app for power apps.

 

Thanks Derek

Aha... I've been trying to create a canvas app.

Thanks for letting me know - I guess that's the clincher!

@dkbollig & @aventham77 - have you had success after all?
I'm working on a project where the customer requests integration of ESRI geolocation map within Dynamics and their Dynamics solution is not available anymore, so I wondered about the PCF route.

aventham77
Frequent Visitor

Hi @ZePowerDiver - I didn't make any big breakthroughs with my canvas app, but as I understand it, @dkbollig had the above code working in a model-driven app.

Hey all, I was wondering if any of you had any luck with this, it seems a shame for our org to have both AGOL licenses and M365 but not be able to use the api in our apps.  

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (2,513)