Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
When I export a report containing opportunities to Excel, the value of some fileds (e.g Est. revenue) is shown as #VALUE. See screenshot. The field value is displayed correctly in the report.
I found a few people who had the same problem and it looks like an issue with the format of the cell you're exporting. There are multiple ways to get the same format, you may one to try another syntax.
Here are a few different format issues that all present the same way:
Hope this helps, if so I would appreciate if you would please mark this as the verified answer.
Microsoft provided the following workaround:
1. Run the report.
2. Export the report in “MHTML” format.
3. Post downloading the report, open it with Microsoft Excel.
4. The rows and columns containing the report on Excel will appear to be hidden.
5. Select All on the Excel sheet.
6. Right click and select the option which says “Unhide”.
7. You will be able to retrieve the accurate report without the “#Value”.
Thanks for the answer Aziz, this will be great when other people have the same issue.
Does anyone know if Microsoft have fixed this issue yet? or are we still reliant on the workaround provided?
Business Applications communities