Allow Custom Column Names for Linked Record Tables in Document Designer
lorenzo
It would be incredibly helpful to have the ability to rename column headers for linked record tables within the Document Designer. Currently, the default column names reflect backend field naming conventions, which often aren't intuitive or user-friendly when presenting documents to external stakeholders or team members.
Use Case:
When creating documents that reference linked record tables, the column names often display as they are named in the backend (e.g., "Project_Assigned_User"). This format makes sense in a database context but can be confusing or unprofessional in a document setting.
For example:
A column titled "Project_Assigned_User" could be renamed "Assigned To" for clarity and readability.
This flexibility would allow document creators to customize their outputs for specific audiences, whether internal or external, without having to alter backend field names.
Benefits:
Enhances the professionalism and readability of documents.
Improves usability for external-facing documentation.
Provides document creators with greater flexibility and control over their designs.
Thank you for considering this enhancement—it would significantly improve the functionality and presentation options within the Document Designer!
Jon Darbyshire
Hey lorenzo, thanks for your feedback! I have a few more questions for you:
- What specific types of documents or reports are you creating that require custom column names?
- How frequently do you need to change column names for different audiences?
- Are there any specific challenges you face when explaining the current column names to external stakeholders?