Runtime metadata is invalid because the same metadata artifact has been defined in multiple assemblies

(0) Share

Report

Posted on by Community Member

Hi all

We created several project in a model under ApplicationSuite.

Now some people decided to use a new Model not und ApplicationSuite to do our Development. For this we moved our existing implementations to the new model.

In the AOT our objects are shown as part of the new model now (only the new model), in the sourceControl Explorer on the Metadata or the old Model our objects are gone but when we compile our stuff we always get the error

Runtime metadata is invalid because the same metadata artifact has been defined in multiple assemblies

The multiple model are the new one and the old one

How can we fix this problem?

Categories:

Development / Customization / SDK

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Joris dG 17,775 on at

Like (0)

Report

If you do anything to code, you need to compile it. That includes removing code. So, after removing the code for Application suite, did you recompile the application suite package?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Joris,

I am getting same error while deploying package. Later I came to know it is due to version mismatch (RTW and 1611).

I want to know from where I can get complete list of conflicted elements? From where to delete all those elements?

I am not able to find elements from packages.

It is saying some HCMMap is present in both Application Suite as well Fiscalbooks. But I am not able to find it on Application Suite.

Regards,

Smit

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

Like (0)

Report

For reference, Smit already has his own thread for the question: Deployable Package Issue. As Joris did here, I also suggested recompiling the application.

Was this reply helpful? Yes No
K scerri on at

Like (0)

Report

Hi Chris, I am facing the same issue. Have you managed to solve this?

I am compiling both models and the issue still persists.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Background :

I was in the learning stage of Dynamics 365. So was trying with creating the all sort of elements in this process I got the same error.

I looked for a solution on Internet but didn't get a proper o/p.

Then, It took me some time but found a solution.

NOTE : This will delete the earlier elements created(It was ok for me)

Solution : Find all the elements which you had created earlier and now shown in the AOT.

->Right on each and select "Open Designer".

->Then right click on the element in the designer window.

->Select "Open Containing Folder" then delete the element form here.

This stopped this error on my instance.

Was this reply helpful? Yes No
Suggested answer

Zia Ur Rahman 2 on at

Like (1)

Report

It Is because your element exists in more than one models

In order to find the duplicated models

1->open event viewer

2->selects events for AX-Metadata under dynamics node all events will be listed down there

3-> view details of that particular event list of duplicated models will be listed there

->remove artifact from Model A then restart visual studio and build your model

Was this reply helpful? Yes No
Anthony 3 on at

Like (0)

Report

@zia ur Rahman answer works.. rebuild model..

Was this reply helpful? Yes No