|
IDEA
|
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
10-24-2025
07:26 AM
|
2
|
1
|
172
|
|
POST
|
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
10-21-2025
01:10 PM
|
0
|
2
|
247
|
|
POST
|
@MikeMillerGIS defining a default value on the subtype Manhole Channel fixed this attribute rule issue and now it Runs. Thank you for that suggestion. @PatrickGCowan thanks for the more detailed explanation. My Civil Engineer has stated he wants all the elevation data in it so it looks like the higher accuracy is the direction I most likely would need to look towards. Another question on the attribute rules when it applies to the Manholes. Within the Manhole it has Rim Elevation, Invert Elevation, and Depth. I'm seeing if I update the Z value on the Manhole it updates the Rim Elevation & Invert Elevation on the Manhole, the Z elevation on Manhole Channel, the Z elevation on associated Pipe Connections and Pipes, along with the elevation on the pipe. I'm loving all the places it automatically fills out. But my questions are: 1. Why does it fill out the Rim Elevation wouldn't this be different than the invert elevation as the rim is at surface level? Otherwise your depth will always be 0. I would think this would just be manually entered as an additional value just in the attribute table. 2. What happens if the Pipes are different heights within the Manhole Channel. I know this is common in Sanitary Sewer to have drop manholes, didn't know if this was a thing too concerning in Strom Sewer. Thanks again!
... View more
10-08-2025
10:01 AM
|
0
|
0
|
184
|
|
POST
|
I've just deployed the Stormwater Utility Network and have been testing and I noticed that every time I try to add a manhole I get this error. I disabled the Structure-Junction - Create Manhole Channel attribute rule for the time now, but it would be nice to know how to fix this. I'm looking at the activevol field in devices subtypes and that isn't even a field being utilized as it has domain set up to it. Also, can someone explain to me why the thought process of having the manhole structure Junction, a Pipe Connection Device, and a Manhole Channel Device all at this location is necessary. Seams like a lot. I've also found that I get an error message when utilizing the template BMP Boundary with centroid BMP Boundary with in the Editor map of the provided Pro Package with an association error message.
... View more
10-03-2025
07:09 AM
|
0
|
3
|
288
|
|
POST
|
Thanks Patrick.. I must have read the documentation wrong and thought that started at Pro 3.5, I was hesitant making that jump.
... View more
09-26-2025
12:29 PM
|
0
|
0
|
67
|
|
POST
|
@RobertKrisher or @BrandiRank22 I downloaded the Stormwater Utility Network off the solution site and I'm having a Pro compatibility issue. Looks like everything in the solution was created in Pro 3.3, but when trying to apply an asset package to my enterprise geodatabase I'm getting the below error message. I'm trying to use Pro 3.1 because I need a version 6 of the utility network, since Field Maps does not support UN version 7. I'm on Enterprise 11.3. Is there anyway to remove unsupported fields, export this out to a new asset package or get a compatible version of the Solution? ERROR 160627: This version of the Geodatabase client is incompatible with the dataset and cannot open it. Failed to execute (ExportXMLWorkspaceDocument).
... View more
09-25-2025
07:30 AM
|
0
|
2
|
605
|
|
POST
|
@RobertKrisher Has there been any more update with Utility Network and Enterprise 11.5 compatibility? The Utility network compatibility page still has no mention of 11.5. Just found out my Enterprise 11.3 Experience Builder is not compatible with Group Subtype Layers and all my Utility web maps are set up with Group Subtypes, I'm not excited about the idea of having to completely reset up these maps without Subtypes Group Layers just so I can use the widgets in Experience Builder. May continue to live in WAB until 11.5 upgrade.
... View more
09-03-2025
02:38 PM
|
0
|
0
|
459
|
|
POST
|
For the 2 Apply to Each question. I didn't add them, as soon as I added the parallel condition statement it automatically add the 2 Apply to Each. Why they need to be there or why it added them I don't know. I did some testing last week and If I make 3 separate workflows with one condition in them each for the services than it works. But it really seems silly to have 3 separate workflows against the same service. I will give your suggestion a try, never thought to put another condition in the NO part.
... View more
08-19-2025
06:02 AM
|
0
|
1
|
443
|
|
POST
|
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
08-14-2025
08:50 AM
|
0
|
3
|
513
|
|
POST
|
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
07-17-2025
08:30 AM
|
0
|
1
|
256
|
|
POST
|
@Shen_Zhang Question...I've had several users like the tooltip but dislikes how the measurement on it changes from feet to miles once you hit 1,000 feet. Is there an override somewhere on that? Yes I we could add the measure widget to the map, which doesn't do this, but I have always utilized the measure part of the draw tool to keep our already widget heavy map not loaded up more.
... View more
06-18-2025
09:03 AM
|
0
|
1
|
364
|
|
IDEA
|
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
06-10-2025
09:37 AM
|
2
|
0
|
269
|
|
POST
|
@Ke_Xu I had reached out to support and we figured out the issue with my layer having issues was it didn't have Advanced Queries enabled. The reasoning for that it was pointing to a shapefile and not a file geodatabase. Once I imported my shapefile into a geodatabase, the advanced queries was enabled and the drop down worked. I'm currently waiting on support to get back to me whether this is a an existing or new bug or core limitation, etc.
... View more
05-13-2025
08:38 AM
|
1
|
0
|
360
|
|
IDEA
|
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
05-12-2025
07:23 AM
|
0
|
3
|
711
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-20-2025 12:40 PM | |
| 2 | 10-24-2025 07:26 AM | |
| 2 | 06-10-2025 09:37 AM | |
| 1 | 05-13-2025 08:38 AM | |
| 1 | 09-14-2020 10:00 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|