PowerBI semantic model's parameters get removed/not recognized after uploading through API

[theflashczech]

Hello everyone,

we've stumbled upon an issue with PowerBI reports. We're deploying semantic models to PowerBI Online using PowerShell scripts in Azure DevOps Pipeline and while doing so we also set parameters (Database, Table) and credentials for each semantic model (also through PowerShell).

We've encountered an issues saying "Dataset parameters at positions 1 - 2 cannot be found in ..." when trying to update the parameters.

I've checked that types of the parameters are not set to Any, they are set to Text. Loading is enabled as well, names are written correctly and even when I download the uploaded semantic model back to my device and open it up, I can see the parameters in Query Editor.

I tried verifying it by calling an API that retrieves parameters for specific dataset in specific workspace and indeed, no parameters are being returned.

I'm at my wits' end with this issue, has anyone ever encountered this issue?

[Anonymous]

Hi @theflashczech,

I wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If the community member's answer your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful.
If you need any further assistance, feel free to reach out.

Please continue using Microsoft community forum.

Thank you,
Pavan.

[Anonymous]

Hi @theflashczech,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please "Accept  as  Solution" and give a 'Kudos' so other members can easily find it.

Thank you,
Pavan.

[Anonymous]

Hi @theflashczech,

Thank you for reaching out in Microsoft Community Forum.

Thank you @Deku    for the helpful response.

As suggested by Deku,  I hope this information was helpful. Please let me know if you have any further questions or you'd like to discuss this further. If this answers your question, please "Accept as Solution" and give it a 'Kudos' so others can find it easily.

Please continue using Microsoft community forum.

Regards,
Pavan.

[Deku]

Are you using PBIP?

Are Rui's example Powershell library?

Are you updating prior to deployment or with API?

[theflashczech]

Thank you for answering so quick:

1) We're using PBIX files

2) Could you explain further what did you mean by the second point? I've written the PowerShell scripts myself using the MicrosoftPowerBIMgmt PowerShell module and Microsoft's documentation.

3) We're updating through API after deployment.

[Deku]

There is a example script for PBIP format

https://learn.microsoft.com/en-us/rest/api/fabric/articles/get-started/deploy-project

https://github.com/microsoft/Analysis-Services/tree/master/pbidevmode/fabricps-pbip

Are you using this API to check if the parameters exist? 

https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-parameters-in-group

Are you able to connected to the deployed sematic model with Tabular Editor to check if everything looks like it should?

[theflashczech]

Hello,

I apologize for the delayed response, I've looked into your points:

Yes, we are using the endpoint to check whether they exist, the result is negative though as only an empty list is returned.

Yes, we're able to connect through tabular editor, the parameters seem to be existing in the file itself but they are not being returned when requested through API, neither for reading nor editing.

[Anonymous · Accepted solution]

Hi @theflashczech,

Thank you for reaching out in Microsoft Community Forum.

Please follow below steps to resolve the error;

1.When deploying PBIX via PowerShell, parameters may not get promoted to the dataset metadata, causing the API to return an empty list.

2.Manually publish the PBIX once using Power BI Desktop to verify if parameters appear via the API.

3.Migrate to PBIP (Power BI Project) format for better DevOps support, where parameters are fully supported and accessible via REST APIs.

4.Use the GetDataset API to ensure the dataset is properly loaded and not in a partial or invalid state.

Please continue using Microsoft community forum.

If you found this post helpful, please consider marking it as "Accept as Solution" and give it a 'Kudos'. if it was helpful. help other members find it more easily.

Regards,
Pavan.