Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
mneidlinger
Contributor II
Contributor II

NPrinting September 2018 Issue with Numeric Levels

We recently upgraded to NPrinting September 2018 and noticed that all numeric dimensions within a chart level are represented in scientific notation.  At first I assumed that it was simply a formatting issue, but closer examination proved otherwise.  The chart below shows the Shop Order No as a small decimal (E-307) when it is actually a 7 digit number.  All of the shop Order numbers below start with '18', so the number that are listed below are not even close.

np issue.PNG

Adjusting the 'Keep Source Formats' does not appear to help the situation, but I did find that if I add the same chart as a table instead of a level it displays the correct numbers. The work around that I found so far is to convert the shop order numbers to text within the chart dimension, but I would rather not have to touch every report again to fix this issue.

This is not an isolated case with one report either.  I am having the same issue with multiple reports across Excel and PixelPerfect.

Any ideas what could be causing this issue?

Thanks

1 Solution

Accepted Solutions
Daniel_Jenkins
Specialist III
Specialist III

Hi Mike,

In my preliminary testing I can reproduce the issue in version September 2018. If you create a Support case I will be able to link it to the bug case I create for R&D to investigate further.

Thanks - Daniel.

View solution in original post

3 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi

If this happen after an upgrade i suggest you open a support ticket. Since you can replicate issue you should be able to provide all required information for R&D.

cheers

Lech

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Daniel_Jenkins
Specialist III
Specialist III

Hi Mike,

In my preliminary testing I can reproduce the issue in version September 2018. If you create a Support case I will be able to link it to the bug case I create for R&D to investigate further.

Thanks - Daniel.

mneidlinger
Contributor II
Contributor II
Author

Daniel,

Thanks for the help. A support case has been submitted.

Mike