Forum Discussion
Power BI API Parameters error - ActionNotSupported
Hello,
I have a problem with report and updating parameters. I'm developing the reports and our developers team have simple task - updating query parameters and usually it works and they are making it the same way for all the other reports, but this one is just not working.
So where is the problem now? We are deploying our reports to our company application (through PowerBI service) and in the report there are parameters for database (server and database) wich is different for every customer. And sometimes we need some more parameters and I have problems with them now.
Error reason (little bit anonymized):
Updating parameters for dataset: Report
One or more errors occurred. ({
"code": "InvalidRequest",
"message": "Dataset parameter at position 3 is invalid in 9d5357cc-4569-4422-a1db-b050ea2908ca. Reason: ActionNotSupported",
"target": "9d5357cc-4569-4422-a1db-b050ea2908ca"
})
At C:\anonymizedPath
+ Receive-Job -Job $j | Out-Null
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (Microsoft.PowerB...kePowerBIRestMethod:InvokePowerBIRestMethod) [Invoke-PowerBIRestMethod], AggregateException
+ FullyQualifiedErrorId : One or more errors occurred. ({
"code": "InvalidRequest",
"message": "Dataset parameter at position 3 is invalid in 9d5357cc-4569-4422-a1db-b050ea2908ca. Reason: ActionNotSupported",
"target": "9d5357cc-4569-4422-a1db-b050ea2908ca"
}),Microsoft.PowerBI.Commands.Profile.InvokePowerBIRestMethod
+ PSComputerName : localhost
Can anyone tell what does this error mean? Before you suggest that the parameters needs to be text and checked enable load....we already tried that.
Here is some output when we tried to call GET if the API at least sees the parameters in the report.
DatasetName DatasetId Name Type IsRequired CurrentValue
Report b5a73e30-111b-4c21-8688-19c083ee21de Server Text True devap…
Report b5a73e30-111b-4c21-8688-19c083ee21de Database Text True repor…
Report b5a73e30-111b-4c21-8688-19c083ee21de EntityID Text True Bom,C…
Report b5a73e30-111b-4c21-8688-19c083ee21de EntityURL Text True bom,c…
Report b5a73e30-111b-4c21-8688-19c083ee21de StaticURL Text True https…
Report b5a73e30-111b-4c21-8688-19c083ee21de URL fixed part1 Text True /repo…
Report b5a73e30-111b-4c21-8688-19c083ee21de URL fixed part2 Text True ?curr…
Report b5a73e30-111b-4c21-8688-19c083ee21de URL fixed part3 Text True &**bleep**…
Report b5a73e30-111b-4c21-8688-19c083ee21de FileNameOverview Text True DQM_L…
Report b5a73e30-111b-4c21-8688-19c083ee21de FileNameSummary Text True DQM_L…
I hope that anyone can help me with that and tell me where is the problem. I can provide some more information if needed. Thank you all in advance for any response.
Best regards, JK
6 Replies
codeautomationHelper I
This looks like a real Update Parameters API limitation rather than a simple “parameter not found” problem.
The GET output confirms Power BI can see the parameters, so I would focus on whether the semantic model itself is supported by Default.UpdateParameters.
Microsoft currently documents these important limitations:
- semantic models created or modified through the public XMLA endpoint are not supported by this API
- DirectQuery is supported only with enhanced dataset metadata
- Azure Analysis Services live connections are not supported
- parameter names are case-sensitive
- Any and Binary parameter types cannot be updated Microsoft Learn
Since the error points specifically to parameter position 3, I would test the update request with only the first two parameters, then add the third one back separately. That should help identify whether EntityID itself is unsupported or whether something in the query that consumes that parameter makes the action unsupported.
Also check whether this report/semantic model was ever modified through XMLA or uses DirectQuery without enhanced metadata, because either can cause this API to fail even when GET still returns the parameter list.
So I’d test in this order:
- Update only Server and Database.
- Update only EntityID.
- Verify the semantic model was not modified via XMLA.
- If using DirectQuery, confirm enhanced dataset metadata is enabled.
- Compare the Power Query usage of EntityID with one of the parameters that updates successfully.
The ActionNotSupported message usually points more toward the semantic model/query configuration than the parameter simply being text or load-enabled.
Thanks for the reply, I will try something and than I will let everybody know if I fixed it.
- v-csrikanth
Community Support
Hi jakubkral
We would like to inquire whether have you got the chance to check the solutions provided by other users in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
I already tried to look at the community solutions and did not find anything useful.
- ibarrau
Super User
Hi. Can you share something about your request to update parameters? You have shared the console response and it's talking about a wrong parameter call, so it might be a code issue. From just being able to see the get params and the error, I can only say that it looks like the update parameters is calling a dataset with id: 9d5357cc-4569-4422-a1db-b050ea2908ca but the get you are showing is clearly different b5a73e30-111b-4c21-8688-19c083ee21de.
I hope that helps,
That is not the problem. Because datasetID always changes after report upload. So the datasetIDs in messages are different. I was wondering if there is not problem about the parameters values, like they are too long, maybe some forbidden characters?
Like here are values that we are updating to the parameters (anonymized little bit):
- Param1: "webpage.otherpage.database.azure.com"
- Param2: "reports"
- Param3: "
Bom,Calendar,Customer,Inventory,Item,Manufacturing,Operation,Output,Purchase,Resource,Routing,Sales,Shift,Subresource,OrderExport,OperationExport,ResourceExport,PurchaseExport,MiscellaneousOne,MiscellaneousTwo,BomExport,CalendarExport,CustomerExport,InventoryExport,ItemExport,ManufacturingExport,OutputExport,RoutingExport,SalesExport,ShiftExport,SubresourceExport,MiscellaneousOneExport,MiscellaneousTwoExport
" - Param4:
"bom,calendar,customer,inventory,item,manufacturing,operation,output,purchase,resource,routing,sales,shift,subresource,orderexport,operationexport,resourceexport,purchaseexport,miscellaneous-one,miscellaneous-two,bomexport,calendarexport,customerexport,inventoryexport,itemexport,manufacturingexport,outputexport,routingexport,salesexport,shiftexport,subresourceexport,miscellaneous-one-export,miscellaneous-two-export"
- Param5: "https://webpage-website.page.com"
- Param6: "/reports/data/"
- Param7: "?current="
- Param8: "&analytics="
- Param9: "powerBIfilename"
- Param10 "powerBIfilename"
Is it somehow possible that this is the problem?
Thx for any help in advance.
