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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Model database inconsi...
Microsoft Dynamics AX (Archived)

Model database inconsistency with AX 2012 R3

(0) ShareShare
ReportReport
Posted on by Beat 1,006

Hi,

i imported a model using AxUtil.exe. It said a virtual model was created because of missing parents. So far so good. But when i check the content of the vitual model it is empty. No elements in that model!

After further investigation in the model database i found a strange entry in table ModelElement:

There exists a Fieldgroup without pointing to a parentHandle (value 0).

Has anybody experienced similar problems? How can i solve this?

Tnx in advace.

Beat

*This post is locked for comments

I have the same question (0)
  • Jonathan Halland Profile Picture
    Jonathan Halland 11,310 on at

    Hi.

    I have experienced this. I think it is because of the way AX2012 forms are structured in the backend that you may get "rogue" elements with no parents. Create a project from your model in the source system to find the element in question and then delete that field group from the Object. IF a form use the Design List.

  • Beat Profile Picture
    Beat 1,006 on at

    Hi Jonathan,

    Tnx for fast reply. The problem i have is that i dont get anything in the project. This is because the parent is not identified. And it does not belong to form but to table. It is kind of 'free flying' fieldgroup of a table - not form :-(

  • Jonathan Halland Profile Picture
    Jonathan Halland 11,310 on at

    Hi Beat.

    It seems like you do have the name of the field group, are at all able to identify what table it was connected to originally? If so, maybe recreate it on that table and delete it again. Unfortunately I think I'm down to guess work on the issue from my side as its not the same issue I have previously experienced.

  • Beat Profile Picture
    Beat 1,006 on at

    Hi Jonathan,

    Don't think that recreate in AX will solve it, guess just creates a new correct fieldGroup entry in the model. But your comment leads me to another idea :-). I'll try to fill in the parentHandle manually pointing to a known existing table. After this i basically should see it in AOT on that table. Deleting it may solve the issue... let's see - i'll post the result of that journey here...

    Beat

  • Beat Profile Picture
    Beat 1,006 on at

    Hi,

    As promised i update this issue with the result of manually define the parentHandle on the 'damaged' modelElement entry. After entering the parentHandle of a known table i effectively saw the fieldGroup in AOT. I deleted it. Exported the model, deleted the model and importet it again.

    Sad to say that stil a virtual model without any content is generated. So the story goes on...

    But i got rid of that 'free flying' fieldGroup element - at least this is good news.

    Beat

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Ali Zaidi Profile Picture

Ali Zaidi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans