Report 10074 Sales Invoice CU12 Update for Nav 2016

(0) Share

Report

Posted on by Louis Li

In Nav 2016 CU10, the report 10074 Sales Invoice skipped G/L entries when printed. In the latest CU12, the Nav team fixed the issue. I tested it out in my test environment by doing the full CU steps, the fix is good. So, does anybody know if I can just export the new object ( Report 10074 in a .fob file), and import it into my CU10 server? In other words, I just want to quickly implement this one fix in my CU10 environment for now, and likely will do the full CU12 update later. Can a single report update via a .fob file be ok without doing the full CU update? I just want to be sure not to mess up my working environment.

*This post is locked for comments

All responses (6)

Answers (2)

Luc van Vugt on at

Like (0)

Report

RE: Report 10074 Sales Invoice CU12 Update for Nav 2016

Regarding Report objects: yes.
Louis Li 65 on at

Like (0)

Report

RE: Report 10074 Sales Invoice CU12 Update for Nav 2016

Good thinking, Luc. I will export the original .fob file. Presume I can import and over-ride the CU12 .fob file with the CU 10 .fob file if I need to?
Louis Li 65 on at

Like (0)

Report

RE: Report 10074 Sales Invoice CU12 Update for Nav 2016

Thanks, Suresh. I reviewed all the new objects in CU12, and found 2 updated tables (37 Sales Line, 5107 Sales Header Archive), 1 code unit (80 Sales-Post), 3 Page (43 Sales Invoice, 132 Posted Sales Invoice, 143 Posted Sales Invoices). So, likely, new Report 10074 would likely have some dependence on these new objects? I don't mind to do the full CU12 update to ensure trouble free fixes. When it comes to the Import Worksheet, do you recommend Merge from existing to new, or Replace? I know the difference, but there's not enough explanation/recommendation for each approach. Some suggested to go with "Replace" to ensure codes are clean, while "Merge" could have combined codes that have conflicts and not working well together. I do have a handful of customized reports. While I like the convenience of not needing to redo the reports after a CU update, I prefer a working report, redo the customization, over a report not working at all. Any good ideas?
Luc van Vugt on at

Like (1)

Report

RE: Report 10074 Sales Invoice CU12 Update for Nav 2016

And to add to other contributions: before you import, export the original report first, so you can always revert to that.
Verified answer

Amol Salvi 18,696 on at

Like (0)

Report

RE: Report 10074 Sales Invoice CU12 Update for Nav 2016

I think you can do that by exporting from CU 12 and import in CU 10 but but before importing check any customization did in the report
Verified answer

Suresh Kulla 47,787 on at

Like (1)

Report

RE: Report 10074 Sales Invoice CU12 Update for Nav 2016

Louis,

Yes that will be ok, you need to make sure it does not have any dependencies of other objects which are updated in the same CU 12, if so you need to update those objects also.