Visual Studio "Model" is grayed out in Build Models Menu after manual import of a deployable package.

(0) Share

Report

Posted on by Zain Bokhari

3,208 Moderator

I have manually applied a deployable package on a VM following this https://ax.help.dynamics.com/en/wiki/installing-deployable-package-in-ax7/

The package elements were successfully imported and I can see the package model and elements in classic/model view of AOT.

But all elements show up in italic font and in the Build Models menu the related package model is grayed out (check-box to select for build disabled). Can anyone please guide me on what am I missing or what do I need to do next??

Categories:

Development / Customization / SDK

I have the same question (0)

All responses (9)

Answers (2)

Sort by

Verified answer

André Arnaud de Cal... 306,290 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Zain,

You are not missing any object. They are deployed correctly. The fact that you see them in italic font is because you have deployed the runnable files, not moved the model with source coding.

The source code is only required on development machines.

Was this reply helpful? Yes No
Verified answer

Zain Bokhari 3,208 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Thank you for the clarification André. You're right.

My second issue related to this was that I could not see the deployed elements in the environment front end. But as Martin suggested in another post I was missing the license file and importing that resolved that issue.

Was this reply helpful? Yes No
Dynamics 365 for fi... 25 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Zain,

I have the same issue and I had imported the license as described on the following link:

docs.microsoft.com/.../isv-licensing

using the following command:

C:\AOSService\PackagesLocalDirectory\Bin\Microsoft.Dynamics.AX.Deployment.Setup.exe --setupmode importlicensefile --metadatadir c:\packages --bindir c:\packages --sqlserver . --sqldatabase axdbrain --sqluser AOSUser --sqlpwd ******** --licensefilename c:\templicense.txt

The command runs without errors, but when coming back to Full Build, Packages still grayed. is there any other step that I'm missing?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

You don't have the models / source code in your dev system. Instead you have installed binaries (deployable package) that contains these models. Correct?

If this is correct, the source code doesn't exist. You need to install models to get source code.

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

Like
a
(2)

Report
Copy link

Link copied!

It's not related to license. Deployable packages generally contain binaries, not source code, therefore you simply don't have any source code installed.

If you tell us what you're doing, we should be able to suggest a correct procedure.

Was this reply helpful? Yes No
Dynamics 365 for fi... 25 on at

Like
a
(0)

Report
Copy link

Link copied!

Ok, this is reasonable, because after the license the added modules appeared at Dynamics Application and I can work with it normally.

What I'm trying to do is to apply for some new user roles on those customized modules, Do I need to have source code or the binaries are enough?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

You can't add anything to those packages. You can only develop stuff on packages for which you have the source code. So, you need to create your own package and model if you don't already have a custom model that you are working on.

Where did you get the deployable package? Is it a third party solution? Ir something your company developed? If it's your company's code, you need to get the source code from source control. That's how you share code between developers.

All your custom code and all ISV solutions (binary or model) should anyway be added to your source control. Then your build process should build one package from all that stuff. Then you deploy this package to test/prod.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Also, if you only want to define new roles, you can do that without development in Security configuration form.

Was this reply helpful? Yes No
Zain Bokhari 3,208 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Hassan,

You can still access the elements for creating new security roles. You can do that from the front end as Nikolas suggested. Or if you want to do this in Visual Studio as a developed solution, you can do it in your own model(create one) and you would be able to access the elements you want in those roles from that other deployed package as long as you add that model (containing the required elements) as a reference in your own model.

I hope that clears things up for you. Cheers!

Was this reply helpful? Yes No