POST
|
Perhaps this is what your looking for? GitHub - Esri/solutions-data-dictionary-viewer: An Interactive Viewer to View Feature Service Details
... View more
01-05-2023
05:04 AM
|
1
|
1
|
1404
|
POST
|
Does Experience Builder have a dynamic query tool/widget of some sort that lets the user create simple queries in their maps?
... View more
12-05-2022
05:04 AM
|
0
|
0
|
131
|
POST
|
Mike, thanks for the input, can you confirm if this is normal behavior? if so, just wondering what best practices might be since determining all terminals versus assets at the commencement of a project likely won't always happen. The foundation models have some of these set by default, perhaps if a client isn't prepared to commit to development of a specific subnetwork initially then the terminal configurations for those assets per tier should be deleted? Assuming if no terminal configuration is set to an asset group/type initially that they still can be set later, after initial topology enablement. Or does all this have to be set before initial topology enable no matter what?
... View more
10-18-2022
06:02 AM
|
0
|
1
|
1189
|
POST
|
The error message isn't about topology currently being enabled or disabled. The error message pertains to the initial enabling of topology on the database. Certain process can only be run prior to enabling the topology the first time - but this tool is not one of them, somehow it thinks it is. It's not about current topology state, it's about post initial enable. I want to confirm this for other viewers.
... View more
10-17-2022
01:30 PM
|
0
|
1
|
1212
|
POST
|
I think perhaps you're reading the post a bit wrong: - the tool error is saying it can't be run once the database has had the initial topology enabled, - there are a couple of tools that can't be run after you set up the db and initially enable topology, but the Set Terminal Configuration tool is not one of those tools, per the screenshot - I have the topology disabled when running the tool
... View more
10-17-2022
12:17 PM
|
0
|
3
|
1253
|
POST
|
I've added a new terminal configuration in our UN, now I need to assign it to an asset. Using the Set Terminal Configuration tool errors out with this message: ERROR 002571: Operation is not allowed once the topology has been enabled. I'm confused by that because all the documentation I read says that this tool can definitely be run after the initial topology enable. I'm connected as DB owner, portal owner, default version. topology is disabled.
... View more
10-17-2022
11:56 AM
|
0
|
9
|
1266
|
POST
|
Thank you all for sharing this information, it's greatly appreciated and will be much used!!
... View more
08-25-2022
09:47 AM
|
1
|
0
|
2857
|
POST
|
I'll be trying that, I also really like those ArcMap tools Sergio mentions, thanks Mike.
... View more
03-31-2022
11:05 AM
|
0
|
0
|
486
|
POST
|
Were in the middle of a UN rollout and this is what we did, we didn't want to educate the client in the default data setup and didn't think they would find it very intuitive. The downside is you will have to chase down all the necessary customizations, rules changes, etc.
... View more
03-09-2022
05:37 AM
|
1
|
0
|
1486
|
POST
|
Posting the solution in our case, not alot of info on this topic. We loaded client storm water CAD data into the latest UN asset package. The load failed at the Device > Manhole Channel > Manhole Channel layer, specifically the 'activevol' field, we left that field null during the load as we don't have attribute data for it. That caused the load to fail. So we inserted arbitrary value of "1", data load was successful. Long story short, it was this value that was keeping the subnetwork dirty and would not propogate the network past the first manhole channel upstream of the subnetwork controller. Once we flipped to 'activevol = 0' the subnetwork is clean and network updated properly. ESRI, seems like a valid default should be enforced in the asset pacakage for this field. This may not be other people's problem, but it could be.
... View more
02-04-2022
06:27 AM
|
1
|
0
|
387
|
POST
|
Posting the solution in our case, not alot of info on this topic. We loaded client storm water CAD data into the latest UN asset package. The load failed at the Device > Manhole Channel > Manhole Channel layer, specifically the 'activevol' field, we left that field null during the load as we don't have attribute data for it. That caused the load to fail. So we inserted arbitrary value of "1", data load was successful. Long story short, it was this value that was keeping the subnetwork dirty and would not propogate the network past the first manhole channel upstream of the subnetwork controller. Once we flipped to 'activevol = 0' the subnetwork is clean and network updated properly. ESRI, seems like a valid default should be enforced in the asset pacakage for this field. This may not be other people's problem, but it could be.
... View more
02-04-2022
06:27 AM
|
0
|
0
|
368
|
POST
|
Randall, encountering a very similar problem. did you resolve and is there any insight you could pass along?
... View more
02-03-2022
01:00 PM
|
1
|
0
|
1412
|
POST
|
Just a shout out that I deal with the exact same problem, alot!
... View more
02-03-2022
08:06 AM
|
0
|
0
|
562
|
POST
|
Hi, grappling with the exact same thing. Just wondering if you had any insight you could offer.
... View more
02-02-2022
02:22 PM
|
0
|
0
|
392
|
POST
|
you could create a new asset type - Bend. if you don't want to get into modifying the model perhaps you could use Fitting > Elbow, and then note the bend degree in the 'Notes' field??? Just a thought. From the Naperville data it looks like ESRI used Elbows as bends.
... View more
09-07-2021
01:36 PM
|
0
|
0
|
1247
|
Title | Kudos | Posted |
---|---|---|
1 | 02-03-2022 01:00 PM | |
1 | 06-13-2023 07:17 AM | |
1 | 02-12-2021 05:37 AM | |
1 | 01-05-2023 05:04 AM | |
1 | 02-04-2022 06:27 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|