Share
Report
4,930Hi,
what's your best practice regarding the "name" field.
When adding a new custom entity, the "name" field is always there by default and also can't be removed from the form.
But in some circumstances I don't have any use for that field and would like to remove it.
How do you use this field?
Sometimes I would at least know what to fill in the field, e.g. in the custom entity "account managers" I would add the name of the account manager. But since I also have the fields first name and last name, I would have to add the name multiple times in the import. Once for first and last name and one time combined for the field "name".
But I assume that the field "name" should somehow be unique, which it will not be, since one account manager can be account manager for multiple accounts/contacts in various roles.
(Account manager might not be the correct Translation. In german my entity is called "Betreuung", which links the contact/account with an employee. Additionally it carries information if it is the main account manager and which type of account manager. Or would connections be the better approach? But since I want to have a tab "account managers" showing all the account managers for a contact/account including all employee information, I guess this is the right approach vs. connections).
thx a lot in advance for your advise
Thomas
*This post is locked for comments
All responses (
Answers (
