Hello Nicolas,
As named queries are used to propagate data, we need to ensure data integrity.
As LOV labels are not unique, it could lead to data discrepancies, hence why only codes are available in named queries.
But it could be an interesting use case to bring to the product team.
So I will convert this into a ticket, for you to let me know more about your use case.
That being said, depending on the use you are doing of this named query, there could be some workarounds, that could interest others.
On top of my head, I can think of a function that would bring the LOV codes' labels.
But as it is a custom solution, it will have its benefits and disadvantages. Especially, that this function will be called for every LOV for every records present in the named query. Hence it could lead to lengthier execution times.
Please let me know if you need more information.
Best regards,
Alexia
Hi Alexia, thanks for your answer.
I was just asking if it was planned to do this enhencement, as i came to the same workaround.
I created a function that queries the LOV label from the MTA_LOV_VAL table.
Thanks a lmot for your quick response,
Best Regards
Nicolas
Hello Nicolas,
As mentioned over on the ticket, as this use case may interest others, we have create an internal ticket MDM-16957 for that purpose.
In the meantime using the function to transcode your LOV codes into values should answer your need.
Thank you for reaching out on that topic, we appreciate your collaboration.
Have a good day and take care.
Alexia
Nicolas KEIM
Is it possible to add Semarchy LOV's label text to named query instead of code value?