Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
jbirco
Resolver I
Resolver I

ALM Toolkit Invalid Key-Value Set

Hello everyone! 

When trying to compare my local dataset with what I have online using ALM Toolkit, it returns me error:

'provider=msolap;Data source=powerbi://api.powerbi.com/v1.0/myorg/Workspace%20Name;Initial Catalog=Dataset Name;' is an invalid key-value set. parameter name; keyvalueset

Steps I took: 

Copied local server link > pasted in source workspace and selected dataset > Copied connection link from workspace settings> pasted in target workspace and selected dataset> Error

I triple checked spelling and assured that I am using the correct links for each workspace. Is there a workspace, tenant, or even semantic model setting that needs to be switched to address this error?

Looking for an explanation for the error and a direction towards a solution to avoid this error.

Thanks

1 ACCEPTED SOLUTION

Issue Resolved:

The initial catalog name had an apostrophe/single quote in it 🙃, which confuses the internal mechanism that parses the workspace link and dataset name. 

I realize that a better example to have used in my initial post would be:

'provider=msolap;Data source=powerbi://api.powerbi.com/v1.0/myorg/Workspace%20Name;Initial Catalog=Dataset's Name;' is an invalid key-value set. parameter name; keyvalueset


In the case that the semantic model or dataset name cannot be changed and has an apostrophe in it you can replace the apostrophe with a unicode " %27 " and it should work. 

View solution in original post

2 REPLIES 2
v-hashadapu
Community Support
Community Support

Hi @jbirco , Thank you for reaching out to the Microsoft Community Forum.

 

This error in ALM Toolkit usually happens because of a problem with the XMLA connection string used to connect to your Power BI (Fabric) workspace. ALM Toolkit connects through the XMLA endpoint and even small formatting issues in the connection string can cause this error.

 

Make sure the workspace you’re connecting to is in a Premium, Premium Per User (PPU) or Fabric capacity, ALM Toolkit won’t work with standard workspaces. Then, copy the XMLA endpoint directly from your workspace settings in Power BI, but use it exactly like this: powerbi://api.powerbi.com/v1.0/myorg/Workspace Name

 

Don’t include provider=msolap and don’t replace spaces with %20. The dataset (Initial Catalog) should be selected inside ALM Toolkit, not added to the connection string.

 

Also, confirm that the workspace has XMLA endpoint access enabled (Read/Write) under workspace settings and that you’re using the latest version of ALM Toolkit. Older versions may not support Fabric datasets or the current XMLA syntax.

 

Semantic model connectivity and management with the XMLA endpoint in Power BI - Microsoft Fabric | M...

Issue Resolved:

The initial catalog name had an apostrophe/single quote in it 🙃, which confuses the internal mechanism that parses the workspace link and dataset name. 

I realize that a better example to have used in my initial post would be:

'provider=msolap;Data source=powerbi://api.powerbi.com/v1.0/myorg/Workspace%20Name;Initial Catalog=Dataset's Name;' is an invalid key-value set. parameter name; keyvalueset


In the case that the semantic model or dataset name cannot be changed and has an apostrophe in it you can replace the apostrophe with a unicode " %27 " and it should work. 

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.