β οΈ Deprecation Notice
Power BI template and connector support will be deprecated by January 2026.
Liongard recommends transitioning to Visual Insights, the in-platform reporting and dashboard solution that replaces Power BI templates and connectors.
The Power BI connector continues to function today, but support will be gradually phased out.
π Recommended Alternative: Visual Insights (Advanced Dashboarding & Reporting)
Overview π₯
When using the Liongard Power BI connector, you may encounter an issue where Power BI repeatedly prompts you to re-enter your Liongard API key when selecting data fields. This behavior prevents successful data loading and makes the connector unusable.
This article explains:
Why this issue occurs
How to resolve it step by step
Additional troubleshooting options
When to contact support
Recommended future alternatives
Why Does This Happen?π€
This issue is most commonly caused by authentication or credential validation failures between Power BI and Liongard. Typical causes include:
Cause | Description |
Expired or revoked API key | Power BI cannot validate requests |
Incorrect Base64 encoding | Credentials are rejected silently |
Cached credentials in Power BI | Power BI continues using invalid tokens |
Insufficient API permissions | Connector cannot access selected data fields |
Because Power BI validates credentials again when loading fields, any authentication mismatch results in repeated prompts.
Steps to Resolve π§βπ«
Follow all steps in order to fully reset authentication.
Step 1: Regenerate Your Liongard API Key
Log in to Liongard
Click your username (top-right) β Account Settings
Go to Access Tokens
Click Generate New Token
Securely store the Access Key ID and Secret
β οΈ Tokens are shown only once
Step 2: Encode the API Key in Base64
The Power BI connector requires Base64-encoded credentials.
Follow the official encoding instructions:
Configure Power BI Connector β Generate Credentials
Ensure:
No extra spaces
No line breaks
Entire string is copied correctly
Step 3: Re-Enter Credentials in Power BI
Open Power BI Desktop
Go to Data Source Settings
Remove existing Liongard credentials (if present)
Re-connect using your Base64-encoded API key
Reload the dataset
Additional Troubleshooting π¨βπ»
If the issue persists after completing the steps above, try the following:
β Clear Cached Credentials
In Power BI:
File β Options & Settings β Data Source Settings
Remove stored Liongard credentials
Restart Power BI
β Verify API Key Status
Ensure the API key:
Is active
Has not been revoked
Was generated by a user with sufficient permissions
β Confirm Account Permissions
The API token must be associated with a user that has read access to all datasets being queried.
Security Best Practices π€©
Treat API keys as sensitive credentials.
Store them in a secure password manager.
Never share API keys via email, chat, or public repositories.
Rotate keys periodically.
Expected Outcome π
After regenerating, encoding, and re-entering the API key, Power BI should:
Stop prompting for credentials.
Successfully load selectable data fields.
Allow report creation and refresh.
Transition to Visual Insights (Recommended) π
Because Power BI connector support is being deprecated, Liongard strongly recommends transitioning to Visual Insights, which offers:
Native dashboards inside Liongard
No external authentication or API key handling
Ongoing feature development and support
π Learn More: Visual Insights (Advanced Dashboarding & Reporting)
When to Contact Support π¦
Contact Liongard Support if:
The issue persists after regenerating credentials.
You are unsure about required permissions.
You need guidance migrating to Visual Insights.
Include:
Error behavior screenshots.
Confirmation that credentials were regenerated.
Power BI version details.

