I agree! Having more fields would be extremely helpful, and I also think some of the fields can be renamed for clarity. Here are some additional field suggestions that our team would find valuable:
Current Date
Document / Date / Created
Document / Date / Last Updated
Document / Author / Created - Name
Document / Author / Created - Phone
Document / Author / Created - Email
Document / Author / Created - Role/Position
Document / Author / Last Updated - Name
Document / Author / Last Updated - Phone
Document / Author / Last Updated - Email
Document / Author / Last Updated - Role/Position
I hope you don't mind me piggybacking on this post with another suggestion related to dynamic fields! (Happy to create a separate post if preferred.)
- Currently, dynamic fields only pull in their referenced data once – either when a document is created from a template or when the field is first inserted.
- I believe dynamic fields should automatically update whenever their referenced data changes. To me, that's what makes a field truly dynamic. Otherwise, it's essentially a static or fixed field.
- For example, if a document's title changes, the Document Title dynamic field should automatically reflect that change (which is actually how the Document Title used to work).
- The same should apply to fields like Project Name, Project Address, Customer Name, Customer Address, Customer Phone, etc.
- Without this functionality, users have to update the same information in multiple places. For example, changing a Project Address should automatically update that field in all existing documents referencing it, rather than requiring users to open each document and manually make the same change. Additionally, field users on mobile devices don't have access to
- Ultimately, dynamic fields should maintain a live connection to their source data, not just populate information once.