Change the JSONLookupValue format

[teosarca]

Is this a bug or feature request?

FR

What is the current behavior?

Currently the lookup values have following JSON format:

{
	"<key>" : "<caption>"
}

e.g. integer key

{
	1000123 : "Some caption"
}

e.g. string key

{
	"CO" : "Complete"
}

What is the expected or desired behavior?

The biggest limitation of that format is that we cannot extend it... or if we do, it will be very twisted.
For that reason we shall change it to:

{
	"key" : <key>
	"caption" : <caption>
	
	// other optional attributes, e.g.
	"attributes" : { .... },
	"attributes2" : { .... }
}

The frontend shall not care about the other optional attributes, it just has to get then and pass it back when the lookup value is sent back.
e.g. the /dropdown endpoint was called and it returned some lookup values. The user picks one. The forntend shall send back the selected value including all it's optional attributes.
This is happening at the moment, but i just underline it because we need to keep this functionality.

[teosarca]

update: at the moment, i am using an intermediary solution (i.e. keeping the "key":"caption" pair as first one, but also having the "key", "caption" and other attributes).
While using this approach, it seems frontend almost work OK, but i found some cases where this is an issue.
Bellow i will list them.

Document Actions

[metas-rc]

[metas-dh]

[cristinamghita]

[cristinamghita]

[pablosichert]

Does this only affect this endpoint?

[metas-dh]

Results of IT1
tested in mf15

• all reported problems working fine now, see IT for frontend: Change the JSONLookupValue format metasfresh-webui-frontend-legacy#1327
• creation of new bpartner on the fly (https://github.com/metasfresh/db03/issues/172) also working fine
• lookup of specific product name & product number for a certain bpartner also working fine