Incorrect totals the first time a report is run

pdj
Member Posts: 643
NAV5SP1 – build 27191, SQL2005 SP3.
I have the strangest result EVER with a report in NAV!
It turns out that the first time I execute it, the calculated totals (from CREATETOTALS) are incorrect. After that it keeps doing it right. Each time I re-open the database the problem comes back, but only for the first run. I have tried it 30-40 times and it is always the same. The first time it seems to miss one of the first entries in the calculation, but after that it works like a charm.
It is an old homemade report that is going through some entry like records with a filter on a Journal No. field. It has been used for years in Native 3.70 without any problems, but now the problem suddenly appear after migrating to NAV5SP1-SQL. The problem doesn’t exist for all journals, so sometimes it gets it right the first time as well. The problem also disappear from the journal if I re-open the database and run it on one of the journals that isn’t causing problems. So it is not a question of having read the actual data before or not.
I’m currently trying to re-produce it in native or make the error appear as simple as possible in SQL before reporting it. But has anyone seen this kind of behavior before?
I have the strangest result EVER with a report in NAV!
It turns out that the first time I execute it, the calculated totals (from CREATETOTALS) are incorrect. After that it keeps doing it right. Each time I re-open the database the problem comes back, but only for the first run. I have tried it 30-40 times and it is always the same. The first time it seems to miss one of the first entries in the calculation, but after that it works like a charm.
It is an old homemade report that is going through some entry like records with a filter on a Journal No. field. It has been used for years in Native 3.70 without any problems, but now the problem suddenly appear after migrating to NAV5SP1-SQL. The problem doesn’t exist for all journals, so sometimes it gets it right the first time as well. The problem also disappear from the journal if I re-open the database and run it on one of the journals that isn’t causing problems. So it is not a question of having read the actual data before or not.
I’m currently trying to re-produce it in native or make the error appear as simple as possible in SQL before reporting it. But has anyone seen this kind of behavior before?
Regards
Peter
Peter
0
Comments
-
I have not seen this, I think it's a bug in your report, that somehow the classic client did not show.
Do you by any chance have savevalues setting or anything enabled? and you are displaying the values on the request form?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