Microsoft Dynamics 365 Blog

It happens very seldom, but sometimes the AOT MetaData is getting damaged, especially for Table objects.

Indications of such an element “corruption” can be that you have one explicit Table in the AOT and every time you access this object either the Dynamics AX Client or the Dynamics AX Application Object Server crashes. But the issue can also start earlier when you expand the Data Dictionary node of the AOT.

If you have no idea what Table could be affected the following X++ Job can help you finding out, by walking through the UtilIdElements Table touching each individual Table object:

static void findDamagedTableObjects(Args _args)
    UtilIdElements util;
    common tabBuff;
    DictTable dt;

    //Look at all Tables
    while select util where util.recordType == utilElementType::Table
        /* Print out the name; the last element showing up here is
           most likely the object causing issues… */
        print strFmt(‘Layer: %1 | Table Id: %2 | Table Name: %3’,

        //This will eventually cause the Client or AOS to crash
        dt = new DictTable(tablename2id(;
        tabBuff = dt.makeRecord();

    print ‘Completed without error!’;

The Job accesses all Table Objects and lists them in the Print window. When the damaged element is reached the operation is stopped (e. g. because the AOS is crashing) so the last object showing up in the Print window is most likely the one causing the trouble.

Once you know the Table object causing issues, you could try deleting the object programmatically with the following X++ Job:

static void deleteDamagedTableObject(Args _args)
    UtilIdElements utilElement;
    UtilElementName tableName;
    UtilEntryLevel tableLayer;
    /* Please adjust to the Table Name and Table’s Layer to be removed! */
       tableName = ‘NameOfDamagedTableToBeRemoved’;
       tableLayer = utilEntryLevel::usr;
    select utilElement where == tableName
       && utilElement.utilLevel == tableLayer
       && utilElement.recordType == utilElementType::Table;
    if (utilElement)
        info(strFmt(‘Table object %1 in Layer %2 has been deleted!’, tableName, tableLayer));
        warning(strFmt(‘Table object %1 in Layer %2 was not found!’, tableName, tableLayer));

If attempting to delete the Table object with the previous X++ Job fails in any way, it will be necessary to rebuild the layer the damaged object is existing.

One possibility to rebuild a damaged layer is:

  1. Create a new Project in the AOT
  2. Specify a filter for all elements from the affected layer (don’t use any grouping here, as this could again cause a crash)
  3. Create another new Project and manually move all non-damaged objects from the first Project to the the other
  4. Export the second Project as XPO (with IDs)
  5. Stop the AOS and delete the damaged Layer’s AOD file (and AOI)
  6. Start the AOS again
  7. Re-import the XPO to the same Layer (now the corrupt object is gone)


–author: Tariq Bell
–editor: Alexander Lachner
–date: 16/03/2010

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!