|
POST
|
@jsarthur I updated my response to make it clearer I was responding to the question @aperi asked. The tabbing/indenting on the community site sometimes makes it hard to track the separate threads.
... View more
04-14-2026
10:22 PM
|
1
|
0
|
259
|
|
POST
|
Intakes are configured to be able to be used as subnetwork controllers in the system tier of the model, they just aren't configured to be controllers of the pressure tier of the model. For the reasons that Pierreloup and myself listed.
... View more
04-14-2026
06:22 AM
|
1
|
0
|
244
|
|
POST
|
@aperi Distributed collaboration is supported between different ArcGIS Enterprise environments at 11.5: Getting the most out of distributed collaboration in ArcGIS Enterprise
... View more
04-14-2026
06:18 AM
|
1
|
3
|
282
|
|
POST
|
There is no system-managed queuing mechanism for posting versions (traditional or branch).
... View more
04-14-2026
06:14 AM
|
0
|
0
|
281
|
|
POST
|
In ArcGIS Pro 3.6 and earlier, once you have assigned a domain to an asset group, you cannot remove any of the codes or descriptions associated with it. If you unassign the domain then assign a different domain to the asset group that has different codes/descriptions, you will get this error.
... View more
04-14-2026
06:10 AM
|
0
|
1
|
187
|
|
POST
|
A feature can only be a subnetwork controller for a single tier, so if you make it a controller for the pressure tier then it won't be considered as a source of water if you run a trace on the system tier.
... View more
04-10-2026
01:58 PM
|
1
|
0
|
348
|
|
POST
|
Because your tool is functioning as an external process you are having these issues with locks. If you can make the requests using the same session as your pro session you won't have an issue with this, which is difficult to do if you are making rest calls directly.
... View more
04-10-2026
07:29 AM
|
1
|
1
|
248
|
|
EVENT
|
If you subscribe to this page/event and have notifications turned on you should get notified when it gets updated every month.
... View more
04-09-2026
10:21 AM
|
0
|
0
|
474
|
|
POST
|
No, the 'terminal configuration' field on the feature refers to the path between the terminals that will be used when the device is traced, not the terminal configuration assigned to the asset type of the feature. Rules are not affected.
... View more
04-08-2026
09:27 AM
|
0
|
0
|
348
|
|
POST
|
Disregard what @VenkataKondepati said about there being a utility network in the configuration tab. That is not a thing. I think he meant to tell you to enable the version management option (which you do have enabled). In your statement you said you're going to ArcGIS Online, but I assume you meant to say ArcGIS Enterprise? You will add the data to your map using a feature service (this is discussed in the online help linked to above and the article I posted). All of the items on the ribbon should be come enabled when a) there is a utility network in the map and b) you have the appropriate licenses applied to your named user.
... View more
04-06-2026
03:16 PM
|
0
|
0
|
284
|
|
POST
|
Make sure the map you used to publish your feature service has the utility network in it, and you should review the list of missing tables and consider including those in your service as well. The steps are outlined in this article: Deploying a utility network to ArcGIS Enterprise If you end up dropping/re-adding any layers make sure that edit the properties of each layer so the layer IDs on your updated service match your original serviec.
... View more
04-06-2026
06:24 AM
|
0
|
0
|
308
|
|
POST
|
Vertex within tolerance will not generate topology errors, but they are data quality issues that can result in problems with tracing and editing. In terms of applying resolutions not fixing all the errors, that shouldn't be the case, but I can imagine there are some edge cases that the tool may not be able to handle. If there are a relatively small number of them than you may be better off manually resolving them. By doing that you will probably understand why the automated tool is not able to correct them. If you plan on running subsequent migrations, you should also look at correcting the problems in your source database.
... View more
04-02-2026
12:00 PM
|
1
|
0
|
242
|
|
BLOG
|
@BrettJohnston1 while Tom finds and updates the link, I think it might be the one listed with the foundation here: UPDM_dynamic
... View more
04-02-2026
10:48 AM
|
1
|
0
|
605
|
|
POST
|
To add onto what @gis_KIWI4 said, you don't want to just pass everything into an anchored snapper. That would be a mess. What you want to do is use transformers to identify the problem, and apply a targeted fix precisely. Mature data migration vendors have already worked out the logic for doing this reliably and safely. When done improperly, this can lead to topology errors (self-intersecting lines, duplicate vertices, etc) and disconnected features (stacked points, missing vertices, etc). But if you don't have too many of these you and/or you have enough free time and grit then it is a tractable issue.
... View more
03-31-2026
06:17 AM
|
0
|
1
|
497
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | Wednesday | |
| 1 | Tuesday | |
| 1 | Tuesday | |
| 1 | Saturday |
| Online Status |
Offline
|
| Date Last Visited |
10 hours ago
|