Hello
This post has identified a critical problem were you can only add approx. 150 custom fields to Mautic and then you hit a mariadb hard limit and can’t add any more custom fields.
https://forum.mautic.org/t/proof-of-concept-restoring-postgresql-support-for-mautic/36313/1
This optional plugin creates the concept of a custom object and is implemented in such a way that it does not hit a mariadb hard limit so you can effectively add as many as you like.
https://forum.mautic.org/t/mautic-custom-objects-plugin-compatibility/34879
My Idea’s
Add the custom object plugin into the core of Mautic code as a standard feature.
Add a custom objects to the main menu.
Allow a custom object to be linked to both companies and contacts.
Allow custom objects to be used in filter rules for segments etc.
A custom object with one field is effectively a tag.
A custom object in theory can be used as a replacement for tags.
Allow the renaming of custom objects. Tags can’t be renamed at the moment via the gui.
Continue allowing custom fields to be added to contacts and companies as they are now as it is needed feature.
Custom objects can be used for everything else and can replace tags.
The way that tags are implemented in the database is not efficient and they can’t be renamed.
Leave tags in place so users can migrate from tags to custom objects at their convenience.
Custom objects can be used for many of the things custom fields are traditionally used for etc.Tags can be replaced by custom objects.
Custom objects database schema is designed to allow for unlimited additions.
The database schema design is more efficient for running at scale.
Most of the code is already written, it just needs adding to the mainline Mautic core so it can be implemented quickly. Please add it to M7A release.
Thanks.