SMS Number is a perfect example. I really want to rename to Cell/Mobile Number.
If I have less technical staff using the back end interface, I really want to minimise the amount of "oh this looks like this but really means that" training I need to do and make things more intuitive.
Aware I can do this on forms, but it's also extra work to do that every single time, and less consistent vs renaming the field.
Post
FollowAllow settings changes on default fields
Present Situation:
Certain fields can't be edited or deleted, e.g. First Name & Last Name.
However, this also means those fields can't be made mandatory.
Proposed Solution:
Make those fields editable, but not deletable.
Example Use Case:
Syncing with external services that require certain data to work. e.g. Cliniko requires First Name, Email & Birthday. At present, I can't make those mandatory, so I have to implement workaround exception reports.
Forms with mandatory field settings don't help if the contact is being entered directly in the interface or other synchronisations (e.g. Google Contacts via PieSync).
Please sign in to leave a comment.
1 comment
Comment actions