Latest Contributions by DavidSolari

Would be nice to have this as an app-level setting that can be locked off during installation, I'd hate to troubleshoot something a junior tech did because "the computer told me to". ... View more

Manipulating the clipboard like that is a faux pas for user-level programs on any OS, let alone Windows so I doubt it'll ever happen. I recommend keeping a text editor open so you can copy some simple text to clean the clipboard yourself, like a painter rinsing their brushes ... View more

Last time I checked, the Data Access Cursor types return BLOB columns as memoryview objects. The docs for PIL's Image.open function say it can open any file-like object that holds binary data. If you're lucky you can just shove the memoryview in there, if not you can do something like:   from io import BytesIO from PIL import Image with arcpy.da.SearchCursor(data, fields) as cur: for row in cur: data = row[index] photo = Image.open(BytesIO(data))   I think the issue with the code above is you're decoding the binary data to base64 which is tripping up PIL, assuming your images were added to an attachment table through the standard ArcGIS methods the data is stored byte for byte without any special encoding. ... View more

Would Contingent Values solve this issue for you? ... View more

if not arcpy.GetSigninToken(): fail() portal = arcgis.GIS("Pro") ... View more

The logical endpoint of this is the geoprocessing modules feature, which allow you to bundle your Python toolbox(es) as members of a standard Python package. There's a very big learning curve and you're forced to deal with Python's perpetually half-baked build systems but your reward is a fully managed, easy to read bundle of code that you can load into different environments, complete with proper dependency management. And the toolboxes are accessed just like system tools which is pretty slick. Just watch out for using them in web tools, that's a whole other can of worms. ... View more

Our team has a project that requires all attachments have a very specific name based on a field in the parent feature. We currently "solve" this using a Python cursor to ensure all attachments are named correctly. Not only does this take several hours to chew through the table but every renamed attachment creates a new record in the archive table, effectively doubling the size of every attachment. Enforcing the proper name via Arcade at the database level would solve all of these issues. ... View more

I haven't found a way to do this in Survey123 alone, but if your survey data is backed by an Enterprise Geodatabase you can use Attribute Rules to flip the read-only switch on submission ... View more

It looks like the "modified" property on each service item aligns with when it was last updated. You'll get some false positives for items that were edited after the service was overwritten but this should be good enough for most purposes. Take another look at Carsten's code for tips on getting the date out in a readable format. ... View more

This is symptomatic of a bigger problem, which is that everything in Field Maps works off the Smart Form definitions and the APIv4 popup definitions except for Edit Multiple which reads the APIv3 popup definitions (i.e. the "fieldInfos" object at the root of the "popupInfo"). I have a sneaking suspicion this is related to the lack of standardized multi-feature editing in the new API somehow, but either way updating Edit Multiple to use the Smart Form definition is a must, there's no reason for the editing workflows to be disjoint. ... View more

Tweaking a layer based on the current datetime relative to a field in the layer is a common request in my org. Usually it's a symbol that we set using Arcade but filtering comes up too and jumping into AGOL Assistant is less than ideal. ... View more

Is your data in an EGDB? You can write a database view that UNIONs every layer into 1 big table with a "score" field, something like:   SELECT ROW_NUMBER() [OBJECTID], tbl.[LayerName], tbl.[Score], tbl.[Shape] FROM ( SELECT 'Layer1' [LayerName], 1 [Score], Shape FROM A.B.Layer1 UNION SELECT 'Layer2' [LayerName], 1 [Score], Shape FROM A.B.Layer2 ) tbl   You'll have to find the appropriate function to get a unique row number for your database, here's some info for SQL Server. Once the view works you can register it to the EGDB, publish it as a layer and drop that in your app for use with widgets. ... View more