Microsoft Dynamics AX (Archived)

Impact of All the Customizations present on USR layer

(1) Share

Report

Posted on by Muneeb

895

Hi,

As per the practice, the vendor is supposed to work for the Customer for any customizations on VAR layer.

However, just need to understand the impact. The vendor has done all the customizations on the USR layer for a Customer using AX 2012 R3. Considering the customer might go for Application upgrade to D365FOE, what can be the list of issues?

Sincerely,

Muneeb

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (3)

Verified answer

Martin Dráb 239,040 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Upgrade is not really a problem (at least I can't think of any problem), but it's far from ideal in AX 2012 itself.

Was this reply helpful? Yes No
Muneeb 895 on at

Like (0)

Report
Copy link

Link copied!

Like, when the customer makes any modifications, he can work on USR layer. So that the code can be differentiated between Customer and Vendor if Vendor would have worked on VAR layer. Otherwise we wont be able to differentiate the code (Considering VSTS is NOT in place).

Was this reply helpful? Yes No
Verified answer

Satish Panwar 14,671 Moderator on at

Like (0)

Report
Copy link

Link copied!

If someone gets to AOT, default layer is USR layer. Code can be deleted. Security needs to be very well controlled. Try provisioning version control at least.

Moving to D365, you have to re-write lot of code anyway considering overlayer is not there so of you are ok with USR layer in 2012, not an issue for D365.

Was this reply helpful? Yes No
Verified answer

Khushhal Garg 1,514 on at

Like (0)

Report
Copy link

Link copied!

There is no impact. In D365FO, layering concept has minimal role. During upgrade, it will create new model in USR layer so no need to worry about USR layer customizations in AX 2012.

Was this reply helpful? Yes No
Muneeb 895 on at

Like (0)

Report
Copy link

Link copied!

Hi Satish,

Yes, deleting is a concern as the default layer is USR. Any other concern while using AX 2012 itself?

Was this reply helpful? Yes No
Muneeb 895 on at

Like (0)

Report
Copy link

Link copied!

Hi Khushhal,

Ok. Thank you for the details.

Was this reply helpful? Yes No
Suggested answer

Satish Panwar 14,671 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi Mohammed,

Don't see other issue with USR layer in Ax2012.

Thanks,

Satish Panwar

Please take time to click yes against the answer that help guide you in right direction.

Was this reply helpful? Yes No
Martin Dráb 239,040 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

You mentioned a much bigger problem - not using version control. Why are you willing to risk losing your code, being unable to see what changes were done and why, return to an older version if needed? It's sounds like a terrible idea! (By the way, notice that VSTS is not the only version control system supported by AX 2012.)

If you want separate development of two companies (the vendor and the user), don't allow them to use the same layer. In such a case, I would recommend moving VAR code to another layer.

Was this reply helpful? Yes No