|
POST
|
The issue is because you have a configuration table. That configuration table, with all check boxes checked, is removing asset groups/type from the target. This results in a SQL filter on the input data to ensure it is not copying AG/AT that does not exist in target. Delete or rename the D_Configuration table
... View more
02-22-2024
11:44 AM
|
0
|
0
|
1871
|
|
POST
|
02-22-2024
05:50 AM
|
0
|
0
|
1883
|
|
POST
|
Can you verify those features do exist in the Asset Package? Want to ensure it is not a Data Loading issue. Any chance we can get the source, data loading workspace and asset package?
... View more
02-22-2024
02:02 AM
|
0
|
2
|
1892
|
|
POST
|
Not really sure the expectation across tier group. Hard to answer the modeling questions without looking at the model.
... View more
02-20-2024
05:21 PM
|
0
|
1
|
824
|
|
POST
|
Just a guess, but I think you are an issue with using tier groups to create a partitioned network. I am not sure as this is not a configuration I have tested.
... View more
02-20-2024
02:36 AM
|
0
|
1
|
2593
|
|
POST
|
This is hierarchical, hmm. That definitely complicates things. Tier Groups are typically used to model different commodities or different rankings of the same commodities. I am not sure what the expectation is when tracing across tier groups.
... View more
02-20-2024
02:17 AM
|
0
|
0
|
2596
|
|
POST
|
You should remove - category = subnetwork controller. That is not needed and is handled by the subnetwork. I think this is your issue.
... View more
02-20-2024
02:14 AM
|
0
|
4
|
2598
|
|
POST
|
That looks correct. I am not really sure. What are you condition barriers? Do you have propagation configured?
... View more
02-20-2024
01:04 AM
|
0
|
6
|
2603
|
|
POST
|
The attribute rule is always run in the database, no matter the client. If it works in pro, it works in a web app. I assume the data is backed by an enterprise database, right? ArcGIS online services do not support attribute rules.
... View more
02-16-2024
12:03 PM
|
0
|
0
|
2140
|
|
POST
|
Yes this should work. You are setting the target to the MV I assume. Did you try it with and without indeterminate flow? Can you post a screen shot of the LV controller and trace settings?
... View more
02-16-2024
02:55 AM
|
0
|
0
|
2661
|
|
POST
|
Without an attribute rule, no. We have created an auto assign terminal Attribute rule that does have this logic though. It will not assign a terminal if it is already used - https://community.esri.com/t5/arcgis-utility-network-documents/automatic-assignment-of-from-to-terminal-values-on/ta-p/1307198 but if there is only one rule to that terminal, then a value is not required and it will connect with no error.
... View more
02-16-2024
02:51 AM
|
0
|
0
|
2445
|
|
POST
|
I would strongly suggest using ArcGIS Pro 3.1.2 and the matching UNTools Also, try it with a pro project with no maps in it. We have seen a lot of issues with locking due to the map
... View more
02-16-2024
02:48 AM
|
0
|
0
|
779
|
|
POST
|
var meters = Filter(FeatureSetByName($datastore, "PipelineDevice", ["Full_Address"], true), "ASSETGROUP = 2") lgtm
... View more
02-15-2024
04:09 PM
|
1
|
1
|
2330
|
|
POST
|
That GUID represents a moniker to a table which is needed when the data is published. Since it shows the GUID, it means the table it references no longer exist. Just change it to the reference the PipelineDevice and wrap the FeatureSet in a Filter and use the SQL to filter to only gas meters
... View more
02-15-2024
03:50 PM
|
0
|
3
|
2338
|
|
POST
|
This is allowed, nothing restricts the cardinality.
... View more
02-15-2024
03:14 AM
|
2
|
1
|
2472
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 2 | 07-07-2026 06:45 AM | |
| 1 | 06-26-2026 09:15 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|