Skip to Main Content
Categories Enrich
Created by Guest
Created on May 15, 2023

Localize CVL value

This post is not about translations!

Sometimes, CVL values might be different from country to country, even region to region. To avoid always creating placeholders for each and every individual exception case, which often quickly leads to an explosion of fields, I would suggest the following:

In the above overview I've added a plus button which provides you the possibility to add regions (potentialy this could also be a CVL). So once you start adding additional regions/countries, you can start to localize your CVL value.

This would lead to a reduction of datafields but still providing you the possibility to localize a certain CVL field where needed and avoids going trough a whole list of "potential" placeholders.

  • Attach files
  • Mark Stuart-Walker
    Reply
    |
    Sep 1, 2024

    Wouldn't this be better handled with a large CVL with parent divisions for each region? The CVL could be maintained from a list of entities with my CVL Entity idea.
    https://customercommunity.ideas.aha.io/ideas/INSE-I-268


  • +1