Best way to store EAV data

[KoenJanssensPD]

Dear,

For the Contacts table, we would like to be able to capture a lot of attributes (like properties on the Products table). We would like to define tens of attributes, which some are mandatory and others are optional. In the future, is has to be possible the end users can add additional attributes to capture other information about contactpersons.

Creating a field/column for each attribute is not flexible and can only be done by System Customizers...

I could create an EAV model, with a table "ContactAttributes" and a table "ContactAttributeValues"... However, I wonder if there is any other out of the box functionality (like the dynamicproperty table for products)?

Thanks,

Koen