Field: Culture

In case the above table was how our culture table looked for a site, we could put in ‘2’ or ‘en-GB’ in the excel cell and the culture of the user would be set to English. User can mix mapping using Number (ID) and character in the same import!

To update this field for existing users, you must map the import using the User_Id column to show which users to update for. If you are updating existing users’ cultures you are forced to update all of the users in your excel. The system will not recognize NULL as an acceptable value and instead update the existing users to get the default system culture and overwrite their existing culture. |- align="left" valign="top" | style="border: 1px solid #010101" width="168" | Auto mapping | style="border: 1px solid #010101" width="1021" | In order to ensure auto mapping then the column name in the Excel must fit with the given name in import. This name is language dependent as shown:

UK: Culture

DK: Kultur |- align="left" valign="top" | style="border: 1px solid #010101" width="168" | Validation | style="border: 1px solid #010101" width="1021" | The value imported to culture (either number or character (ISO code) must exist in the table ‘culture’ of the systems database or an error will occur. Error type: ERROR (the import job will not be allowed to be executed).

If number and culture-code is mixed in one excel column, then the system will try to convert iso-code to id number. If some cells do not follow the chosen method they will be considered as ‘empty’ and ‘DefaultCultureForImportedUser’, as described in the ‘web.config’file, will be used as the culture of the imported user. |- align="left" valign="top" | style="border: 1px solid #010101" width="168" | Notes | style="border: 1px solid #010101" width="1021" | If the value in your excel cell is empty, the system will use the ‘DefaultCultureForImportedUser’ setting, as described in the ‘web.config’ help file, as the culture of the imported user.