Latest Contributions by NickHarvey

@JacobBoyle412  - Hi Jacob - Please see the highlighted text  in the attached pic (and at bottom).  Do I take this to mean that 3rd party SAML with multifactor authentication will work with AGOL?  But that the AGOL-based multifactor option won't work with a SAML login?   The text in the attached pic reads: "Multifactor authentication is not supported for SAML logins,...".  Sorry, I'm reading it both ways...Any help appreciated...  -Nick    ... View more

Thanks Jon makes sense - and concise.  ... View more

9.  It looks like creating Terminal Configurations for double-outlet manholes may be a better way to handle this:  See this post:  https://community.esri.com/t5/arcgis-utility-network-questions/trace-results-with-loops-and-double-outlet-sewer-structures/m-p/1070684#M1233 ... View more

Just discovered this post.  Using the UN Package Tools it looks like you can Apply Asset Package to a newly created UN inside a newly created fgdb and the schema/model is applied and will still allow you to create a new terminal configuration. ... View more

I just got this working thanks Alex. I had seen this post regarding double-outlet manholes (We use the term 'double-outlet', as 'elevated' might invoke raised manholes at our agency).  I had thought it might be a solution but couldn't figure out how to create terminal configs, post-Topology. So that brings me to this question:   I could not find a way to implement this solution without creating a new fgdb UN which are not auto-associated with the asset package data model (a number of steps to replace). Will terminal configs always be necessary to create, pre-Topology? Or, is there workflow that I'm missing or unaware of?  Knowing the answer will help me plan for our UN Enterprise deployment, your solution works in either event.  Thanks a bunch! -Nick ... View more

Man, its tough when everyone replies at once.  I did find a Note regarding this on the Utility Network trace types page: Can anyone on the ESRI UN Team suggest a workaround? Or will directional loops be supported in the future?  Our braided (dual) interceptor lines cover dozens of river miles.  If we were storm water, this would be troublesome because tracing upstream of an illicit discharge sampling hit on one side of the loop would select the whole loop (upstream and downstream).  But the same goes for our wastewater allocation queries  (with a potential connection to one side of a dual interceptor).  ... View more

8.  We have dozens of double-outlet manholes in our sewer system that typically exist along the basin boundaries (ridgelines).  Even though the associated outlet lines were digitized in the correct flow direction, some loops are still generated in our single use UN.  Some of the lines associated with these loops are categorized as having an indeterminate flow direction in the single use UN (which is puzzling).  This only became apparent when I turned off the 'Allow Indeterminate Flow' option in the Trace config (the trace would then stop at those lines).  This isn't the case in our production Geometric Network traces (same lines).  I'm not sure how to explain it yet (probably doing something incorrectly).  But for now, I have solved the problem by script-appending some faux sewer devices at each double-outlet manhole and specifying a condition barrier for that Device Asset Group.  Using this condition barrier (Dynamic barrier) allows the user to still add their own barriers interactively (Feature barriers) when using Set Trace Locations or when using a saved Trace Configuration.     ... View more

BUG-000140068 ... View more

7.  Also from notes:  When I scaled this up using our actual data (loading our mains, etc) - I had to disable the topology, load data, then re-enable the topology to update the Is Connected attributes.  Otherwise the UN tools would not acknowledge that the newly loaded features were topologically correct.  I also had to delete the original Asset Package (Naperville) spatial index before updating the subnetworks due to the grid size being invalid (threw error).    ... View more

This appears to be fixed at 2.8.0 (launches default browser when clicking hyperlinked documents).  However, hyperlinks containing single quotes are not working as expected.  Have put in a Support case. -Nick ... View more

Just updated to Pro 2.8.0.  Document hyperlinks are opening as expected but single quotes are giving me trouble.  Anyone else having this issue? -Nick ... View more

Hi Cindy - I agree with Robert's comments and went the same route at first (fgdb Trace Network). I did come back to the Utility Network (fgdb) recently and got the upstream, downstream, and subnetwork tracing functions working.  I'm listing some suggestions below that helped me in the second attempt. See the Sewer Utility Network Foundation if not already.  Change the spatial reference of the Asset Package and edit the ServiceTerritory polygon per your geography. Apply the Asset Package to a File Geodatabase. At first, create/edit a tiny fictitious collection system (from scratch) using the output fgdb from #3. I did this with just the Sewer Line, Sewer Device & Structure Junction feature classes. Populate the Asset Group and Asset Type fields at minimum. Include your system scenarios (connect a couple of gravity mains to a pump station to a force main to a pipe connection/controller point to a gravity main to the treatment plant, etc). Each time you create a different scenario, validate the topology and refer to the connectivity rules provided under Network Properties until the dirty areas get resolved. Finding the right 'From' and 'To' device terminal types (attribute fields) on the Sewer Line feature class is key for each scenario. Create the Tier1 (sewer collection system) subnetwork using your treatment plant (Sewer Device) as a subnetwork controller before you try to create a Tier2 (sewershed) subnetwork. I made this error at first (obvious in hindsight). I had to add a pipe connection-controller point where force mains connect to gravity mains. Without the pipe connection-controller point, I noticed that my Tier1 subnetwork would not update (expand) upstream through the force main when I added features upstream of the associated pump station. HTH -Nick ... View more

We put in a Support case, now connected to the two items below: BUG-000138846 : Pop-up fails to play the MPG video file stored in a local drive in ArcGIS Pro 2.7. *Note:  Our .mpg's would not play from network or https hyperlinks either. We demonstrated formatting with Support remotely, etc.  ENH-000138568 : Provide the ability to open pop up link page with specific internet browser in ArcGIS Pro. The original title of our Support case was "Hyperlinked documents do not open using default Windows program".  ... View more

Thanks Jared - I haven't been able to duplicate this workaround at 2.7.3.  In the end we want our field-based hyperlinks (pipe video) to work from the attribute table too, but will use custom popups if need be.  Bottom of this thread had this as an enhancement I think:  ENH-000107706.  ... View more