Notifications
Announcements
No record found.
Hi,
It seems that after applying a license deployment package the full build screen is blank. There are no package models listed anymore. How do I retrieve the list of models in order to select for a full build?
Thanks,
Ricky
Hi Ricky,
Do you have own custom models on this environment? What exact version of Dynamics 365 are you using here?
I think source code doesn't exist. You need to install models to get source code.
Please go through this thread:
community.dynamics.com/.../visual-studio-model-is-grayed-out-in-build-models-menu-after-manual-import-of-a-deployable-package
I would assume to see the standard packages since you still can build them in the dev box.
You can reset the situation at least by deploying a new dev box.
Hi Andre,
Just prior to installing the deployment package I had just installed several models from this other ISVs and I was to see them here and select them for full build. Now they've all disappeared. I even tried reinstalling the model but of course it failed because it was already there. Is there away to reset this? I would assume to still see atleast the standard models. The D365 version is 10.09.
The license deployment package should change only data (in D365 database) so it should have no impact on what you see in Visual Studio. Are you 100% sure that the package contained only an ISV license? To me it seems that it was not (only) an ISV license package. Or you have also installed / updated something else.
You can try to Refresh models in Visual Studio.
But if it seems that it takes more than 1-2 hours dealing with this issue, just deploy a new dev system.
Hi Nikolaos,
Thanks, but I would hope not having to deploy new dev box. Any other ideas?
Hi Blue,
Good information here but in my case the models aren't just grayed out they have entirely disappeared all together.
In general I suggest treating the dev boxes as disposable. This way you will save a great deal of time not dealing with technical issues.
I believe that also in your case redeploying is the fastest and therefore cheapest solution.
By the way, looking at your first screenshot, I see directory K:\AosService\PackagesLocalDirectory\Releases\8.1.... What is that?
Normally all code & metadata is directly in K:\AosService\PackagesLocalDirectory folder. Do you use some non-standard folder structure? If yes, perhaps you have made some mistakes in the setup. Or applying a deployable package has re-set some setup that you had changed?
If you are using some non-standard process, it's useful to mention it since it might explain your problem.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 456 Super User 2025 Season 2
Martin Dráb 429 Most Valuable Professional
BillurSamdancioglu 239 Most Valuable Professional
