Ideas

Hello Johan!
First of, let me ask this: Why wouldn't you fully support the field framework in an API that lets you manipulate the entities?
Somewhere along the line you've obviously identified the need of grouping fields in a container and having it grow dynamically hence creating the MultiField type in Litium, so why not have proper support for it?

In our specific case we're working with logos and print files that are migrated from the ERP into the PIM. We need to save every color that existed on the logo together with and ID and its actual color values like RGB and HEX. This is in my opinion a primary case for using MultiField rather then using some hack where you save everything in an editor with separators for example.

Sure it might be possible to handle it through the Admin API in theory, but in practice the admin API is awful to use and in my opinion the Connect API misses the mark if you are forced to use another API to do a complete transaction.

Further, the product import/export seems to be missing support for MultiFields making it very hard for our customer to handle more complex product data outside of working in Litium BO directly. With that in mind, maybe a better name for this request would be "Please add proper support for MultiField across all aspects of Litium".

If you feel like this doesn't belong in the Connect API, which I would disagree with, then maybe it is time to create a more flexible and user friendly alternative to the Admin API.

Hope this answered your question. Let me know if you want to discuss this in more detail.

It would be interesting to know more about the use case for this. What kind of data in the ERP do you need to represent as a multifield?