web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Unable to Export Datav...
Power Apps
Suggested Answer

Unable to Export Dataverse Tables

(0) ShareShare
ReportReport
Posted on by
I've recently deployed a power app solution from a developer environment to a production environment. I am now unable to export data from any of the dataverse tables in the solution whilst in the production environment. The error I get is the following: 
 
The export service is not available: Connection set initialization failed for project DMExport_2026_06_04T08_09_12_789Z. Error: Dataset retrieval error
 
I am still able to export from the same solution whilst in the developer environment.
 
When using 'Edit in Excel' within the production environment, the file downloads and includes all the column headers but contains no data.
 
I am unable to export both custom tables and 'default' tables such as Account etc.
 
Thanks in advance for any help!
I have the same question (0)
  • Suggested answer
    timl Profile Picture
    37,214 Super User 2026 Season 1 on at
     
    This can often be caused by a transient error.
     
    If you try again later, the export service may be available and you won't get the error. 
     
    If it still fails, I suggest raising a support ticket with Microsoft.
     
    Here's a link to a post with the same issue. 
     
     
     
  • Suggested answer
    11manish Profile Picture
    3,333 on at
    Based on the symptoms, the most probable causes are:
    • Security role or table permission differences between environments
    • Office/Excel integration configuration issue in Production
    • Environment-level export service problem
    • DLP or governance policy restricting data export
    • Dataverse service issue specific to the Production environment
    The fact that standard tables such as Account are also affected strongly suggests the issue is not with the deployed solution itself but with the Production
     
    environment configuration or permissions.
     
    I would start by testing with a System Administrator account and comparing Office Integration and security settings between the two environments.

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard