I have created a new entity on powerapps and was trying to import some data. Was getting the below error when i try to do so:
The import service is not available: Connection set initialization failed for project ImportService_2018_06_01T23_19_30_909Z. Error: Connection set name DM_CdsToFile_39220ffa48854fa083e83f4b92ae392f_Ammar is not valid. Verify that no non-word characters are in the connection set name.
Solved! Go to Solution.
Looks like there are mutliple issues - We fixed one and looking into your issue now.
Appreciate your patience.
I am having the same issue . When i am in the app , i can see the data , edit and save them . But when it come to "export the data" i get this "
Sorry you are still experiencing an issue. There were 2 separate issues in the past, which have since been mitigated. We hotfixed it across all regions. I am equally surprised that you get same error. We'll take a look at it and get back to you. Appreciate your patience.
I get the same issue "The import service is not available: Connection set initialization failed for project DMImport_2018_12_05T16_54_37_585Z. Error: AX or CRM RuntimeUri was not found"
Still getting the issue here too.
The import service is not available: Connection set initialization failed for project DMImport_2019_01_03T16_22_09_697Z. Error: Service principal couldn't be written
I'm also getting this message: "The export service is not available: Connection set initialization failed for project <specificToInstance>. Error: Service principal couldn't be written". I've tried multiple browsers, no change in behaviour. I also tried to export entities with and without data. The CDS is the one for the "PowerApps Community Plan" and is fully upgraded (184.108.40.2066). I also applied the April 2019 updates to the environment.
Appreciate the details. We have diagnosed this issue to be specific to the Community edition. We are working with the corresponding teams to figure out a solution.
Thanks. I hope this is fixed. My official support ticket for this was closed as "this was by design" for the community edition. I am not sure what we are supposed to do with the community edition version if the CDS is crippled like this. It honestly might as well not be part of the community edition.
The fact that the training modules have users attempt this functionality presupposes that they'll get this working again. The "Create a model-driven application in PowerApps" learning path has a sub-module "Get started with the Common Data Service for Apps" where the export is used:
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!