Latest Contributions by RyanBohan

@JakeSkinner  Thank you Jake, it appears the ArcGIS Enterprise product lifecycle.  link is broken, do you know how I can get it reported, it appears to be linked in multiple places. ArcGIS Configurable Apps Roadmap for Retirement     ... View more

Nevermind, I got it ... View more

I am running this script and only getting returns of class webmaps, I know our organization and more old stuff that needs to be found and either upgraded or deleted ... View more

Can changing the default Expression Type, just be added under Options?  I don't really want to tell all users to just edit their "Pro.settingsConfig" file, so I know the next thing I will get is an email, saying they broke it. ... View more

I don't call my layers: Layer, Layer1, Layer2, Layer3, etc ... View more

This would be so helpful.  Which map was I just working on.  Hmm I have by default Map, Map1, Map2, Map3... yes, I can rename them, it would be so much better to just name the map when it's being created. ... View more

As we transition to branch versioning, our preferred approach is for teams to create and manage their own versions, then perform reconcile and post operations to the default version. Since teams are most familiar with their own data, they are best positioned to resolve any conflicts that may arise. To perform reconcile and post operations, one or two team members need to be assigned the Version Management (VM) role. Ideally, two users per team will hold this role to ensure coverage during absences. However, this setup introduces a potential loophole: users with the VM role can directly edit the default version. This could prompt more team members to request VM access in order to “work faster,” effectively bypassing the intended versioning workflow. As a safeguard, we’re considering restricting who can create versions and perform reconcile and post operations. While this would help maintain the integrity of the default version, it could also slow down workflows and place added responsibility on a small group of trusted users. These users may not be subject matter experts in the data they’re managing, which could lead to additional back-and-forth with the teams that originally created the data. We’d appreciate any insights or experiences from others who have implemented similar workflows. How are you balancing control and flexibility in a multi-team environment? ... View more

Thank for the update @Nelson_Schaefer! ... View more

Python treats null values as none.  And python can't add to nothing. Attribute1 = null Attribute2 =   5 Current State: Attribute1 + Attribute1 =       none     +         5         = null To handle Nulls: Use or include a default value (!Attribute1! or 0) + (!Attribute2! or 0) =                 0               +                5               =  5 Or use arcade: $feature.Attribute1 + $feature.Attribute2 =              null                 +                 5                 =  5 ... View more

I am currently experiencing the same issue.  Guess I will try again in a few hours ... View more

Try adding a new Calculate Field tool to the model, and replacing the one that is causing the error ... View more

I just had the same thing happen to me.  One of the toolboxes, just died.  Tried to open it in a new project, and no luck ... View more

@DavidSolari I apricate the tip and will give it a go.  While it does sound tedious, it is better than my plan of exporting to python hoping the error continues.  And add print prompts to annoyingly track the model. ... View more