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 :
Finance | Project Operations, Human Resources, ...
Unanswered

Error on clicking the Open in Microsoft Office on form in D365 for finance and operations

(0) ShareShare
ReportReport
Posted on by 5

Export on form is not working. System throws below error on click of the Open in Microsoft Office

There was an error deserializing the object of type Microsoft.Dynamics.AX.Metadata.MetaModel.Extensions.AxODataResource. Unexpected end of file. Following elements are not closed: HelpText, Value, KeyValueOfstringAxODataFieldLjh4bohd, Items, Fields, AxODataResource. Line 1, position 2750.

Please suggest if there any resolution. 

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    301,069 Super User 2025 Season 2 on at

    Hi Arun,

    Can you provide some more information? On what form do you get this error? Do you have a customization here? Did it work correctly in the past? Does every user has this issue?

  • Khaled_Dyanmics Profile Picture
    10 on at

    Hi Andre,

    1. It is coming in all the form in D365 FNO.

    2. Yes it is due to customization, But not able to find out due to which customization.

    Not able to get from call stack and trace parser.

    3. getting this error in ExportToExcelMetadataCache class , Method. :- initialize

    Line  :- var odataModelBuilder = Microsoft.Dynamics.Platform.Integration.Services.OData.Metadata.MetadataModelBuilder::Instance;

    4. Yes it is coming for all user.

    5. we have written COC for DMFPackageExporter,(exportToPackageV2) class, After that we have deleted also.

    6. Raise case with MS but still no luck ,

    Any help will be appreciated.

  • WillWU Profile Picture
    22,361 on at

    Hi Arun,

    Issue was with the customization on the model.

    You need to check the Windows event logs and SQL Server error logs to find the related models.

    Remove it and test if it will work or not.

    Hope this helps.

  • André Arnaud de Calavon Profile Picture
    301,069 Super User 2025 Season 2 on at

    Hi Arun,

    If you have added new data entities, make sure the label, public entity name and public collection name properties are unique.

    Perform a full build of your custom models and execute a full database sync.

    I do hope these steps will solve your issue.

    Otherwise, you need to review all your customizations.

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 592 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 478 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 305 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans