Latest Contributions by CalvinHarmin

@RichardLittlefield I could see that working for some use cases. In my case this would not be a solution for a custom asset ID field, as I have an hosted feature layer (Pole, point) that is related to another hosted feature layer (Sign, table) with the custom asset ID field being the key. So the Pole must have an asset ID before a sign can be created. Or, in other words, an existing Pole feature must be selected, and there is an option to create a related sign record from that pole feature using the asset id field as the key. The field work includes taking pictures of the pole and selecting attributes, and then creating a sign asset attached to it and taking pictures and creating attributes for the sign, etc. It must be done right there in the field and can't (realistically) be accomplished after the fact, or it would require multiple field visits to the same location at another time after the notebook script has run. OBJECTID-based asset id integer from an arcade expression also doesn't work since oid is not generated until the feature is submitted to AGOL. The arcade expression can't calculate after submission, it is calculated before. ... View more

@KevinMayall  We have this frustration as well with AGOL hosted feature layers -- no ability to use a 'database sequence' type of integer auto-incrementing for the purposes of asset ID generation. There is an arcade expression that almost gets there by calculating the 'max' integer of the existing asset ID field. However, if more than one person is in the field (or office) adding new features, they will both be trying to save a new feature and both will have the same asset ID since in both cases the 'max' asset ID of the existing data is the same at the time they started created the new feature. This means one of them will 'lose' if the other saves first, and they have to cancel that feature creation and start over.  Here is the arcade expression I've applied for my 'POLE' hosted feature layer with asset id field named 'POLE-ID'. Hopefully the rest is self-explanatory. I believe the original source of this arcade expression was from the Sign Management solution. I found the solution helpful as a starting point but went in a different direction since the solution has way more functions than I care about and I wanted to have my related SIGNS assets in a table format and not a point layer format. Anyway, I'm just sharing this example in case your use case doesn't have multiple editors at once, it might work for you.   var layerIndex = '0'  // PW_Pole is the layer reference '0' in the AGOL Hosted Feature Layer service; PW_SIGN layer reference is '1' var idField = 'POLE_ID' var idPrefix = 'POLE-' var digits = 5 /*DO NOT CHANGE ANYTHING BELOW THIS LINE -------------------------------------------------------------------------*/ function GenerateWildcards(digits, wildcard) {   var wildcards = ''   for (var i=0; i < digits; i++) {     wildcards += wildcard   }   return wildcards } function GetNextId(layerIndex, idField, idPrefix, padding, sqlFilter) {   // get the feature with the greatest assetid that matches the id pattern specified in the SQL statement.   var assetid_features = Filter(FeatureSetById($datastore, layerIndex, [idField], false), sqlFilter)   var max_assetid_feature = First(OrderBy(assetid_features, `${idField} DESC`))     // If no features match the pattern the featureset will be null, return the first assetid   if(max_assetid_feature == null) {       return `${idPrefix}${Right(padding, Count(padding)-1)}1`   }   // when features do match the pattern calculate and return the next assetid     var max_assetid = max_assetid_feature[idField]    var next_assetid_number = Number(Replace(max_assetid, idPrefix, "")) + 1   return `${idPrefix}${Text(next_assetid_number, padding)}` } // Define the edit context so the value is only calculated when the feature is created if ($editContext.editType == "INSERT") {   // return matching prefix pattern and get next value   var wildcards = GenerateWildcards(digits, '_')   var padding =  GenerateWildcards(digits, '0')   if (idPrefix != '') {     var sqlFilter = `${idField} LIKE '${idPrefix}${wildcards}' AND ${idField} NOT LIKE '%[^0-9]'`         GetNextId(layerIndex, idField, idPrefix, padding, sqlFilter)   } // return number id's only and get next value   else {     var sqlFilter = `${idField} NOT LIKE '%[^0-9.]%'`         GetNextId(idPrefix, padding, sqlFilter)   } } else {   return $feature[idField] } ... View more

I agree that an addition of a 'native' sum of length/area of selected features in the UI (attribute pane maybe?) would be useful for me as well. Showing multiple areal units in addition to the base map unit at the same time would also be useful in my case (i.e. sq. ft, acres, sq. miles) Aside from the Data Engineering view, I have found the closest thing to a dynamic view is to right-click the field you want to SUM in the attribute table, choose Visualize Statistics, and this creates a 'chart' element for that layer. When more than 1 feature is selected in that layer, the Chart Properties will show a SUM of the selection in addition to the statistics for the total of the dataset. If you only care about SUM of area or length field then setting a Bin of 1 may speed up the calculation.       ... View more

That makes sense. It feels like the whole archiving and historical management has not gotten any love in a couple decades. I think there could be a lot more helpful tools that could be made to improve management and usefulness of it.  ... View more

That's really unfortunate that there was no warning for you. I know that when archiving is purposefully disabled, you get the option to 'Preserve' the history table or delete it. I wonder if it created a <layername>_H object in your geodatabase that could still be used for historical purposes (although can't be 'restored' as the active Historical table). But it seems your notes indicate that since you chose 'dont preserve' the related historical table, so it also fully deleted the one you care about? ... View more

In my case the need/desire for stacked labels is ubiquitous. For my use case, it's more of a question of where I don't want stacked labeling as an option. But off the top of my head the most common labeling I would like to be stacked are Street names, full Addresses, Subdivisions, pretty much any location/name or string attribute. For certain concatenated/ more complex labeling using an Arcade expression I can at least use "\n" or TextFormatting.Newline to split labeling manually if using multiple fields.  ... View more

AGOL can only reference a custom locator service published from Server, not host one itself? EDIT: https://doc.arcgis.com/en/arcgis-online/manage-data/create-locator.htm I guess not 😞  I was hoping to duplicate my locator on AGOL for Survey123 usage to avoid issues where our local server may have downtime but still allow public to complete Survey123-based requests that have an address-validation step using the custom locator.  ... View more

In my case I found that publishing a feature service with 'two fields' option is not supported (e.g. for an enterprise geodatabase feature class published as feature service with editing enabled); in that case, one needs to use the expression option instead. This expression will then populate all of the symbology permutations available from the current data and can be manipulated (grouping, change labels, etc.) in the same way as using the 'two fields' option.    ... View more

Thanks, that's a good consideration. When we start migrating to b.v. we will probably follow this advice and keep branch and traditional objects in separate databases to avoid confusion. ... View more

One thing to consider/prepare for is that if you previously used Python workflows with arcpy geoprocessing tools including UpdateCursor and all the other tools that performed any editing operations on a traditional or non-versioned feature class or table -- those will no longer be able to perform those functions on a branch-versioned object, and you would need to re-write processes with ArcGIS API for Python or some other means. In my testing the ArcGIS for Python API methods may not be as efficient for certain workflows, but I didn't quantify it so I'm not sure if that would be a significant impact. But at least on my end, I have pushed the migration to branch versioning until I have time to be able to rewrite some rather complex automations that rely heavily on arcpy.  ... View more

Just want to clarify that branch versioning is not applied at the enterprise geodatabase level, but at the dataset or feature class or table level. So you can have mixed Traditional and Branch versioned objects in an EGDB.  ... View more

Thank you all -- this happened to me randomly just now in my main public web map! I performed the portal item Enable Search / By Layer toggle on/off and it fixed the issue for me immediately.  ... View more

Are you using Python to do the API calls and get the JSON response? ... View more

Linkie to patch page info for convenience: https://support.esri.com/en-us/patches-updates/2025/portal-for-arcgis-11-5-web-applications-patch ... View more