Latest Contributions by LindseyStone

The ability to Filter not only one field but multiple fields in Field Maps is a very helpful addition to the App.  However,  I think it would be nice to be able to have a setting to adjust the order of the field list in the Filter Window.  To me it appears that the field order in the Filter Window is based on the order the fields were created in the dataset, which sometimes doesn't make sense or helpful to the end user. I recommend that in the Layer Filter settings where you select Off, Selected Feature Layers and Fields, or All Features and Fields that there is few more options.  First option where you can check "Honor Form Order" and it is in the order that you set up the Form.  Second option is where you could drag and reorder the fields in the layer Filter settings.  This would be useful in the case where if the end user filters on the same set of fields all the time, then you could drag them to the top so they are not scrolling for them, but still giving them the option to filter on the other fields if they need to. ... View more

I'm on Enterprise 11.3 and trying to convert some of my map from WebApp Builder to Experience Builder and running into a lot of compatibility issues.   First I had my maps that I published to my Portal 11.3 as Map image Layers set up with Subtype Layers.  However, when doing this I noticed that the Map Layers widget, Search widget, and Table widget doesn't recognize anything within a Subtype Layer.  So I tired another map, and have a Group Layers created in my Pro Project, then added individual layers with filters that represents each subtype.  Now when I try this in Experience Builder, the above widgets work,  but NOW it doesn't show my legend.  But it shows the legend in the Subtype layers. What are we expected to do if Subtype layers don't work with all widgets and Grouped Layers don't work with all widgets.  Are we to have no grouping whatsoever in order for Experience Builder to work correctly? Has anyone else seen this,  or know when this is going to change.  Is there a table or documentation of what each widget that works with subtypes or group layers? ... View more

I'm on Enterprise 11.3 and I'm trying to send email notifications when a record is created in a layer that is hosted.  It is a hosted feature with 3 layers of Electric, Gas, Water.  I want the email to go to a different person depending on which layer the record is created in. Initially I had 3 individual flows set up for Electric, Gas, and Water and only had Hosted Feature/Electric selected in the Electric and so on...it would still send the emails out to all 3 of them.  So I tried to combine them into one flow with conditions.  I got it where it will go, but only go for the left condition.  If the Right condition is met the flow says it succeeds but never sends the email.  When I test the flow and click the apply to each on them to see the results they are grayed out for those when the right condition is tested.    Not sure what I'm doing wrong.     ... View more

I'm deploying the Sign Management solutions and just appended 6,000 signs from our existing records to the hosted feature via ArcGIS Pro.  There is a Sign ID field that has an Arcade Expression in the ArcGIS Online Form Editor that auto calculates incrementing values on Adding a feature .  How do I apply this same code to my appended records to create that Sign ID for them?   var layerIndex = '4' var idField = 'assetid' var idPrefix = 'POLE-' var digits = 6 /*DO NOT CHANGE ANYTHING BELOW THIS LINE -------------------------------------------------------------------------*/ function GenerateWildcards(digits, wildcard) { var wildcards = '' for (var i=0; i < digits; i++) { wildcards += wildcard } return wildcards } function GetNextId(layerIndex, idField, idPrefix, padding, sqlFilter) { // get the feature with the greatest assetid that matches the id pattern specified in the SQL statement. var assetid_features = Filter(FeatureSetById($datastore, layerIndex, [idField], false), sqlFilter) var max_assetid_feature = First(OrderBy(assetid_features, `${idField} DESC`)) // If no features match the pattern the featureset will be null, return the first assetid if(max_assetid_feature == null) { return `${idPrefix}${Right(padding, Count(padding)-1)}1` } // when features do match the pattern calculate and return the next assetid var max_assetid = max_assetid_feature[idField] var next_assetid_number = Number(Replace(max_assetid, idPrefix, "")) + 1 return `${idPrefix}${Text(next_assetid_number, padding)}` } // Define the edit context so the value is only calculated when the feature is created if ($editContext.editType == "INSERT") { // return matching prefix pattern and get next value var wildcards = GenerateWildcards(digits, '_') var padding = GenerateWildcards(digits, '0') if (idPrefix != '') { var sqlFilter = `${idField} LIKE '${idPrefix}${wildcards}' AND ${idField} NOT LIKE '%[^0-9]'` GetNextId(layerIndex, idField, idPrefix, padding, sqlFilter) } // return number id's only and get next value else { var sqlFilter = `${idField} NOT LIKE '%[^0-9.]%'` GetNextId(idPrefix, padding, sqlFilter) } } else { return $feature[idField] }     ... View more

I think it would be nice to be able to set custom zoom scale per query within a Query widget.  For example within one Query widget I have multiple query items set up where I'm searching by Address Point, Parcel, Subdivision, or Section.  I have the Zoom to Map option in the Data Action selected but that is for the entire Query Widget and not the individual Query Items that I have designated.  For Subdivision, Section, and Parcel it zooms to where the polygons are full screen which for section and subdivision this works great.  However when I do this on an address point it zooms way in farther than I would like. I would prefer that it zooms to the scale of the house and a little buffer of that and not the actual point.  So what I have is somebody does an address point search and it zooms to it and then the user has to automatically zoom right back out to see what is happening.  It would be nice say in the Results section of the Set Query window that there was a zoom scale setting of taking the default set in the Action tab or where you can overwrite that default with a custom zoom scale. ... View more