While using NAS with OSYNCH parameter in a Dynamics NAV 5.0 + partnersource update 25874 or Dynamics NAV 5.0 SP1, we had to use the Localization Tips that were published on page 55 of the Setup and Installation Guide:
When a localized version of Microsoft Dynamics NAV is used, some actions are required to align the version and country codes specified in the license (.flf) and system text (.stx) files of Microsoft Dynamics NAV C/SIDE Client, Application Server, and Outlook Add-in with the localization used.
When you install Outlook Synchronization Update, the described alignment must be performed only after you have imported and compiled the Outlook Synchronization Update objects.
For the details on installing the Outlook Synchronization Update, please refer to the Installing Outlook Synchronization Update appendix.
Using SP1 this process could be easy. Using the Partnersource update, this could be a bit more difficult because at what point did you have to import the modified objects and compile them (see Note above). Using web services, this changed which is a BIG win for all of us.
When using web services, the NAS is no longer required and there is no need anymore to copy the license and system text files manually anymore. After installing everything required and after publishing the web service in NAV, the following error will show up in the Outlook Add-in:
NST Asynch Call completed with Error: Microsoft.Dynamics.Nav.Types.Exceptions.NavCSideException: A ‘=’ is missing in TransferFormulaData. WHERE(Soort=CONST(-1),Verkoper=CONST(EMS)); .
NOTE: example has been taken from Dutch NAV 2009 CTP4.
This is an error coming while executing the web service call to the NST (NST Asynch Call). The message we are receiving is in english, therefore it means the NST its working in english and you are filtering using translated field values in Dutch, e.g. Verkoper (Salesperson).
This means that you need to change the language of the NST. You do that through the Role Tailored Client, so no stx file mambo jambo anymore 🙂
One thing to keep in mind though, is that the values of the filters you put in the entities, are language dependent. That means that they will not change values if you suddenly change the language of the NST or NAS or classic client. You can test this on a local build by, first opening NAV on the language of the local build (let’s say Dutch) on a fresh database, open the Outlook Sync. Entities or Outlook Synch User Setup tables. This will populate default values in the current language. Now, change the language into English, you’ll see that the field values are still on the local language. This can be solved actually but is a new feature.