It would be beneficial for field names to be specific to apps rather than to pages / screens. This would help with custom PDF development, 3rd party integrations, and most likely ZAPs. If this was the case, we could move fields from one screen to another when / if needed without breaking any outputs or integrations that depend on screens.
An even bigger / more pie-in-the-sky idea would be to have the ability to control the significance level of a field by being able to select global / company, group, app, or page/screen for the level at which the field must be unique and / or could be used for potential cross-app integrations, etc. in the future. That would be very cool.
4
Comments
Please sign in to leave a comment.
That seems crazy complicated on the programming side, but there are probably some universal fields (contact info, date, time, user) that could be universally accepted as 'standard' fields and able to be global/group/app etc... that would make product integrations much easier and repeatable.