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

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) / Error 'The model f...
Microsoft Dynamics AX (Archived)

Error 'The model file references an element that belongs to another model that does not exists in the model store.' while importing model in AX2012 R3.

(0) ShareShare
ReportReport
Posted on by krishna.rao@dax 3,008

Hi,

while importing AX model in fresh Ax environment it's prompting the below error.

ERROR: The model file references an element that belongs to another model that

does not exists in the model store. You can use the /createparents

command switch to create a model where these elements will be placed.

ERROR: The import has been aborted and rolled back.

Error :Timeout expired."

Note : The imported model has customizations assosiated in a single layer(USR) only.

Kindly suggest on this,

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 239,029 Most Valuable Professional on at

    I think that the error is very descriptive. Please read it once more:

    "The model file references an element that belongs to another model that does not exists in the model store"

    Let's say that you have ClassA in model A and you add MethodB to ClassA in model B. If you try to import model B (without model A) to another environment, there is no ClassA to add the method into. The right solution is importing model A first.

    If you can't do it for some reason, AX can create a dummy ClassA header for you, so you can import MethodB (and migrate it to another object or so). That's what the error message means when talking about /createparents switch.

  • Verified answer
    Sohaib Cheema Profile Picture
    Sohaib Cheema 49,677 Super User 2026 Season 1 on at

    I never got a chance to validate what this guy has done on gitHub Scripts, but he has written beautifully to explain the issue

    Model dependency part 1

    Model Dependency part 2

    This guy has placed some scripts at GitHub you may check those if those can be useful for you.

  • krishna.rao@dax Profile Picture
    krishna.rao@dax 3,008 on at

    Thank you..

    The whole changes which we have done we kept under single model only.

    I got one warning message also.

    'Warning : one or more model elements in the imported model file contains the elements that have a different name in the model store.

    The following elements have adopted the model store name:

    Menu InventoryAndWarehouseManagement adopted name InventoryManagement.'

  • Martin Dráb Profile Picture
    Martin Dráb 239,029 Most Valuable Professional on at

    If you believe that the axutil is wrong and your model doesn't refer to any missing module, please report the bug to Microsoft.

    But it's seems more likely that it's you who is wrong.

  • krishna.rao@dax Profile Picture
    krishna.rao@dax 3,008 on at

    Thanks for your time.

    We imported Model file using -CreateParents .

    Anyway i have a query why should i use this command(CreateParents) even the elements not dependent on the another model.

    I will double check and will update the thread. 

    By the way you  fell free to comment on this.

    Install-AXModel -File "Filename" –Details -CreateParents

  • Martin Dráb Profile Picture
    Martin Dráb 239,029 Most Valuable Professional on at

    Q: why should i use this command(CreateParents) even the elements not dependent on the another model?

    A: It makes sense only if you have a modification of an object that doesn't exist in the target environment. It normally shouldn't happen; it indicates a problem in your deployment procedure.

  • krishna.rao@dax Profile Picture
    krishna.rao@dax 3,008 on at

    Thanks Martin,

    I'm so glad if you comment on underneath query.

    Consider: 

    Source environment : customized ClassA is present in the USR model.

    Target environment : default environment without changes and doesn't have ClassA in USR model.

    In this scenario if we are importing USR model from the Source to the Target.

    should we use the command -CreateParents ?

  • krishna.rao@dax Profile Picture
    krishna.rao@dax 3,008 on at

    Can anyone please  comment on my query regarding -CreateParents.

     


    Thanks,

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 239,029 Most Valuable Professional on at

    No, you shouldn't use -CreateParents. What parent would you like to create? Classes are top-level elements in AOT; they don't have any parents. As I demonstrated on the example in my first reply, it would be needed if you modified an element that doesn't exist in the target environment, such as if you tried to add a method to a non-existing class. It's not your case.

    You maybe also forgot to read the documentation, so let me repeat it here:

    -CreateParents

    Specifies that if you install a child element that does not have a parent in the model store , a new parent element should be created. By default, this option is off, so that if child elements that do not have parents are encountered, the import process is stopped. In general, we recommend that you avoid the use of this parameter, if possible. If you are importing multiple models that have dependencies, we strongly recommend that you import them in the correct order, so that the use of the -CreateParents parameter is not required. If you must use -CreateParents, then we recommend that you use it in combination with the -Conflict parameter set to Push, and then resolve issues with the parent elements in AOT. Note that if you use the -CreateParents parameter, a new model of Category virtual will be created.

  • krishna.rao@dax Profile Picture
    krishna.rao@dax 3,008 on at

    Martin,

    much appreciate for your time.

    I got confused by considering   the documentation and your 3rd reply.

    "if you have a modification of an object that doesn't exist in the target environment."

    It makes me to reply again with a scenario(ClassA does't exist in the Target environment).

    Thank you.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans