Latest Contributions by Matt-Goodman

Thanks for confirming. I ended up setting up a basic hosted table with edit-tracking fields, shared to the appropriate permissions group in ArcGIS Online, then using it in a super-simple Experience Builder app that includes an 'edit widget' in a collapsing panel. I wish it a was a little more configurable, but it sort-of does the job.      ... View more

Thanks for this response - I wasn't aware of the Discussion Boards functionality. Another potential reason to subscribe to Premium. ... View more

I found this documented elsewhere, but essentially... change the .loz file extention to .zip unzip it find/edit the file you're looking to change zip up all the files again, making sure to use "Store" compression level for the .zip change the output .zip file extension back to .loz ... View more

I edited the buildconfig.json in the .loz file (just deleted the PARCEL_JOIN_ID and FULL_STREET_NAME sections) and re-zipped the .loz.  Now the script runs as expected as well as the gp tool.  ... View more

Genius, thanks @ShanaBritt!  I think it was that parcel join that was fouling things up....I didn't set that up intentionally, it must have carried over from a join I had in the project the last time I re-created the locator. Anyway, my arcpy script to rebuild locators is working smoothly now. Thanks again! ... View more

3.3.5 "mapping_schema":[ { "role_field":"HOUSE_NUMBER", "mapped_field":"ANUMBER", "display_field":"Address Number" }, { "role_field":"STREET_PREFIX_DIR", "mapped_field":"LST_PREDIR", "display_field":"LST_PREDIR" }, { "role_field":"STREET_NAME", "mapped_field":"LST_NAME", "display_field":"LST_NAME" }, { "role_field":"STREET_SUFFIX_TYPE", "mapped_field":"LST_POSTYP", "display_field":"LST_POSTYP" }, { "role_field":"STREET_SUFFIX_DIR", "mapped_field":"LST_POSDIR", "display_field":"LST_POSDIR" }, { "role_field":"FULL_STREET_NAME", "mapped_field":"LST_CONCAT", "display_field":"LST_CONCAT" }, { "role_field":"SUB_ADDRESS_UNIT", "mapped_field":"SUB_ID1", "display_field":"Subaddress Identifier 1" }, { "role_field":"SUB_ADDRESS_UNIT_TYPE", "mapped_field":"SUB_TYPE1", "display_field":"Subaddress Type 1" }, { "role_field":"SUB_ADDRESS_BUILDING_UNIT", "mapped_field":"ANUMBERSUF", "display_field":"Address Number Suffix" }, { "role_field":"PARCEL_JOIN_ID", "mapped_field":"PropertyID", "display_field":"PropertyID" }, { "role_field":"CITY", "mapped_field":"POSTCOMM", "display_field":"Postal Community Name" }, { "role_field":"SUBREGION", "mapped_field":"CO_NAME", "display_field":"County Name" }, { "role_field":"REGION_ABBR", "mapped_field":"STATE_CODE", "display_field":"State Code" }, { "role_field":"POSTAL", "mapped_field":"ZIP", "display_field":"ZIP Code" }, { "role_field":"COUNTRY", "mapped_field":"COUNTRY", "display_field":"Country" } ]   ... View more

I think I'm bumping into the same issue. IDK, might be version issues between locators and db?  The reference data is in an enterprise SDE db. I'm signed-in to our enterprise licensing through Portal.  S ... View more

Still don't have any idea what's going on.  I tried a fresh/clean .aprx with just one single SDE data set in it. I ran this Select By Attributes looking at an integer field, [mar_id] and the application was basically incapacitated for over an hour (I quashed it to go home for the day). It did, after about 40 minutes, return the message stating "The SQL expression is valid, but no records were returned." But even after that message, I was stuck with limited functionality as the 'processing' cursor continued to spin. Even after closing the Select By Attributes dialog, the cursor remained and context menus were all grayed-out.    ... View more

As I dig in deeper, I'm starting to think I have a uniquely glitchy bug.  Starting with a totally clean project/map, with only one single feature class I can get the query to work normally, especially when I intentionally put duplicate ID attributes for it to select. I can run the Select By Attributes and it will select them. However, when I run or validate the query while there are not any duplicates present for it to find, it behaves abnormally: When validating (clicking the green check mark) it returns a message that the query is valid, but it does not also give the usual message stating that no records were returned. When executing the query, it appears to do nothing and then when closing out of the Select By Attributes dialog, the cursor turns to the "processing" wheel indefinitely (or at least for more than 30 minutes, which is debilitating).    So far the only field that seems to cause this issue is the ID field that I'm trying to check, which is a 36 character UUID (but not an Esri GlobalID and not managed by the database). I can perform the same test on, for example, the address number field, and it successfully selects the many duplicate address numbers. ... View more

The feature class is not versioned. The project is pointing at the default. ... View more

Good clarifying questions, @JoshuaBixby ... The enterprise geodatabase I'm querying is Microsoft SQL, a ArcGIS Pro 3.3.2 Enterprise geodatabase (upgraded from 10.7.1 in February). When I run this SQL query in ArcGIS Pro, I get the spinning cursor (processing) and it never resolves. I have to use Windows Task Manager to "End task" and restart the software.  The query does run as expected when it's executed in SSMS on the exact same data table (query syntax has to be slightly modified for that use).  ... View more