web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Metadata is 'confused'

(0) ShareShare
ReportReport
Posted on by 134

Hi

I'm in the middel of a upgrade from Ax2012R3 to D365 v10.0.17

We are only doing Data dictionary (EDT, Enums and tables) upgrade

I have used the LCS tool to migrate the model store and as you know, it does not create extensions to standard tables so I have to do that manually.

example, new fields on VendtTable is ApplicationSuite foundation var model

I have moved all extra fields to a new model, by doing the following

1) open the Vendtable in designer

2) create extension

3) add the vendtable to a new project in the same solution

4) delete the vendttable

5) open the extension

6) drag and drop the customized (new) fields from vendtable (step 1) to the extension

7) save the extension

in the package directory, K:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxTable\Delta there is nothing

and the extension is in the new model directory

but when doing a build it continue to say that the fields that is moved to the extension is still in the old model as well as in the new model so the full compilation falis.

using d365fo.tools to compile from the command line indicate that the metadata somehow is screwed up:

the Get-D365Model fail:

Exception calling "CreateRuntimeProvider" with "1" argument(s): "Runtime metadata is invalid because the same metadata
artifact has been defined in multiple assemblies. \nFirst 10 conflicting names:
AccountingDistribution,AccountingDistributionTmpJournalize,AODatosCadenaCliente. \nSee metadata events for complete
list."
At line:14869 char:9
+ $metadataProviderViaRuntime = $metadataProviderFactoryViaRunt ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : MetadataReadCrossAssemblyDuplicateException

How do I fix the metadata?

I have the same question (0)
  • steen.rabol Profile Picture
    134 on at

    One option is to double check that everything is moved to a new model and then use the ModelUtil.exe to remove the 'empty' model

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 74

#3
Martin Dráb Profile Picture

Martin Dráb 64 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans