Hi, I am receiving an error message "Something went wrong. Please try again later. Session id: 16bd0304-b896-4b87-8b9a-68078b386703" when I click into Power Apps -> Admin Centre -> Data Integration. Please advise on what we can do. Thanks.
Best Regards,
Simon Chan
Solved! Go to Solution.
Update:
Data integration currently only supports the regions below:
Europe, US, Canada and Australia.
For other regions, it will show messages like "Something went wrong, Please try again later" or "Powerapps user:"XXX" has home tenant location: 'XXXX'.Data Integration is not supported in :'xxxx' region."
Regards,
Michael
Can anyone help? Thanks.
Just FYI that we have seen same issue http://disq.us/p/1mddzt3 (post from Ruchi) and there has been no response to the item
Hi All,
Thanks for the feedback.
Error message could be reproduced with a testing account.
I will send the feedback from my side, and post back if I got any response back.
Regards,
Update:
Data integration currently only supports the regions below:
Europe, US, Canada and Australia.
For other regions, it will show messages like "Something went wrong, Please try again later" or "Powerapps user:"XXX" has home tenant location: 'XXXX'.Data Integration is not supported in :'xxxx' region."
Regards,
Michael
We are seeing the same issue. It was working but when I changed the friendly name of our enviroment, (We are part of a much larger org and the smaller companies within are creating their own enviroments) I started to get this error.
Then the text below:
section Section1;
shared vw_WorkOrders = let
Source = Sql.Database("**ServerName**", "IME"),
Navigation = Source{[Schema = "dbo", Item = "vw_WorkOrders"]}[Data],
#"Changed column type" = Table.TransformColumnTypes(Navigation, {{"DocumentNo", type text}}),
#"Remove other columns" = Table.SelectColumns(#"Changed column type", {"DocumentNo", "DocumentDesc", "StatusCode", "BusinessUnit"})
in
#"Remove other columns";
**ServerName** is me replacing the SQL Server name for just this post. It does have it correct in the error text however.
This enviroment is in the US and is set to Production. This is activly effecting my ability to keep look up fields within the CDS up to date. I've had to fall back to a manual Excel File upload to the Entities which works fine. However, I would like to get this automated again.
EDIT: In trying to re-run the project after it was created. I received the following error.
Load to Common Data Service failed. Details:
DataPartition imelect for CDS is not valid, Valid DataPartitions are org2e2b95ac.
. (Job ID: 543b9311-055c-4582-a4a4-c0361d312fb7)
(So do I need to change the name from imelect bac to org2e2b95ac?)
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.
User | Count |
---|---|
207 | |
187 | |
83 | |
52 | |
37 |
User | Count |
---|---|
288 | |
245 | |
119 | |
77 | |
56 |