Importing values into a CVL (more than one language)

Avatar
Nicky Lilja
  • Updated

sections in the article

    This article describes how to import values into a CVL that has data type LocaleString (more than one language).

    Once you have set up a CVL, you need to fill it with values. One option is to do this manually, one row at a time. If there are many values, it may be more convenient to import them from Excel.

    To view defined languages

    1. In inriver Control Center, go to Model > Language. Here is a list of languages that are defined in your version of inriver.

      Note: There are language codes consisting of two letters within parenthesis, for example (es) for Spanish and (de) for German. These language codes are used in the Excel files to identify each language.

    To create the Excel file

    1. Create an Excel file with the following columns: Key, ParentKey, SortOrder, Deactivated, plus one column for each language that is needed. If you are adding values for example for English, Swedish, Spanish and German, the full column list would be: Key, ParentKey, SortOrder, Deactivated, en, sv, es, de. 

    2. Enter the key value in the cell for the Key column. >span>The ID can contain letters and numbers and must be unique within the list.

    3. Does the value have a parent value in another CVL?
      1. If no, leave the cell for the ParentKey column blank.
      2. If yes, enter the value for the Parent in the ParentKey column.

    4. Enter a number in the cell for the SortOrder column. This number determines the sort order for the values when the CVL is used in the Web Portal.

    5. Should the value be hidden initially?
      1. If no, enter false in the cell for the Deactivated column. 
      2. If yes, enter true in the cell for the Deactivated column.

    6. Enter the CVL value in the cell for the language columns. Continue until all needed values have been added. 

    7. Your Excel file may now look something like this: 

    8. If the CVL has a Parent CVL list, the Excel file may now look something like this: 

    To import values to a CVL

    • In inriver Control Center, go to Model > CVL.
    • Find the CVL.
    • Double-click on the row of the CVL you want to import values to.
    • Click the button Import CVL Values.
    • Select the Excel file that has the values you need.
    • In the dialog that opens, click Open.

    The dialog closes and the import starts. If the import was successful, you will receive a confirmation message.

    Troubleshooting the imported values

    If some values couldn't be imported, you will get an error message notifying you. If this is the case, here is how you can troubleshoot the values to see why it wasn't imported:

    • Check that all values in the ParentKey column match a value in the ParentCVL.
    • Check that the Key column doesn't contain space (for example, write UnitedKingdom rather than United Kingdom).
    • Check that the Key column doesn't contain language-specific characters (for example ê, ë, ñ, å, ä, æ, ö, ø). 

     

    Further readings

    Excel import

    Excel export

    Publish application

    Characters not accepted when importing data

    Was this article helpful?

    Still need help? contact us

    Related articles

    Comments

    3 comments

    Sort by Date Votes
    • Avatar
      Erik

      "Check that the Key column doesn't contain space (for example, write UnitedKingdom rather than United Kingdom)."
      Why is the interface (modelling tool) accepting spaces in the CVL keys if that is not allowed?

      0
    • Avatar
      Dany Raymond
      Conversation Starter

      I tried and the Key column does accept spaces. If I remember, inRiver reduced restrictions "slightly" before Erik van Zuijdam comment. I guess they just forget about updating this page.

      What seems to be an up to date page about those restrictions is: https://community.inriver.com/hc/en-us/articles/360012339693

      1
    • Avatar
      Dany Raymond
      Conversation Starter

      Google Spreadsheet users (exporting as xlsx): Many UI features seems to break the inRiver import (Fixed header, background colour, text orientation, format (including switching from auto to raw or the other way), true/false, .... Using the clear formatting doesn't seem to always work.

      So if you end up with an issue, try to create a new file without any style, copy your columns/data and paste them as raw in the new file.

      LibreOffice (exporting as xlsx): I could use formatting features and inRiver would import the file without an issue.

      (https://community.inriver.com/hc/en-us/articles/360019399913/comments/360002562379)

      0

    Please sign in to leave a comment.