Latest Contributions by MichaelSnook

I have a simple event layer table attached to road routes and we are using branch versioning/feature services for editing.  When an edit is made to the event table generally the event layers update correctly.  When we save edits, the event layer geometry reverts back to it's old formation.  The edits do save correctly however and it's not until I exit out of Pro and open the project does it look correct.  This happens no matter what type of caching set we have.  Does anyone have any tips to get the data to update on the map correctly? ... View more

Hello!  I am trying to add the ESRI subscription terrain layer using an API Key generated in our ArcGIS Online organizational account.   https://esri.maps.arcgis.com/home/item.html?id=58a541efc59545e6b7137f961d7de883 I am attempting to add a portal item to a web map using the Javascript API and using the 'apiKey' parameter in the constructor and using the API Key.  No matter what I try I still get a login prompt when the layer tries to load.  Is it possible to use layers marked with 'Subscriber' and API keys? Any help would be great! Thanks! ... View more

I am running into an issue where non-editable layers are appearing on the editor dialog widget.  The layers are hosted in Portal, are created from a read-only datastore PostGres database, and 'Enable Editing' is unchecked in the layer configuration.  I have also tried to specifically set the layer as not editable in the layerinfos configuration in the editor widget.  I can use the create tools to create a new polygon for this layer but, as expected, it fails when I try to create a new feature. Is this a bug?   ... View more

We have an internal Portal instance that is using Branch Versioned feature classes that are shared out to a Distributed Collaboration on our ArcGIS Online Organizational account.  This is set up so editors can log into AGO and edit features as needed for these various feature classes.  These workspaces are synced automatically every hour.  This seems to work fine but when the syncs happen, the editor tracking fields DO NOT retain the editor values from the external source (the actual editor). Instead it looks like it's from my own account on the inside -- I'm assuming the internal Portal account that is initiating the sync?    So: When the initial sync is completed all features on the AGO side have me as the editor and creator at the time the sync occurred Features that were edited by users on the AGO side show their correct tracking information in the AGO feature class When the features are synced back, the user that controls the sync is now the editor/creator of those features   Is there something I'm missing here?  I need the original editor information to be synced back and forth correctly. ... View more

The LayerList widget is great!  Our organization and I'm sure many others have a TON of layers to sift through.  It would be great to have a simple filter/textbox for users to use to filter down the available layers in the widget. Thanks! ... View more