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 GP (Archived) / Management Reporter Vi...
Microsoft Dynamics GP (Archived)

Management Reporter Viewer - Export to Excel fails

(0) ShareShare
ReportReport
Posted on by Tim Foster 8,515

My user can successfully Generate a Financial Report to the Library.  While in the MR Viewer, the user attempts to Export the Report to Excel and receives the following message:

"The given key was not present in the dictionary."

Then the MR Viewer crashes.

Has anyone seen this?  Is there a work-around?

Thanks

Tim

*This post is locked for comments

I have the same question (0)
  • Tim Foster Profile Picture
    Tim Foster 8,515 on at

    Bump!

  • Community Member Profile Picture
    Community Member on at

    Hi Tim,

    I have seen similar errors during a migration from FRx to MR but have never seen that error when exporting to Excel. I would recommend the following.

    1. Can you export directly from Report Designer to Excel?

    2. Check the version of Report Designer and confirm that it is at least 2.0.1700.31. If it isn't, download and apply the October SP2 update to all MR components.

    mbs.microsoft.com/.../mroverview.htm

    3. Check to see if this issue occurs with all reports. Create a very simple test report and confirm if you can export directly to Excel. If you can, generate it to Report Viewer and test exporting from there.

    4. If the issue persists, re-create the error and then check the Event Viewer. List any Management Reporter entries in your next update along with what you found from the above steps.

    Hope that helps!

  • Community Member Profile Picture
    Community Member on at

    Hi Tim,

    Were you able to check into the information I provided?

  • Tim Foster Profile Picture
    Tim Foster 8,515 on at

    Jake,

    Thanks for  responding.

    Sorry for the delay.

    To answer your questions:

    Q1. Can you export directly from Report Designer to Excel?

    A1. <rant>This is what delayed this response.  After a frustrating couple of hours yesterday afternoon with error messages that looked like "A file with the name 'X:\XXX\XXX.xlsx' already exists and can't be deleted.", I discovered that the service account for the Process Service has to have permissions on the target directory.  There's one sentence in the installation manual (Account Requirements) that mentions this.  There are no other sections describing this CRITICAL setup point (or the error message) in the manual or the help file.  Why doesn't the service just impersonate (or use the credentials of) the user RUNNING THE REPORT!?! </rant>  After getting other members of the IT team to set all this stuff up (we are multi-company and a multi-person department), the report did export successfully.  We can work around the error in the MR Viewer this way.

    Q2. Version?

    A2. 2.0.1700.66

    Q3. All reports?

    A3. No, just this one.

    Q4. Event Viewer?

    A4. The Designer successfully generates the Report to the Library.  There are no errors in the Generation process, hence no errors in Event Viewer.  The error only occurs when the user attempts to Export the report from the Viewer application to Excel.  I suspect there is something in the row format that is odd.  I will look.

    I guess we can work around this for now.  If I find out anything more, I will advise.

    Tim

  • Verified answer
    Tim Foster Profile Picture
    Tim Foster 8,515 on at

    Jake,

    I found the problem in the row format.

    The row looked like:

     7737.Img2.PNG

    formatted like:

    8662.Img3.PNG

    I changed it to:

    and the report now exports cleanly.

    Thanks for your help.

     

    Tim

  • Community Member Profile Picture
    Community Member on at

    Hi Tim,

    Glad to hear you were able to determine the cause of the issue and thank you for posting it here for others to see.

  • Ian Richardson Profile Picture
    Ian Richardson 4,150 on at

    hi Tim and Jake

    resurrecting an old post.

    I am getting this same error message.

    Like Tim I can export to the report viewer without incident.  

    I can export the report from the viewer to excel. I get the error if I click the box for

    "export to a single worksheet"

    I am running the report at the financial and account level is that going to cause issue as a single sheet cannot handle the -f and -a that I would get with multiple tabs?

  • Ian Richardson Profile Picture
    Ian Richardson 4,150 on at

    further testing has found that including the @DateLong auto text into the footer of the report causes this error.  The current system time also seems to be causing this error.

    The reporting tree has over 100 levels, the report is generating in about three minutes so each level of the tree could have a different time than the last.

    Bringing those together onto one sheet in Excel I could see where you would then get different values all competing for that one footer field.

    Still seems like an odd error however.

  • Community Member Profile Picture
    Community Member on at

    Our client too received this error & the @DateLong didn't seem to matter-still got the error -  but when I unmarked the box to Export to Single Worksheet under Microsoft Excel Options in the Export window, it exported fine - to 2 pages which the client doesn't want, but at least it is in Excel & they can reformat - like you have to do with most MR reports you try to export anyway...  Thanks!

  • Community Member Profile Picture
    Community Member on at

    I also experienced this error.

    Exporting to Excel from MR Viewer

    Export to single worksheet checkbox marked

    MR Version 2.0.1700.66

    After much testing i found that it was the company logo image that had been added to the report header that caused the problem.

    After the logo image was removed the report exported to excel without error to a single worksheet

    Note: Formatting changes and having 4 lines in the header or using the @DateLong auto text didn't seem to matter in this instance.

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 GP (Archived)

#1
HP-11021721-0 Profile Picture

HP-11021721-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans