Can you display the label(not the code) of a LOV in a display card?
Best Answer
M
Matthew AMMONS
said
about 1 year ago
Alexia,
We no longer use Semarchy's LOV functionality. It's limited functionality and the fact that you have to promote the model through the environment if you need to update the values has pushed us to create a LOV entities. This allow us to update the values as needed without promotion of the models. We've created it in our reference domain and push the entries to the other domain upon creation, edit, or deletion of an entry. We lose the functionality of making it a multi value comma separated field but we are ok with that.
First you create a entry in the LOV List entity. This is where all the List names are stored.
Then you create the values for the list in the LOV List - Values entity.
This is our workaround and it seems to be serving us well.
It is not currently possible, but we have an internal request on the topic.
If you want me to communicate you the reference, I can convert this topic into a ticket.
Otherwise, what I can see in the meantime, would be to go retrieve the label from within the repository.
Please let me know if I can help further.
Have a good day. Alexia
M
Matthew AMMONS
said
about 1 year ago
Answer
Alexia,
We no longer use Semarchy's LOV functionality. It's limited functionality and the fact that you have to promote the model through the environment if you need to update the values has pushed us to create a LOV entities. This allow us to update the values as needed without promotion of the models. We've created it in our reference domain and push the entries to the other domain upon creation, edit, or deletion of an entry. We lose the functionality of making it a multi value comma separated field but we are ok with that.
First you create a entry in the LOV List entity. This is where all the List names are stored.
Then you create the values for the list in the LOV List - Values entity.
This is our workaround and it seems to be serving us well.
Thanks,
Matt Ammons
A
Alexia SIMOND
said
about 1 year ago
Hello Matt,
That is also a way to do it :)
And it is much more adapted to list of values that move in time.
It is true that we recommend using the Semarchy LOV only for closed ones that don't evolve in time (or not too much).
Glad to hear that your approach is answering your need.
Matthew AMMONS
Can you display the label(not the code) of a LOV in a display card?
Alexia,
We no longer use Semarchy's LOV functionality. It's limited functionality and the fact that you have to promote the model through the environment if you need to update the values has pushed us to create a LOV entities. This allow us to update the values as needed without promotion of the models. We've created it in our reference domain and push the entries to the other domain upon creation, edit, or deletion of an entry. We lose the functionality of making it a multi value comma separated field but we are ok with that.
First you create a entry in the LOV List entity. This is where all the List names are stored.
Then you create the values for the list in the LOV List - Values entity.
This is our workaround and it seems to be serving us well.
Thanks,
Matt Ammons
- Oldest First
- Popular
- Newest First
Sorted by PopularAlexia SIMOND
Hello Matthew,
It is not currently possible, but we have an internal request on the topic.
If you want me to communicate you the reference, I can convert this topic into a ticket.
Otherwise, what I can see in the meantime, would be to go retrieve the label from within the repository.
Please let me know if I can help further.
Have a good day.
Alexia
Matthew AMMONS
Alexia,
We no longer use Semarchy's LOV functionality. It's limited functionality and the fact that you have to promote the model through the environment if you need to update the values has pushed us to create a LOV entities. This allow us to update the values as needed without promotion of the models. We've created it in our reference domain and push the entries to the other domain upon creation, edit, or deletion of an entry. We lose the functionality of making it a multi value comma separated field but we are ok with that.
First you create a entry in the LOV List entity. This is where all the List names are stored.
Then you create the values for the list in the LOV List - Values entity.
This is our workaround and it seems to be serving us well.
Thanks,
Matt Ammons
Alexia SIMOND
Hello Matt,
That is also a way to do it :)
And it is much more adapted to list of values that move in time.
It is true that we recommend using the Semarchy LOV only for closed ones that don't evolve in time (or not too much).
Glad to hear that your approach is answering your need.
And thank you for sharing it to the community.
Have a good day.
Alexia
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 346 topics