Model is greyed out - Unable to do build for ISV package

(0) Share

Report

Posted on by YOG

414

Dear experts,

am I missing anything?

I have 3rd party ISV package that i have installed on Dev box but i am unable to refresh data entity. I can see ISV models installed on Dev box but it is greyed out.

I have performed follow steps

1. Uploaded ISV package to asset library

2. Deploy package on Development environment

3. Added package to source control

4. synchronized database

5. run VSTS pipeline

Error while refreshing entity list

Model is greyed out

I have the same question (0)

All responses (8)

Answers (2)

ergun sahin 8,826 Moderator on at

Like (0)

Report

It is normal for the isv model to be gray in fullbuild, but it is not normal to give 203 errors. Are you sure the errors are coming from there? Can you do full sync?

Was this reply helpful? Yes No
André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi YOG,

When you install a deployable package, the runtime objects are installed only. The ISV vendor is not always providing the models with source coding. That is the reason why the model is greyed out.

You didn't had the error before installing this ISV model? Have you already verified if the deployable package is supported on your version of Dynamics 365? Did you contact the ISV vendor for help?

Was this reply helpful? Yes No
Alex VN 1,994 on at

Like (0)

Report

Hi,

Typically, these artifacts are distributed as code (in the form of models) or binaries (in the form of deployable packages). Can you check with your ISV provider if they provide you with the package as it normally provided as deployable package and not contain of the source code so you will not see the code and build the model.

The issue seems to be with database and you might need to enable change tracking to overcome the problem and do not need to do a build as the model is already "built". Reference:

community.dynamics.com/.../d365fo--data-entity-refresh-list-problem

Hope this helps.

Was this reply helpful? Yes No
YOG 414 on at

Like (0)

Report

Isv package provider do not give a source code.

I have noticed that I can add data entity to all entity screen manually but they do not appear automatically. Package has over thousand of custom entities and I am not really keen to adding them in one by one.

Andre - no, I did not have any error installing ISV Model. ISV Vendor confirms that package is compatible with the D365 version that we have and they do not provide help.

Alex - I have turned ON Change tracking. Data entity is being refreshed ok but still cannot see ISV data entities under all data entity screen.

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi YOG,

do you have the ISV solution license installed in your dev system? Perhaps the automatic data entity refresh doesn't bring up entities which don't have the config key (=license) enabled.

Anyway this issue is not related to your original question of not being able to compile this model.

Was this reply helpful? Yes No
YOG 414 on at

Like (0)

Report

Hi Nikolaos,

I have contacted ISV provider and they says they do not ship license with Package.

package is completely ok.

Entity list is being refresh successfully but getting error as below

Is this causing issue?

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi,

seems this is some new question/problem. Is your original issue solved?

If ISV entities are still missing, do you have the ISV license installed? You wrote that they don't ship the license with the package which is ok, but just remember that you need a license (if the ISV solution requires one). How they ship is is up to you and them to agree.

Was this reply helpful? Yes No
YOG 414 on at

Like (1)

Report

Hi Nicolaos,

We have identified the issue. ISV package has a bug in 10.0.20 (PU44).

Additionally, regarding screenshot above,

here is a explanation.

Resolution

The actual error was reported by a client and it is still unclear how it became an issue. The investigation into the case revealed no duplicate data is present when applying the Atlas Package to a pristine Contoso system.

There are actually two issues here, firstly the Contoso System has the wrong XML Field Name recorded in the DMFTargetTable.

You should first try Deleting the Data Entity from the Data Management Data Entities Section. You will need to remove any export jobs first, then refresh the data Entities list

Deleting the XML Table from SQL and refreshing the data entity list created a different Field name called ExternalItemDescription for BusinessDocumentSalesInvoiceLineItemEntity

If the above does not work, try clean the complete current entity structure on local AxDB using this T-SQL script:
TRUNCATE TABLE DMFENTITY
TRUNCATE TABLE DMFTARGETXML
TRUNCATE TABLE DMFTARGETXMLTOENTITYMAP
TRUNCATE TABLE DMFTARGETENTITYHIERARCHY

Then Synchronize DB. and Refresh the entity list.

Was this reply helpful? Yes No