Data lists in aspects?

[itzamna]

Hi engineers,

first of all, I'm not sure if this topic is related to the current sub-forum or if it more belongs to the content modelling. Maybe its a mix.

I've the following requirement, that should be solved:
A job periodically receives via an interface some data from a remotly connected system. These data will be stored in properties and the properties belongs to a custom aspect. The aspect will then be added to the affected document.
Now, the remotly system provides -in addition- to the known basic properties also the possibility to return a table with an unknown number of different properties. At the end, the content of the table will be parsed to a simple KEY-VALUE hashmap by the interface. So we can make sure that the table (or data list?) will have always 2 columns but an unknown number of rows. The number of rows in the table can vary by each document.

Now the question:
What is the best way to display a table content (a varying key-value map per each document) in the document properties? Since it technically belongs to the same aspect where the basic properties are visible, it should be displayed also in the aspect.
Please see the attached image. I hope with it, the problem will be a bit more clear.


BR,
Itzamna

[jpotts]

Store your data however it makes the most sense to you. Some people will use JSON. Others use a multi-value field with the key and value separated by a special separator. Then, write a custom form control using freemarker that takes your data and displays it how you wish. The custom form control is bound to your special data field through Share form configuration.

Jeff

[mrogers]

Or you can store your ad-hoc properties as "residual" properties.   That is properties in a namespace which do not have a definition.  You can then pattern match to display them in the ui. 

It's another option.