Upgrade analysis reports in Lifecycle Services

(0) Share

Report

Posted on by dinuk

I did an upgrade analysis for an 'in-place' upgrade (2012 FP to R3) using lifecycle services. The report that was generated is not the same as the one that's explained in technet (http://technet.microsoft.com/en-us/library/dn268611.aspx#Report). Has the report layout changed? If so, is there a definition for the new version of the report?

Thanks!

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Dinuk,

I think the description of the report in this article is related to AX4, AX2009 upgrades. I have tested the tool for in-place upgrade and provided some feedback in the past. I can't recall the exact output. Can you provide a small capture of the current output? Then probably I can help you.

Was this reply helpful? Yes No
dinuk 65 on at

Like (0)

Report

Hi Andre,

Thanks for your quick response. The Excel report consists of these sheets. I am ok with the first few, trying to figure out the last two sheets (see screen capture).

code merge summary - summary of merged elements by layer with and without conflicts

after auto-merge conflicts - summary of conflicts by element type by model and by layer

compilation classes - error/warning details on classes

compilation forms - error/warning details on forms

compilation tables - error/warning details on tables

compilation other - error/warning details on other elements such as security

code merge details - ?

change analysis - ?

Was this reply helpful? Yes No
Verified answer

Kevin Kidder on at

Like (1)

Report

The code merge details report shows you how many unresolved conflicts there are after LCS attempts to perform the automatic code merge that is part of the R3 code upgrade. All locations for code merging should be inspected, but the ones with conflicts are areas where the merge was not able to be automatically resolved.

The Change Analysis report is a new report which is basically a "heat map" of the various areas of the customized code which will give a visual indicator of how difficult/complex the given area will potentially be to upgrade. The weight factors used are built into the spreadsheet. If you find that the "complexity" ratings don't seem appropriate, you could use the feedback button inside LCS (the smiley face at top) to send a suggestion on why something might not make sense.

Kevin

Was this reply helpful? Yes No
dinuk 65 on at

Like (0)

Report

Thanks a lot for the explanation Kevin

Dinuk

Was this reply helpful? Yes No