Closed rhalabi closed 2 years ago
Hi, I got the same error since yesterday... after some tests, it seem that the "$top1" is triggering the error, but i'm not 100% sure.
As a workaround,I used the getData function under the "Functions" folder
This is the M code I used for this workaround (sorry, the steps are in french)
let Source = PowerBIRESTAPI.Navigation(), Functions = Source{[Key="Functions"]}[Data], GETData1 = Functions{[Key="GETData"]}[Data],
#"Converti en table" = Record.ToTable(#"Fonction appeléeGETData1"),
#"Lignes filtrées" = Table.SelectRows(#"Converti en table", each ([Name] = "value")),
#"Value développé" = Table.ExpandListColumn(#"Lignes filtrées", "Value"),
#"Value développé1" = Table.ExpandRecordColumn(#"Value développé", "Value", {"id", "isReadOnly", "isOnDedicatedCapacity", "capacityMigrationStatus", "description", "type", "state", "name", "reports", "users", "datasets", "dataflows", "dashboards", "capacityId", "pipelineId", "dataflowStorageId"}, {"id", "isReadOnly", "isOnDedicatedCapacity", "capacityMigrationStatus", "description", "type", "state", "name.1", "reports", "users", "datasets", "dataflows", "dashboards", "capacityId", "pipelineId", "dataflowStorageId"}),
#"Colonnes supprimées" = Table.RemoveColumns(#"Value développé1",{"Name"}),
#"Colonnes renommées" = Table.RenameColumns(#"Colonnes supprimées",{{"name.1", "Workspace Name"}, {"isReadOnly", "Is Read Only"}, {"isOnDedicatedCapacity", "Is On Dedicated Capacity"}, {"capacityMigrationStatus", "Capacity Migration Status"}, {"description", "Workspace Description"}, {"type", "Workspace Type"}, {"state", "Workspace State"}, {"id", "Workspace ID"}})
in
Thx I will wait for developer to maybe fix the .mez file. I am not too technical to update the connector with M code.
No problem. However, I didn't update de connector, I just create a new source/connection in my PowerBI... and instead of using the "Workspace User (Admin)" connector, I used the GETData connector that is already provided under the "Functions" folder (we can see this folder in your print screen).
If you want, you can add a new blank source in your powerBI and copy/paste the M code ... it should work as a starting point for this workaround.
I can repro this, my guess is something changed with the API because I can't even make these calls in Postman.
This will take an escalation to Microsoft to figure out
I can repro this, my guess is something changed with the API because I can't even make these calls in Postman.
This will take an escalation to Microsoft to figure out
Thx for the reply. Is anyone reaching out to Microsoft why this is occurring?
Just curious if any update, if anyone is working on fixing this?
This looks to be working again. Not sure what changed.
This started occurring again today.
I can't reproduce it unfortunately, in either the connector or Postman
Very strange working ok today.