Feature Requests

I want to know where a user was located when they create particular repeatable records. (We need to know during QA if they were actually near the feature they were monitoring.) I created some data event (load-repeatable) code that seemed to be working well on some records until I tested it on another record, for which I got no coordinates from these two properties: this.featureCreatedLatitude this.featureCreatedLongitude Because it had worked on other records, I ran a query to using the equivalent fields: _created_latitude _created_longitude This showed that some records had the information; others did not. I then ran another query, which suggested that the lat/long metadata are missing for records created on iOS, but present on Android. The AI support bot confirmed this, also pointing out that these metadata properties won't be available on very old records, or records created using the web app. The repeatable in question did not have location enabled, so I can see why iOS wouldn't bother recording it. However, it is useful to have this information in this case and I feel it increases the risk of serious errors and user dissatisfaction when code that works on one mobile platform breaks on another. (My original code broke with an unhandled exception when this first occurred.) This article also seems to imply that the created location is always recorded. (It doesn't say it won't be recorded if location is not enabled on iOS mobiles.) https://help.fulcrumapp.com/en/articles/2440341-location-data "The created location is the location of the mobile device when the record was initially created. This information is provided as a way for administrators to see where the user was actually located when the record was created." So I'd like to see the iOS app always record the _created_latitude and _created_longitude, even for repeatables that don't have location enabled, just like Android. I realise this won't be a high priority fix, and I can live without it, but if it's straightforward to harmonise the apps, this could save someone else more serious problems.

Example of 2 choices I would need in a choice field below: Since there was greater than a 0.1-inch deviation between manual & meter level readings, extended setup was changed with a sensor offset of X to Y <- X and Y here would need to be able to be changed after selecting this choice option by the user input to whatever values they need to enter. Since there was less than a 0.1-inch deviation between manual & meter level readings, extended setup was not changed. <- This would just be a regular choice field, no change after selection needed.

This will allow a way to tell if a generated report has valid contents or has run into an error/TypeError preventing proper generation. Workflows and API calls will still provide a PDF if there is an error, but the contents for an advanced report will only display the error. Since there is no programmatic way to tell if this has happened, we are hearing about it too long after the fact. Having a way to tell in the workflow or in the API JSON response if the PDF contents ran into an error will allow us to build in automatic checks for issues.

Please add a function in record view to duplicate a record. This is available from mobile but not in the web browser

Just your usual dark mode option for the app. We work at night doing surveys for animals, the dark screen is a lot easier on the eyes.

Can we please have the ability to format label text - ie bold; red for warnings etc.

There needs to be a way to "refresh" and re-run all data events and calculation fields without having to go into each record individually and re-syncing. This is especially true when you have big apps, and data that you import is going to have an affect on these calculations.