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 / Finance | Project Operations, Human Resources, ... / Unable to Open .XLSX A...
Finance | Project Operations, Human Resources, ...
Answered

Unable to Open .XLSX Attachments and Use Preview in D365FO After 10.0.43 Update

(1) ShareShare
ReportReport
Posted on by markovicb85 23

Hi everyone,

After updating D365FO to version 10.0.43, I'm encountering an issue when trying to open .xlsx attachments in General ledger -> Journal entities -> General journals.

Preview functionality is also not working.

Has anyone experienced a similar issue or have any suggestions on how to resolve it?

 


 
preview_not_working.png
error_when_try_to_open.png
Categories:
Dynamics 365 Finance
I have the same question (0)
  • Verified answer
    Anton Venter Profile Picture
    Anton Venter 20,346 Super User 2025 Season 2 on at
    Hi,
     
    It seems there is a data issue because of the error message. Value cannot be null. Parameter name: location. Add a new attachment document and then check and compare the data in the DocuValue and DocuRef tables with the new attachment and the ones giving you errors. Assuming that adding new attachments is working fine, by comparing the data you will be able so see what's wrong.
  • Navneeth Nagrajan Profile Picture
    Navneeth Nagrajan 2,438 Super User 2025 Season 2 on at
    Hi CU2105-844-0,
     
    A few questions:
    1. Do you have file names with a parenthesis in your file name?
    Have you checked the KB Article number 4614558, Unable to preview attachment with parenthesis in the file name in self-service environments in Dynamics Lifecycle services Issue Search?
     
    2. Can you provide some insights on how this file is being attached or is it imported from a ftp site into D365 F&SCM?
     
     
  • markovicb85 Profile Picture
    markovicb85 23 on at

    Hi all, thanks for the responses.

     

    Additional context:

    After updating both the Dev (cloud-hosted) and UAT (sandbox) environments to version 10.0.43, the issue began occurring. On the Production (sandbox) environment, which is still running version 10.0.42, everything is working as expected.

    To rule out data corruption, I refreshed the Production DB to UAT. Note that the Dev environment also had the Prod DB imported about a month ago.

     

    Response to Navneeth Nagrajan:

    1. No, the file name does not contain parentheses or any special characters.

    2. The attachment was added using the F&O app via: General ledger → Journal entries → General journals → New.

     

    Response to Anton Venter:

    When I add a new attachment, the Preview and Open functions work correctly.
    After checking the tables you suggested, I found the following difference:

    In the DOCUVALUE view:

     
    Attachment Type ACCESSINFORMATION STORAGEPROVIDERID
    Working attachment blob URL 1
    Not working attachment (empty) (empty)

    In the DOCUREF view, there were no differences observed.

  • Verified answer
    Anton Venter Profile Picture
    Anton Venter 20,346 Super User 2025 Season 2 on at
    If the AccessInformation and StorageProviderTypeId fields in the DocuValue table are empty, then that's definitely the problem. Make a backup of the data in in the DocuRef and DocuValue tables in production just in case. I don't have any idea what could have caused this.
  • markovicb85 Profile Picture
    markovicb85 23 on at
    I’m also not sure how this happened. I just updated the UAT environment (and Dev as well) to version 10.0.43, and after that, I refreshed the database with the Production DB.

    I’ll try to refresh the UAT database again, maybe that will fix the corrupted data. I assume the AccessInformation and StorageProviderTypeId fields in the Production DB have values, but I’m currently unable to verify that.
  • Verified answer
    markovicb85 Profile Picture
    markovicb85 23 on at
    It looks like this is expected behavior. According to the official documentation, the database refresh only affects the application and financial reporting databases. It does not include the Azure Blob Storage where documents are stored.

  • Anton Venter Profile Picture
    Anton Venter 20,346 Super User 2025 Season 2 on at
    Ah, now it makes sense. Good to know. Thanks for posting this too.
  • markovicb85 Profile Picture
    markovicb85 23 on at
    No problem at all. Thanks for helping me out and pointing me in the right direction

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

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 669 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

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

#3
Martin Dráb Profile Picture

Martin Dráb 384 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans