Latest Contributions by RobertKrisher

Ah yes, this is why I'm glad I started taking photos of people's faces with notes 🙂 Its typically best to digitize the circuits since it makes easier to also capture the equipment installed on each conductor. Think about how you would represent the different elbows on circuits in a junction cabinet or the different bays of a switchgear if you didn't draw the conductors. In this case you would have two cables in each conduit, offset them slightly from each other (and the conduit) then when they get to any elbows, switches, etc you would connect each cable to the corresponding device. ... View more

This is most likely a path issue, but instead of adjusting the file name or asset type name (or subtype code/name in the source database), the first thing I'd recommend trying is using a shorter Windows path. Instead of trying to have it put everything in a folder like this: "C:\\Temp\\UNmigrationTest\\UNFremontTest\\WorkingData\\MigrationWorkspace\\FremontMigration\\FremontMigrationWorkspace1\\DataLoadingWorkspace\\DataMapping\\Polylines\\PriOHElectricLineSegment_Single Phase Primary Overhead-ElectricLine_Medium Voltage Overhead Conductor.xlsx" Try something like "C:\\UNmigrationTest" as your output directory. Which would give you a path like this: "C:\\UNmigrationTest\\DataLoadingWorkspace\\DataMapping\\Polylines\\PriOHElectricLineSegment_Single Phase Primary Overhead-ElectricLine_Medium Voltage Overhead Conductor.xlsx" ... View more

This is a currently known limitation of how subnetwork management handles propagating subnetwork name. If this is important to you, please log an issue with support so they can get you attached to the corresponding bug. ... View more

Due to performance issues with the Maps SDK, Field Maps by default limits selection results to 500 features. In the next release of Field Maps, this value will change to 1000 features. If needed, the max trace results value can be increased through a mobile device management (MDM) parameter. Other trace output types, like aggregated geometries and functions, are not limited to a feature count in this way. This only applies to selections. ... View more

The helpful un links document  is meant to be a replacement for a giant collection of bookmarks that most people who work on the UN have. It was never meant to be gone through in any particular order, especially because certain links target different audiences. There are articles in here for engineers and operations, others are intended only for developers, and some are only meant to be used during data migration. ... View more

@Aaron_Sapsford I didn't see this comment because you mentioned the wrong Robert. You will not be required to upgrade past v6 for quite some time. You will still be able to leverage new features in ArcGIS Pro and ArcGIS Enterprise, but you will not have access to any of the features that are available in later schemas. You can find a list of all the features for each schema here: Utility network upgrade history—ArcGIS Pro | Documentation Move at a time that is right for your organization. If Field Maps and offline is a requirement for your organization AND you want capabilities in schema version 7 (or later schemas) then you will likely want to set up a staging environment when the next release of Field Maps comes out so you can do the upgrade in a lower environment, test out the features with field maps, and start preparing your production environment for the upgrade. ... View more