Feature Requests

Guys. Lemme preface this by saying, this is great. Love this app. So much good. So In trying to handle my phone like a camera things are ok. but when using the phone with the volume button as a shutter, i can take the photo, but i cant confirm it with the same button. it leaves me having to then click the screen and breaks flow. This would be an amazing add if the phone secondary shutter button could also confirm that. Would cut down on having to have two hands on it. Often one hand is manipulating something for a photo and having to then somehow also click the screen is awkward and fights you sometimes.

I got a request from a team member to add a search function when selecting a single choice value in a drop down menu. He said that scrolling through the list of choices was very time consuming while in the field and being able to search for one of the values would cut down on time. Is it possible to implement something like that? Thanks!

It would be great to have the ability to use a lasso style select tool to draw around and highlight visible records on app maps. Not just limited to field filters, status/dates, or screen zoom extent. Additionally, have the ability to export based on hilghlited/selected records with the lasso tool.

For example, my use case is carbon calculations using allometric equations for specific areas (forests), which inadvertently depends on tree diameter (within repeatable fields). Currently, if there is a mistake in my allometric equation. my correction on formula, would mean I would have to reopen all 200 records (and save) to get a new adjusted carbon value. This is very time consuming and could be something that can be done easily addressed through future updates or scripting.

Allow the ability to import a csv file to an existing choice list.

The ability to print/create reports for single record within a parent record rather than a a report for the whole record

Hi there, it would be useful to import file attachments during the import process. I envisage the same process as importing photos, so that if there are specific non-photo documents required per record we can bulk upload these.

It would be extremely valuable to have the ability to upload a custom PDF template and map Fulcrum fields directly onto it. When a Record Report is generated, Fulcrum would automatically fill the mapped fields with the actual record data, producing a professionally formatted, branded PDF using our own designed template. This would allow us to generate polished invoices, timesheets, work orders, inspection forms, and other standardized documents directly from Fulcrum records. Support for fields inside repeatable sections (such as line items or time entries) would be especially important. This feature would greatly improve the quality and professionalism of documents produced from Fulcrum.

I am experiencing inconsistent behavior with calculated fields that need to read values from single-choice fields located inside a repeatable section. When a calculated field (located outside the repeatable) tries to access a single-choice field inside the repeatable section via record.form_values["key"], the value is frequently returned as: An Object, or An Array(1) containing the actual value This requires complex extraction logic such as: if (Array.isArray(rateRaw)) rateValue = rateRaw[0]; else if (typeof rateRaw === "object") rateValue = rateRaw.value || ... While this approach works on the web, it is unreliable or completely fails on the mobile app, often resulting in the calculated field returning 0 even when data is present. Request to provide a consistent and simple way to access the actual stored value (string or number) of a single-choice field from within a repeatable section in parent-level calculated fields. Ideally without needing manual array/object unwrapping. Potential solution to either: Make record.form_values["key"] consistently return the raw stored value (string/number), or Provide a helper function like CHOICEVALUE_IN_REPEATABLE() or improve REPEATABLESUM() to support conditional logic based on choice fields more reliably. Additional Context: This issue is particularly painful for common use cases like conditional summing (e.g. sum hours only when rate_type = "Straight Time"). The same code works reliably on web preview but fails on mobile, creating a disrupted user experience. Using stored values (Label;value format) helps but does not fully resolve the mobile inconsistency. Steps to Reproduce: Create a repeatable section with a single-choice field. -> Create a calculated field outside the repeatable that loops through records and checks the choice value. -> Test on web (works) vs mobile app (returns 0). This has been a recurring pain point when building complex time/expense/labor forms.

I would like to be able to select multiple files and upload them to a record. I would also like this functionality to be such that I can drag and drop multiple items to a photo/video/audio/attachments field.