Way too much custom fields needed, will this solution work? Our custom CRM system contains hundreds of fields (attributes) related to companies and / or contacts. The number of fields is an ever-changing thing, meaning one day we remove some, another day we add some.The overview in the backend is lost, so we need to have another solution for this. We came up with the following, but I am not 100% sure that the ‘solution’ is future proof. At the base we divide our attributes in attribute groups: e.g. machinery (group 22)At the second level we define the attribute itself: e.g. printer (attribute 155)At the third level we define the value e.g. true Our internal notation would be something like [attribute-group];;[attribute];;[attribute-value] -> 22;;155;;true This 1-attribute definition will be part of a far bigger string, values are separated with 2 pipe symbols. ( ‘||’) ( and we use double semicolons to separate group-attribute-value ) The idea is the put the complete attribute string in 1 custom field, something like12;;11