Today I ran into problems with the language in the enhancements of the NAV adapter.
I changed the language from ENU to NLD (Dutch) and the following happened.
- The table names in the staging database were changed to Dutch apparently using the captions stored in the NAV database.
- The fields names in the staging database were changed to Dutch apparently using the captions stored in the NAV database.
What did not change!
- Transformations and conditions that are using table fields still use the original field names.
- Scripts and Stored Procedures are still using the original fields.
Altogether the conclusion can be drawn that one does not want to change the language and leave it on ENU.
Why would one want to change the language?
Because of the tables with the options (NAV_Option_…). The content of the field 'Option_Text' is in ENU, but one wants to have it in the native language. In this case being NLD.
Date
Votes
1 comment
-
Jet Reports Historic Posts Hello Willem,
Thank you for the feedback. I will put in a request for the transformations and conditions for a future version, but the scripts and stored procedures are hand typed and therefore wouldn't be subject to the language settings in NAV. These will always have to be changed manually.
Please sign in to leave a comment.