I am using Jet Essentials 2015 32 bit.
I am trying to create an extreme simple report where I want to check the sales per customer per year.
NL function is based on Customer table
NF function is based on Sales (LV) and then I use e datafilter ie. 01012013..31122103
When I run the report the results of the sales in the first row are correct. The results of the next row return a #VALUE.
Strange thing is when I hit debug when selecting a field which returned the #VALUE, it does give me the correct info.
I am coplelety lost!
Date
Votes
5 comments
-
Jet Reports Historic Posts Something to try would be using the NP Datefilter in Cell D3. eg. =NP("DateFilter","01/01/2013","31/12/2013")
-
Jet Reports Historic Posts Is your datefilter hard-coded into the formula, or are your referencing a cell?
if you're using a cell reference, make sure you have 'locked' the refernce to that cell (example: $A$4 instead of A4) -
Jet Reports Historic Posts I have the same problem at a couple of clients, it looks like a memory issue or time out, as you say, if you click debug, the cell calculates perfectly
I'm still trying to find the problem, I have tried not using NF commands, and making sure all offsheet references have NP(EVAL, but still no luck -
Jet Reports Historic Posts Hello stefantamis,
I would suggest verifying what type of Data Source you are utilizing as some of them have timeout settings.
e.g.
Jet Data Warehouse > Advanced tab
Dynamics NAV 2013 and later (SQL Server) > Connection tab
If you are using one of these Data Sources then increase the timeout incrementally, testing the report after each increase.
e.g. 30 > 60 > 120 > 240 > etc….
Best regards,
MWilson -
Jet Reports Historic Posts I think I have found out why this happens
On a report, I used a date range
d3 = 1/1/16..31/12/16
D6 = NL(Rows,Customer,Name)
I then created at F6 = NL(SUM,Customer,Sales LCY,Name,D6,Date Filter,d3)
This immediately caused #VALUE which resolved when clicking on debug
When I changed the NL to use H6 = NL(SUM,Customer,Sales LCY,No.,NL(Filter,Customer,No.,Name,"@@"&d6))
As this now used the key that is associated with the SUMINDEX field, it worked perfectly
The #VALUE is caused by not filtering on the actual key the calcfield is associated with, it was fixed by creating the filter to pull through the "no." records associated with the name
Please sign in to leave a comment.