Finance | Project Operations, Human Resources, ...

The model is blocked from customization. You cannot have more than one model in this package.

(0) Share

Report

Posted on by itlabnarmi_ivoruk

166

Hi community,

I've been assigned a task by my manager and provided with a virtual machine. Before proceeding, I just trying to build some specific models; however, I encountered an error during the process. At present, I'm not aware of any prior customizations made on the machine. Could you please advise whether this error is common ? any solution

/The model 'Ledger.CUS Model' belongs to the package 'Ledger' that is blocked from customization. You cannot have more than one model in this package./

thanks

All responses (5)

Answers (0)

Sort by

Suggested answer

Martin Dráb 241,360 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I don't know who did it and why, but no 'Ledger.CUS Model' should exist. It's a bug. Either get a new, clean environment deployed, or you'll need to fix this one (by remove the model). I would rather get a new one, because if there is one completely meaningless change, there may be other surprises as well.
Suggested answer

Hana Xue Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,
Some packages are marked as blocking customization. You can verify the properties of the "Ledger" package. As Martin mentioned, if you choose to fix it, you can delete the model according to this post: Models and packages - Finance & Operations | Dynamics 365 | Microsoft Learn
Best Regards,
Hana
Martin Dráb 241,360 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Beware: the link describes how to delete a whole package, not a single model in a package (despite the title saying Deleting a model). You don't want to delete the whole Ledger package.
Kevin Xia Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

There have been previous posts on the forums asking for a solution to a similar error, and you can refer to this old thread: Solved: Removing models created by 2012 > D365 code upgrade (dynamics.com), where Martin also gave a solution.

Best regards,

Kevin
MuthukumaranAX 2,903 on at

Like (0)

Report
Copy link

Link copied!

is it fresh Dev instance? or you got code from Ax 2012 version?