Hi!
I am not a developer who understands the code below. The presence of this code in Report 94 stop me from generating journal lines for YearEnd transaction in our current system (5.0) when compared to our older version (4.0) which doesn't contain this code. I'm referring to Report 94 C/AL code.
SETRANGE("Entry Type","G/L Entry"."Entry Type"::Definitive);
By the way (ReporNAV 5.0 Cronus db) has this code but still proceed generating the journal line.
Please explain what is this code for.
Thanks.
0
Comments
this is a simple filter, this means your G/L entry's option field definitive is set to your entry type field. if it matches with definitive the only the entire code or loop will be run if there is any.
FYI:
This code is part of the local French and APAC (Asia Pacific) feature called Simulation, which allows you to post entries to G/L from a simulation journal without impact on G/L. The trick is that simulation entries will get a negative Entry No., where 'normal' entries have a positive Entry No.[/i. Next to that there is an option field called Entry Type which has value Definitive or Simulation.
Reports like report 94 have been adjusted for this Simulation feature so either show only 'normal'- i.e. definitive - entries, simulation entries or both.
The simulation feature has been added to APAC since 5.0 which accounts for the difference you have found.
Hope this helps
Never stop learning
Van Vugt's dynamiXs
Dutch Dynamics Community
My Blog - nav.education
Though this resolve the issue, it is still a question why in Cronus NAV5 standard, it is possible to generate the journal lines even with the existence of the line below while in NAV5 Live, we can not proceed.
SETRANGE("Entry Type","G/L Entry"."Entry Type"::Definitive);
Note that in the Live DB Rep94 is not modified ; the same with the Standard Cronus.
Please guide
Thanks
Loren
- You don't know what code means
- By deleting code directly fromthe Live database, you are showing that you have absolutely no clue at all about proper development procedures
You need to stay away from the code completely, and get a developer to help you. Deleting code is not something you should be doing, and deleting it from the live system is about the worst thing you can do.RIS Plus, LLC