Latest Contributions by Bud

Survey123 Designer text fields are 255 characters long, but a new text field from scratch in AGOL is 256 characters long. This idea is to make the default text field length in AGOL and Survey123 consistent. Why is Survey123 text field 255 chars, but manually created text field is 256? ... View more

Can an ArcGIS Online Model Builder model be called by an ArcGIS Online scheduled task? Or do data pipelines do everything that a model would do? For example, run this model every 15 minutes: Find features in a Survey123 feature layer that don’t have matching IDs in an archive feature layer. Load the missing features into the archive layer. All data is hosted in AGOL.   ... View more

This idea is to automatically keep a record of the original survey submission in a separate read-only archive layer. The Survey123 features will be edited by staff (indigenous artifact data that will be shared publicly). I want to keep a record of the raw data elsewhere for future reference. It would be great if this functionality could be built right in to the Survey123 app.   ... View more

It’s my limited understanding that data pipelines can only be run every 15 minutes via a ArcGIS Online scheduled task. For a simple pipeline used to sync a small dataset, I want to run the job more often, such as every 5 minutes. Related use case: Make entire feature read-only based on attribute condition For example, if the feature is less than 15 minutes old (determined using an editor tracking field), then that means an AGOL scheduled task (TBD; limited to 15 min cycle) has not been run yet to copy the feature to a “record of original survey” archive layer. Since the feature has not been archived/copied yet (not true Esri archiving), I want to prevent edits until the feature has been archived. But I still want to see the feature in Experience Builder; I don’t want to hide it, I just want it to be read only. ... View more

I have an AGOL Experience Builder app that uses a hosted Survey123 feature layer. In the app, I want a feature to be read-only in an editor widget if a certain attribute condition is true. For example, if the feature is less than 15 minutes old (determined using an editor tracking field), then that means an AGOL scheduled task (TBD; limited to 15 min cycle) has not been run yet to copy the feature to a “record of original survey” archive layer. Since the feature has not been archived/copied yet (not true Esri archiving), I want to prevent edits until the feature has been archived. But I still want to see the feature in Experience Builder; I don’t want to hide it, I just want it to be read only. ... View more