Report 94 C/AL Code

marialorena
Member Posts: 62
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.
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
-
SETRANGE("Entry Type","G/L Entry"."Entry Type"::Definitive);
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.Dynamics NAV0 -
SETRANGE is setting a filter on the "Entry Type" field of the "G/L Entry" table (one of the DataItems of report 94) so that only those G/L Entry records will be 'seen' that have value Definitive.
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 helps0 -
-
I tried to delete this line from Report 94 CAL Code in our Live DB and it allowed me to proceed in generating the journal lines.
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
Loren0 -
I'm not understanding... First you say:marialorena wrote:I am not a developer who understands the code below
<snip>
Please explain what is this code for.marialorena wrote:I tried to delete this line from Report 94 CAL Code in our Live DB- 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
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions