Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Integer table position in report?
mdsr
Member Posts: 163
in report how position of integer table affects report
in sales invoice report 206 we add integer table after sales invoice header why we not put it on the top of data set and what would be it's effect
thank you
in sales invoice report 206 we add integer table after sales invoice header why we not put it on the top of data set and what would be it's effect
thank you
1
Answers
A integer table is offen use i report (like 206) because they use temporary table, and on previous version of the report element it was not possible to use a temporary table.
So a lot of legacy here
The "Integer" DataItems are a kind of FOR-NEXT construct where you know upfront the number of iterations in the loop, but you do not want to/or cannot link this directly to a physical table in your database.
Example:
You want to generate three copies of your invoice. So you implement a dataItem "CopyLoop" based on Integer and set a filter to Number 1..3.
This forces the system to run through the more indented dataitems the number of times you defined in the "CopyLoop" and therefore create 3 copies.