Latest Contributions by DavidSolari

Pro uses Conda instead of pip/pypi for package handling and I doubt this will change in the near future. I think the Conda version of what you're doing is called a "private channel", the official docs might help here. This has the added bonus of letting you grab a package and all its dependencies from pypi and hosting it, avoiding the usual issues with outdated packages. ... View more

Attribute rules do not perform any updates if you return with no value, so if you throw this at the top:   if (!IsEmpty($feature.FullStreetName)) { return // Do not replace existing data }   Then the rest of your code can run below. As an added bonus, you've guaranteed "FullStreetName" is an empty value which can simplify your logic a bit. ... View more

To expand on this, if you have access to attribute rules you can use that as well. You'll want to run some tests to see if the cost of calculating the value on feature insert/update is less than just calculating it through arcade. ... View more

Trying to override React's layout system with the useEffect hook is a very bad idea, React has no idea you're moving the widget around the DOM so it'll constantly try to snap it back to its stored position. It seems like you're trying to pet the dog backwards here, if you create a custom widget controller that has position overrides you'll get something that works for any widget and allows your widget to be used outside of a controller. If you absolutely must do this through the widget itself, try looking into the useRef hook to capture the appropriate chunk of the DOM, then override any events that can reposition the widget. ... View more

Breaking arcpy backwards compatibility to fix ill-defined logic issues is at the bottom of ESRI's priority list. You'd be better off posting the actual problem you're trying to solve in one of the communities, chances are there's a fix for whatever the root issue is. ... View more

You can check this section of the Survey123 docs for more info. Note that layer queries are flaky at best (and unusable at worst) if your users are working offline, if you need offline support then you'll have to regularly update a hosted CSV file that you link to the survey form.  ... View more

Normally this is our workflow, but in this case we do want users to make geometry edits from time to time. The issue is the vertex editor being active by default in all cases, when we'd prefer an "opt-in" workflow for some maps where these edits are infrequent. ... View more

Haven't tried something like this myself, but combining the Extent, Polyline and NearestCoordinate functions might work. ... View more

There's a lot of "it depends" here but the RMS fields are the must have fields, there's virtually no reason to bother with GNSS metadata without them. ESRIGNSS_POSITIONSOURCETYPE is also a big one, this is what confirms that your users are using the equipment. The DOP data is less useful in my experience, but I'm sure someone who's spent more time with GNSS workflows can correct me here. ... View more

At first thought, the easiest solution is to pin the required Python versions to the supported versions of Pro when the Conda package for the esri channel is built. The Pypi and non-esri channel Conda packages can continue to list a wider range of Python versions as that's not what Pro's package manager will look for. ... View more