Subnetwork Controller name do not like parentheses

[VickyWang]

Are there any limitations to the subnetwork or subnetwork controller name? 

Form the sample solution it accepts dash ‘-‘ and semi column ‘:’ ('Iso:755' or 'Bob-O-Link Isolation Zone Valve')

Would any special characters are not accepted for the name ?!

Use the subnetwork name as 'TS (testing site)'. 

It's not working as what's expected when using this subentwork name for update the subnetwork process.  

Create another subnetwork name (remove the brackets e.g. 'TS testing site') then it works update subnetwork and tracing function. 

Thanks 

[MikeMillerGIS]

According to the help - Set a subnetwork controller—ArcGIS Pro | Documentation 

Supported special characters include hyphens, colons, ampersands, spaces, number signs, forward slashes, open parentheses, and closed parentheses.

So Open and Closed parentheses like in your example should work.  If not, we need to get a bug logged.

[VickyWang]

HiMichael Miller‌ : 

Thanks for the link. It is likely to be a bug.

I've run another testing, more details below:

To set a subnetwork controller name: subnetworkcontroller (storage). 

Run an Update Subnetwork geoprocessing, it shows the No Subnetwork Controller was discovered. 

ERROR 001797: No subnetwork controller was discovered.
Failed to execute (UpdateSubnetwork).

I modified the subnetwork controller name to : subnetowkrcontroller:storage. The Update Subnetwork tool ran successfully. 

The environment is :

ArcGIS Enterprise  10.7.1

ArcGIS Pro 2.4

Water Utility Network solution 3.2

(process ETL from source to UN model asset package)

water utility network‌ #utility network

[MikeMillerGIS]

Your message says brackets, but your example uses parentheses.  Brackets are invalid.  Can you verify which you are having problems with?  Can you share an asset package with an example of the name that is failing?  Did you use that name before as a controller name or as a subnetwork name?

[VickyWang]

Hi Michael Miller‌, 

Updated the title, sorry makes it confused. It's open/close parentheses on the Subnetwork Controller Name. 

The first try: Both names of Subnetwork Controller and Subnetwork are with parenthesis - failed.

the second time: only replace parenthesis in the subnetwork controller name - working.