Latest Contributions by RobertKrisher

Can you post a screenshot of where the update stops in the circuit?  The most likely causes are things like not setting a terminal connection or accidentally setting a value on a feature that stops tracing (i.e. setting a device to be open or a junction/device/line to not be in service). ... View more

If you had a way to match up your non-spatial table with a spatial source you could use geoprocessing tools to achieve this, but if that line you're trying to create is the one that was deleted out of SDE than you may be out of luck there.  If you were just trying to get the geometries for one or two features you may be able to go back to source drawings for the area or infer its shape based off of some stationing or linear referencing system (if you have one), but all of these approaches can be fairly difficult. ... View more

I've included a copy of the service definition and the ArcGIS Pro Web Map definition.  I thought about including the web map definition from a map created in ArcGIS Enterprise, but it behaves exactly as you described 😃 ... View more

Michael,   I just revisited this and @ 10.6.1 with ArcGIS Pro 2.2.1 I lose domains and subtype descriptions in my map document definition in a shared web map even if I symbolize using only the subtype field.  If I look at the map definition I can see that the domains element is blank (even though the field has domains) and even though the type has an id its still unrecognized as a subtype by the map (I wouldn't the order would matter, but the id is typically at the beginning of the json element but for a pro web map its located at the end). "types": [           {             "name": "Anode",             "domains": {                            },             "templates": [               {                 "name": "Anode",                 "prototype": {                   "attributes": {                     "assetgroup": 15,                     "assettype": 0,                     "rotation": 0,                     "insulatordevice": 0,                     "ownedby": 1,                     "cpsubnetworkname": "Unknown",                     "depth": 0,                     "terminalconfiguration": "Default",                     "devicestatus": 1,                     "accessible": 1,                     "maintby": 1,                     "lifecyclestatus": 3                   }                 },                 "drawingTool": "esriFeatureEditToolPoint"               }             ],             "id": 15           }, ... View more

This still sounds like a bug.  Just because I'm symbolizing off of something other than the subtype field doesn't mean that I should lost all of my domain and subtype information.  The other thing is that if I author a web map using Portal or AGOL I won't lost all the subtype and domain information.  Using AGOL or Portal to author all my web maps isn't a good workaround at this point because I have hundreds of customer symbols across half a dozen styles that I need to use in my map and there's no way for me to load a custom style into my ArcGIS Enterprise site (unless its a style for 3d points). ... View more

Jimmy,  I've run into this issue with the UN extension with a slightly different case (for which there is a bug that is logged). You can also replicate this behavior my sharing a web map authored in ArcGIS Pro (take a fully functional layer like the one you've published it, pull it into pro, share the web map, now that map is broken). My way around this is to publish my initial feature service just using the asset group field, since I usually need to apply additional configuration (definition queries, additional symbology, etc) in a web map to make use of the data.  Because of the previous point I'm left authoring maps in Portal / AGOL until they resolve the bug. ... View more

For medium and large sized utilities a lot of this detail is stored and maintained inside external asset management systems (Cityworks, SAP, Maximo, and WAM are the ones I've seen the most).  Related data you're going to be using in things like collector is going to be captured in related tables (the example packages have inspections done this way).  Other misc related data can be stored in flat tables and then either related or joined to the source data as needed.  I wouldn't recommend having these joins and relates in your day-to-day editing displays since they'll impact performance, but having specific views that pull in several aspects of this data at a time is pretty typical. ... View more

I'd recommend take a look at the different types of input connectors ( Input connectors—Real-time Data Feeds and Sensors (10.6) | ArcGIS Enterprise  ) that GeoEvent server offers.  These can allow you to pull data from other systems using flat files, web calls, and many other methods.  It sounds like you're trying to extract information from some kind of SCADA system, depending on the software being used to store the data you may be able to use certain apis or products to accomplish this.  As an example, if the data is being stored in OSIsoft's PI Historian, they have a product that allows you to publish real time feature layers from your SCADA data that can be read directly by the GIS. ... View more

When you first apply the asset package it should also create all of database sequences, even if you don't load the data.  I'd recommend you either run the database sequence tool ( Create Database Sequence—Data Management toolbox | ArcGIS Desktop  ) and create the "WaterDevice_10_seq" that this expression is expecting.  If that doesn't work you can always identify and disable any attribute rules that are making calls to database sequences using the disable attribute rules tool ( Disable Attribute Rules—Data Management toolbox | ArcGIS Desktop  ). Hope that help! ... View more

Kylie - I'll be attending the Esri UC if you want to have a follow up conversation about this. My area of interest is in the Utility space where we're dealing with the constraints imposed by Branch versioning feature services.  In terms of editing, one of the biggest constraints around this is that any versions (and therefore edits) created against a given feature service can only be seen within that feature service.  So if I set up a separate feature service for Collector (or web editors) that only exposes a subset of the data to my editors, then when the data is being reviewed / cleaned for posting the reviewer will be limited to seeing the same amount of data. This becomes incredibly important when you have field personnel collecting a subset of required information and require back office personnel to do a lot of the heavy lifting to get the data prepared.  The way I handle this right now is by just using client side configuration to use settings on the layers (definition queries, field visibility, field highlighting, etc) to control these behavior.  The challenge with the client-side constraints is that they are easily bypassed by advanced or malicious users.  By enforcing these constraints at a service level I am able to safeguard against this. ... View more

Excellent!  Since you're already using a topology builder that gets you half the way there, just find all the regulators with a pressure differential between their high side and low side and set terminals accordingly.  This solution works for simple regulator stations with a single regulator, but for situations where there are multiple regulators working in parallel and/or series the logic gets increasingly complicated. ... View more

While I love the idea of using hosted feature layer views the limitation of only being able to use them on hosted feature layers definitely limits how I can use this right now.  Any idea on when / if there will be support for something like this with feature services? ... View more

While the workbench either shows how or allows you to extrapolate how to do the majority of the conversion, one of the biggest items not shown is how to derive the subnetwork controllers for systems and pressure zones.  This is problematic for a few reasons. Te biggest issue is that this means that all the station regulators in your model will create three ambiguous connectivity errors (type 9, more than one rule exists). In order to resolve this error you need to properly identify associate the inlet and outlet terminals with their corresponding mains, typically inferred by a pressure differential between the mains on a regulator but in cases where there are two (or more) regulators working in a station only the low-side regulators will have a pressure differential. Once the inlet/outlet associations for each regulator have been defined each downstream regulator must be assigned a subnetwork named based off of all the other regulators it is connected with for the pressure system. I've typically relied on python scripts to do this after-the-fact, but given that without the terminal associations most networks won't build I would have expected to see it included in the workbench. ... View more