Microsoft Dynamics AX (Archived)

Question for CUP layer with CU13 upgrade

(0) Share

Report

Posted on by Ganriver1

1,559

Hi Friends,

We are upgrading to 2012R3 CU13, then found out there is CUP layer which created way back for whatever reason.

Problem is we have VSTS now, only have CUS layer code checked in, when come to fixing the conflict for those objects in CUP layer, what is best way to handle it?

Many thanks!

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report
Create a project of objects that exist in CUP layer (Tools - Code upgrade - Create project from model)

Export that project as xpo

Delete all objects from CUP layer

Import xpo to CUS layer

Full x++ compile, CIL, db sync

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

And in step 2, export elements only from CUP layer (there is a checkbox in xpo export dialog for this).

Was this reply helpful? Yes No
Suggested answer

Mea_ 60,284 on at

Like (0)

Report

It's a bit harder than that, deleting objects you can loose data if you sync data dictionary and mess up with Ids, instead follow this blog post https://community.dynamics.com/ax/b/axinthefield/posts/moving-customizations-between-layers-in-dynamics-ax-2012 it guides you through the process.

Was this reply helpful? Yes No
Ganriver1 1,559 on at

Like (0)

Report

Hi Nikolaos,

As I dig in, found more stuff. There are two models in CUP layer, and I did a layer comparison between CUP and CUS,

objects in red circle are in 'CUP' only, not existed in CUS, 4 forms are in both 'CUP' and 'CUS'. That's all.

To create another environment is a little too much work as we have tight schedule, do you see a problem I just follow the steps you listed in same environment?

Was this reply helpful? Yes No
Ganriver1 1,559 on at

Like (0)

Report

Or, if we just move classes and forms, that shouldn't have any problem.

Was this reply helpful? Yes No