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 / Customer experience | Sales, Customer Insights,... / Error Trying to Edit C...
Customer experience | Sales, Customer Insights,...
Answered

Error Trying to Edit Catalog and Products using Excel Online "OfficeDocument.createdon"

(2) ShareShare
ReportReport
Posted on by BluFin.S 108

 

Microsoft Dynamics 365

1 ciclo di rilascio 2025 abilitato

Nome dell'app: Hub delle vendite

Nome organizzazione: D365_Sales-Sandbox

Canale: Mensile - Aprile 2025 (app)

SANDBOX

Versione server: 9.2.25044.00160

Versione client: 1.4.10217-2504.4

ID sessione: 20340c6d-ae7c-4c04-b7c1-6a13b5e4790b

Tempo: 5/4/2025 1:52:16 PM GMT+0200 (Central European Summer Time)

Hello if anyone is facing this error i'm sharing my support ticket at Microsoft:

****

Dear Microsoft Support,

I am writing to report a persistent error encountered while using the "Open in Excel Online" feature within Dynamics 365 Sales.

Action Performed:
Attempting to open a view containing Catalog Products using the "Open in Excel Online" command.

Error Encountered:
The operation fails with an "Invalid Argument" error message.

  • Error Code: 0x80040203 (Decimal: -2147220989)
  • Key Error Message: DateTime was passed as a value of attribute OfficeDocument.createdon; CrmDateTime should be used instead.

Analysis:
Based on the detailed error information (full XML trace provided below), the issue appears to stem from an internal data type mismatch within the Microsoft.Crm.ObjectModel.ExcelService component. When generating the temporary document (OfficeDocument) for the Excel Online session, the system seems to be using a standard .NET DateTime format for the document's createdon attribute, while the Dynamics 365 platform expects its specific CrmDateTime format. This mismatch triggers the InvalidArgument error.

This suggests a potential platform-level issue related to how the date/time is handled during the export-to-Excel-Online process, rather than an issue with the product data itself.

Troubleshooting Attempted:

  • Retrying the operation several times.
  • [Optional: Add any other steps you tried, e.g., trying different views, checking with other users, clearing browser cache, etc.]


 

ErrorDetails.txt
Categories:
Dynamics 365 Sales
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,530 Super User 2025 Season 2 on at
    Good morning, afternoon, or evening depending on your location!
     
    It looks like the error is caused by a mismatch between the standard .NET DateTime format and the expected CrmDateTime format within Dynamics 365. Essentially, when exporting data to Excel Online, the system is incorrectly passing a DateTime value for the OfficeDocument.createdon attribute instead of the required CrmDateTime format.
    Possible Solutions:
    1. Check for Updates
      Ensure that your Dynamics 365 environment is fully updated, as Microsoft may have released a fix for this issue.
    2. Modify the Data Format
      If possible, try manually adjusting the date format before exporting. You may need to convert the DateTime values to CrmDateTime within the dataset.
    3. Use an Alternative Export Method
      Instead of using "Open in Excel Online," try exporting the data to Excel offline and manually adjusting the date format before re-importing.
    4. Check for Plugin Conflicts
      The error message references Microsoft.Crm.ObjectModel.ExcelService, which suggests that a plugin or customization might be interfering with the export process. If applicable, review any customizations related to Excel exports.
     
    Please note: I teamed up with CoPilot AI to research and craft the best response to your question!
    Hope this helps some!
  • Verified answer
    BluFin.S Profile Picture
    BluFin.S 108 on at
    Yes, the second next day, issue has been resolved from Microsoft side, looks like it was something NOT related to my environment anyway.

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 > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 74 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 32 Most Valuable Professional

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 31 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans