Latest Contributions by LindseyStone

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

This is regarding the Electric Utility Network. I'm required to export by subnetworks to JSON files in order to import them into our Outage Management System. This is the file format that is required by this vendor. I utilize the export subnetwork tool and have no issues with the export of each of our 54 subnetworks. In this situation with this vendor the GIS is the normal state of the our Distribution System and then within the OMS software they can temporarily open/close switches in the event an system/feeder outage or maintenance and their maps update accordingly to show the LIVE status of lines. So in reality the GIS is the normal state but the OMS could be showing a different state of LIVE. The situation that I have is in places we have lines sitting between two OPEN switches in the GIS which is the normal state. So when I run the update network tool no subnetwork is applied to these lines because it stops at the OPEN switches which is exactly as I would expect. However, since no subnetwork is applied to this these lines, when I run the Export Subnetwork to export the subnetworks to JSON these lines are then left out of all my exports. The issue with this is, in the event of a LIVE situation of an outage or maintenance they may CLOSE these two switches in the field making this line LIVE. However in the OMS, this line will not even be on their maps because it didn't export with the rest of the subnetworks because it has none in the normal state of GIS, giving them an inaccurate map. My question/suggestion is there needs to be a way to export these "Dead" lines to a JSON in the exact format as my subnetworks so I can import them into our OMS so they can be utilized as part of their maps. ... View more

In Experience Builder developer v1.17.  I am trying to set up the query widget with an attribute filter where Field Name is Unique where it gives a drop down list of all the values.  Upon testing it the drop down just spins.  I have this same setting set up on a different Experience Builder App utilizing a different service and it works just fine.  The one working is about 50 records compared to the one not working is 650 records.   I looked on the service properties (service is published from Pro to Enterprise server) and it has the maximum number of records returned by server as 1000.  Within Experience Builder I upped the record page size to 900. Is there a max size limit on this option or am I missing another setting to check for this capability on this amount of records? Just for fun I also tried to add the Search widget and added this same layer as a custom data source with suggestions and after a type the first 3 letters than I DO get suggestions.     ... View more

I just downloaded the newest Developer version of Experience Builder 1.17.  Curious if I'm missing a setting or if we went backwards on the Draw widget.  On version 1.16 the widgets tools where in two rows so the widget didn't have to be as wide On version 1.17 all of the widgets are on one row,  forcing me to make a widget super wide or creating a scroll bar at the bottom. Why would ESRI put this all on one row forcing a scroll bar from left to right, this doesn't seam as user friendly then just putting it in multiple rows.  I think if any widget has multiple tools like the draw widget it should automatically wrap the tools based on the width of the set widget window.     ... View more