I have used a report with advanced dimensions for a long time now.
Instead of using the shortcut dimension fields provided by NAV, I have used the dimension code/dimension code description as a field name in my Jet formula's.
All without trouble, until I switched to the SQL connection.
It seems randomly impossible to access the information through the dimension code/dimension code description.
Sometimes I get the message:
Jet can not find any relationship between the 'xxx' table and Advanced Dimensions. There must be at least one Advanced Dimension entry for a table in order for Jet to find the relationship. Either there are none, or Jet does not support Advanced Dimensions for this table.
Where xxx is the table name I use for reporting.
Sometimes I simply receive no data, without any error message.
Switching back to the shortcut dimension fields provided by NAV itself, all seems to work again.
But that becomes a problem when I need dimension 3 or higher…
I have tested it with the newest versions: Jet 15.0.14295.0 and Excel 2013 (15.0.4659.1000) all 64-bit
I'm using NAV2013 as a data source. NAV 2013 (7.0.34745.0)
What is happening here?
Does anyone recognize this?
Do I need to do anything in the database to still use dimensions this way in reports?
Is JetReports missing something?
rmw
Date
Votes
1 comment
-
Jet Reports Historic Posts It looks like the culprit is the new way dimensions are stored in NAV2013 through dimension set id's
One of the great things about advanced dimensions and Jet was the ease of use by simply providing the dimension code as a field name and let Jet/Nav do all the fancy trickery to get the correct information.
Now I have to find dimension set id's first and then use them for finding the real lines I am looking for.
Is this going to change back to the old way of using dimension codes as field names?
It still is allowed in the syntax but it will return just garbage and that is not the way it should be…
rmw
Please sign in to leave a comment.