Latest Contributions by HusseinNasser2

Assume you have a user called "gdb" and you connected to the workspace with "gdb" user , you can create the attribute rule using FeatureSetbyName (  "gdb.dbo.TreeTable" ). You can also just say FeatureSetbyName ( "TreeTable") (you can do that because gdb owns the table). Regardless what you write we will ALWAYS persist it internally fully qualified "gdb.dbo.TreeTable" If a user "test" try to connect to the workspace and tried to execute the attribute rule (made an edit) then it will query the table "gdb.dbo.TreeTable"  which means test must have access to the table "gdb.dbo.TreeTable"  ... View more

Hey Andrew, Yes you only add the "gdb.DBO." prefix if you are not the owner of the dataset. if you owner the dataset you can just use the name of the class. Attribute rules are considered schema change so all connections should be closed before a change can be done.. this includes stopping services. (Exclusive lock required) You can add them to any dataset with any registration type versioned or unversioned.  ... View more

Hey Andrew, That error means that FeatureSetByName could not find the table name {FC} Means the table {FC} could not be found. Can you paste your script and a picture of your geodatabase schema? The `$datastore` global in FeatureSetByName must be your geodatabase workspace, so make sure that the table Name you specify is the physical table name in your geodatabase not the layer name. Hope that helps Here is a video of the talk I gave back in Dev Summit 2019 in Attribute rules with demos from scratch Attribute Rules in Arcade Video | Esri  ... View more

Pro 2.4.2 is now live and should fix this problem. Thanks for reporting this and again apologies for taking this long, the patch is large and has a lot of good performance fixes across the entire system not just utility network. -Hussein ... View more

Hey Joep, We are in the process of building and verifying 2.4.2, shooting for end this week or early next week. Will update the thread when its out. Apologies for taking this long, the patch is large and has a lot of good performance fixes across the entire system not just utility network. It is equivalent to a DLC in video game speak. Thanks! Hussein ... View more

If you go back to 2.3.x you should be to work normally. The bug is in the 2.4 client.  I don't have an exact date on 2.4.2 but will be sometime in August.  ... View more

Hey Kevin, We have found the problem with Pro 2.4 consuming utility network that are published to 10.6.1/10.6 services. We are planning to bring the fix to 2.4.2 Please confirm that you are on the same environment so we make sure that we covered all cases..  Thanks! Hussein ... View more

Hey Killian, can you provide the fiddler logs of update subnetwork? I think one of the calls before update subnetwork is failing and the software is giving a generic error message. We were trying to catch this bug for long time, if you have a repro case it will be great. Also tell us if you are updating subnetwork in a version or in default that will help.   Thanks p.s. I contacted support with the same request.  -Hussein ... View more

Hey Damien, Are you able to reproduce this? One way we think this could happen if Pro is left idle for a long time (4 hours+) which causes the session to expire after which editing fails. We are working on a fix for this particular case. A workaround is closing and reopening Pro should obtain a new session and fixes the problem. It will be great If you have a repro case to get so we can correct it accordingly.  And thanks for sharing this, it is useful for us to keep the quality of the software.  -Hussein ... View more

Glad that worked Ed, I still would like to know why the original approach didn't work for you, because there could be a lurking bug that we have been chasing for a while. I'm assuming you were using a special publishing map Gas Utility Network, so you can get advantage of the symbologies that comes with the model and then you repaired that map to point to your dataset correct?  Can you compare the subtypes for each layer between the service that works and the service that doesn't ? You can do that by adding both services to Pro (two different maps and just compare each layer)   ... View more

Hi Edward, Can you provide which version of Pro and server?  Also, can you try publishing a brand new feature service by doing the following? I want to eliminate certain variables 1. Connect to your geodatabase and make sure the connection is branch 2. Right click on your utility network dataset and select add to a new map 3. Say yes to the prompt to add all layers 4. Publish as feature service and enable the version management server and make sure to enable default for Zs 5. Use this service and see if you still see the errors.  Would you mind sharing an asset package with us as repro case? ... View more

The utility network layer is not yet supported in the web map spec. That is why you might have noticed when we publish a map that contains a utility network layer the sublayers are flattened into regular layers (point errors, line errors etc..). When we turn around and add the new web map to Pro the application does not recognize the utility network because it never existed in the web map.   The web map spec is evolving to include the utility network and other new layer types such as the subtype layer. No hard timeline for when those will come. There are multiple workarounds for this: 1. (For 2.1/2.2) Add the web map to Pro and then go to the original feature service and add the utility network layer (only) to the map. That should activate the ribbon.  2. Use project packages instead of web maps for Pro. Although Pro can consume web maps, the native pro project package will support not only the utility network but any layer that is supported by Pro such as the subtype layer which is much more performant than regular layers. I do understand the desire to use 1 web map that can be served across the entire organization in different clients instead of maintaining multiple maps. However, I think maps should be optimized to take advantage of smart clients capabilities. In 2.3 we have made a fix to allow displaying the utility network ribbon all the time if at least one layer that belongs to a UN is detected. The workaround to add the utility network layer won't be necessary in this case.   Edit 12-14-2018: The utility network layer still need to be present in the map in 2.3, you just don't have to click on the layer to activate the UN tab.  So the workaround to add the utility network layer after opening the web map still required. ... View more

Hi Vikram, In order to set a certain asset (Asset Group/Asset Type) to be a potential subnetwork controller in a partitioned network, you will first need to assign a directional terminal configuration to the same pair. This is critical in the partitioned network not as much in hierarchical.  Hope that helps let us know if you have any more questions and good luck!  -Hussein ... View more