Hi guys,
I am trying to optimize the way we allow the admin to document products and I am considering development of a custom FieldType.
The problem I want to solve is to avoid defining unnecessary fields if they are not used in comparing or filtering.
That's why I am trying to define a field, that would allow definition of several subfields. Based on the list of Subfields, I would create in the interface a list of labels and inputs, the values will be stored in the database as a JSON (or XML).
I have managed to create a proof of concept but I have stumbled on a major limitation.
Namely, the way I am able to define the list of subfields.
In my proof of concept, I have used a MultiSelect editor in the FileTypeProvider. This works well but I need to create a FieldType for every Field I want to create. It's ok for small datasets but maybe too much for large datasets (which is the case I am trying to solve).
Long story short, I am wondering if I can move the Subfield definition in the interface where I define the field. Something similar to how the ListBox field type is collecting the Options and values. I have investigated the source code but I could not figure out how I can add my custom logic in the "Options" section of the Field definition.
Is there a way to accomplish my objective? If not, can this extensibility be considered as a feature request? Does anybody else see the benefit of such functionality or such a field type?
Thank you,
Adrian