mibuso.com
Home› NAV Three Tier
Options

How-to force NAS to use a specific language in NAV2013

kasper.jensen@logica.comkasper.jensen@logica.com Member Posts: 5
edited 2013-05-17 in NAV Three Tier
I am running a support case with MS at the moment as controlling GLOBALLANGUAGE in NAS via Job Queue does not work in NAV2013 :-(

I have an international client where the Danish product dvd where used for the base installation. Afterwards additional languages for NL, FRA etc. have been installed.
When Job Queue is running it is in Danish which also means that the English user does not understand the runtime errors captured in the Job Queue Entry Log - is there some kind of setting or dll file I can swap on the NST/NAS server to force all execution in English (1030)?

/Kasper

Comments

  • Options
    mohana_cse06mohana_cse06 Member Posts: 5,503
    Add GLOBALLANGUAGE(1033); in Codeunit 450 OnRun trigger and try..

    -Mohana
    http://mohana-dynamicsnav.blogspot.in/
    https://www.facebook.com/MohanaDynamicsNav
  • Options
    kasper.jensen@logica.comkasper.jensen@logica.com Member Posts: 5
    Hi Mohanna,

    Been there done that - does not work :-(
    PS: It works in NAV2009.

    /Kasper
  • Options
    mohana_cse06mohana_cse06 Member Posts: 5,503
    How are you running the NAS?

    -Mohana
    http://mohana-dynamicsnav.blogspot.in/
    https://www.facebook.com/MohanaDynamicsNav
  • Options
    kasper.jensen@logica.comkasper.jensen@logica.com Member Posts: 5
    Via Job Queue, startup codeunit =450
  • Options
    Marije_BrummelMarije_Brummel Member, Moderators Design Patterns Posts: 4,262
    Do you mean this?

    http://www.waldo.be/2013/05/15/nav-2013 ... -nas-user/
    Marije Brummel | Freelance Business Central Specialist
  • Options
    einsTeIn.NETeinsTeIn.NET Member Posts: 1,050
    Waldo's solution certainly works from a technical point of view. But we all know that not all users speak English (or just don't want to because they are very proud of their native language like the french). So, it's not just a topic of get it to run but also of how are messages in Job Queue Log Entry displayed.
    "Money is likewise the greatest chance and the greatest scourge of mankind."
  • Options
    kasper.jensen@logica.comkasper.jensen@logica.com Member Posts: 5
    Hi Mark,

    Thx for your input. I believe it will solve my problem but limit the solution to using the same language for all Job Queues (this is ok as a temporary workaround).

    Currently I am trying to change the Globallanguage just before the new background session is started in CU451 as I want to control this per Job Queue Entry - see example below:


    Process(VAR JobQueueEntry : Record "Job Queue Entry")
    COMMIT;

    //{CGITS/001/START}
    // Not support by Microsoft at the moment.

    StandardLanguage := GLOBALLANGUAGE;
    IF (JobQueueEntry."Language ID" <> StandardLanguage) THEN
    GLOBALLANGUAGE := JobQueueEntry."Language ID";
    //{CGITS/001/STOP}

    AttemptToRun := TRUE;
    WHILE NOT Success AND AttemptToRun DO BEGIN
    Success := CODEUNIT.RUN(CODEUNIT::"Job Queue Start Codeunit",JobQueueEntry);
    IF NOT Success THEN BEGIN
    NoOfAttempts := NoOfAttempts + 1;
    AttemptToRun := NoOfAttempts < JobQueueEntry."Maximum No. of Attempts to Run";
    END;
    END;

    //{CGITS/001/START}
    // Not support by Microsoft at the moment.

    IF (StandardLanguage <> GLOBALLANGUAGE) THEN
    GLOBALLANGUAGE := StandardLanguage;
    //{CGITS/001/STOP}
Sign In or Register to comment.