Direct Query SAP HANA Credential Lockout

[Anonymous]

Hey all,

General inquiry and may need some guidance here for best practice. When performing a Direct Query to a SAP HANA data source, I connect to the data source of interest (server/custom port), and  use a SQL statement in the advanced Query Editor to pull out the dataset I'm looking into. Once I put in my SAP HANA login credentials for the first setup time, things work as normal. I also publish the report with the SAP HANA data connection to Power BI service online. I'm using an on-prem gateway setup for me to test out direct query refreshes.

However, once I'm prompted to change my SAP HANA password from my work account at least once a month, I'm aware that my credentials that I used on Power BI will no longer suffice, so I'll have to change the credentials from the cluster I setup. I'll also have to change the permissions on Power BI Desktop once I make any edits or changes there. Once I change my login credentials on my Desktop, it seems like I somehow get locked out of accessing the credentials when I look at the same report on Power BI service. This is before I even publish the file online with my changed password. So I'm not sure if the issue is coming from when I open the file on Power BI Desktop, or when I attempt to open the same report on Power BI service, with potentially the old credentials saved on the gateway cluster.

Is there a particular order in how I should change the credentials to avoid future lockouts or data load issues once I change my password for a data source connection? Any guidance or perspective from past experience would be greatly appreciated--thank you!

[Terrance]

Under Data Source Type, select SAP HANA.

Add the SAP HANA data source

After you select the SAP HANA data source type, fill in the Server, Username, and Password information for the data source.

All queries to the data source will run using these credentials. To learn more about how credentials are stored, see Store encrypted credentials in the cloud.

After you fill in everything, select Add. You can now use this data source for scheduled refresh or DirectQuery against an SAP HANA server that is on-premises. You see Connection Successful if it succeeded.

Advanced settings

Optionally, you can configure the privacy level for your data source. This setting controls how data can be combined. It's only used for scheduled refresh. The privacy-level setting doesn't apply to DirectQuery. To learn more about privacy levels for your data source, see Privacy levels (Power Query).

[camargos88]

Hi @Anonymous ,

I've the same problem once. 

My password used to get locked if I input it wrong for 3x and I was pulling data from at least 4 tables from Hana.

Try to check it and you can use parameters to change the user and password online. Maybe it helps you.

Ricardo

[Anonymous]

Hey @camargos88 ,

That makes sense. I was able to change the user and password login online for the cluster and that solved the issue. Was I supposed to do that before or after I change the user/password on the report file itself?

If I change the password for my credentials online first, then do I have to close any related Power BI files beforehand?

[v-shex-msft · Accepted solution]

HI @Anonymous,

For 'direct query' mode data source, you need to keep its data credentials valid. (notice: it refreshed triggered every time users interact with visuals or table records)

So if you change your credentials on Datasource side, you also need to update your data source credentials on power bi service dataset side.
For local report file changes that apply to power bi desktop, it does not interact with published power bi service contents.

Regards,

Xiaoxin Sheng

[camargos88]

@Anonymous ,

No, if it's online it's another version,.... there is no relation with the file on your computer.

Ricardo