Feature Requests

Current Challenges: The Historical Records API returns the complete history with no way to retrieve only recent changes. There is no filter for: history_change_type history_created_at The Records API updated_at timestamp does not reflect delete events. Incremental synchronization requires downloading and processing the entire history dataset repeatedly. The solution does not scale well for large production environments. We would appreciate one or more of the following enhancements: Option 1 (Preferred) Add filtering support to the Historical Records API, for example: history_created_at >= <datetime> history_change_type = deleted Other date range filters for incremental synchronization This would allow clients to retrieve only the records that changed during a specified time period. Option 2 Update the updated_at field in the Records API whenever a record is deleted. This would enable integrations to detect delete events using the existing incremental synchronization logic without requiring a full history scan.

Hello, can you give repeatable field types in the browser the option to have filters similar to other fiel types. see attached photo exampls

In addition to the option for grouping layers, another related option would be the ability to turn map layers off within the web-based version of Fulcrum, which would then shorten the list that users see in the field (rather than scrolling through 20+ layers that aren't relevant). So adding an eye icon next to the download, edit, delete icons would allow us to easily make them visible/not visible in the field. Thanks!

A tool that would allow straight-line measurements between points and between points and elements of background layers. This is a consistent complaint from our field crews about the app because not having one is hindering their in-field decision-making abilities.

Provide an option to allow automatic task/issue creation based on certain criteria being met in an app.

Sometimes drafts are created in error or cannot be avoided. From that point, if they cannot clear validation they either have to be forcibly adjusted to sync at which point there is bad data being uploaded or may override correct data. It's possible to delete the point entirely from the mobile device but in my experience this creates other issues. The ability to simply discard a draft on mobile devices would be fantastic.

Allow us to be able to use private feature service layers from ArcGIS as Map Layers using ArcGIS's built-in access tokens as authentication. Some users don't have a license to our ArcGIS but still need to be able to see some of the data, so it would be helpful to just use access tokens for non-arcgis users to be able to see the data without needing an account to log into ArcGIS

The iOS app has a feature parity gap

Using Workflows or a feature of similar nature, allow for Tasks and Issues to be auto populated using information gathered from apps.

We have text fields which store UUIDs or similar which are non-editable. Having the ability to select and copy this data would be very helpful, better yet would be a copy button to add the field entry to clipboard (mobile device)