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
- 263 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
trouble with report: Too many rows
IvanB
Member Posts: 17
Hello! Can you help me. I created new report and run on preview. Total rows in the report 19000. I get error "Stream was too long". Why can't show 19000 rows?
Nav2016
Nav2016
0
Best Answers
-
Options
Slawek_Guzek
Member Posts: 1,690
Hi,
Check if you don't have anything like a picture or other BLOB data anywhere in your dataset.
SlawekSlawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-035 -
Options
RockWithNAV
Member Posts: 1,139
Picture, Blob, Loop, Clearance of variables check everything OR eventually debug you will find the real culprit.Thanks
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/5 -
Options
vaprog
Member Posts: 1,118
Why does does the thread caption read "...: Too many rows" when the error message says "Stream was too long"?
Did you jump to an unwarranted conclusion, or do you have more indication for this?
A quick google search let me believe, not enough memory is the reason for the error message. So, try to reduce the size of the data in the dataset. I believe, structuring (indenting) the data items and keeping fields as "outdented" as possible may help. For instance, it makes little sense to transmit a company logo with every row.6
Answers
Check if you don't have anything like a picture or other BLOB data anywhere in your dataset.
Slawek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
Zaid Tariq
Dynamics NAV/365 BC Developer at Dynamics 360
please like / agree / verify my answer, if was helpful.
Did you jump to an unwarranted conclusion, or do you have more indication for this?
A quick google search let me believe, not enough memory is the reason for the error message. So, try to reduce the size of the data in the dataset. I believe, structuring (indenting) the data items and keeping fields as "outdented" as possible may help. For instance, it makes little sense to transmit a company logo with every row.
The trick is to base the very first Data section on the Integer table, limit iterations to just one, and add all BLOBs as variables calculated in the code and exposed as columns in that sectoin.
Or investigate ForNav Reports - far, far better and cost-effective solution for creating and maintaining reports in NAV/BC
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03