Forum Discussion
Teradata refresh issue
- 4 years ago
Hello and thanks for the answer.
I found what was wrong in my api calls.
I was using the api "Datasets - Bind To Gateway" (Datasets - Bind To Gateway - REST API (Power BI Power BI REST APIs) | Microsoft Docs) but by design :
Binds the specified dataset from the workspace to the specified gateway, optionally with a given set of data source IDs. If you don’t supply a specific data source ID, the dataset will be bound to the first matching data source in the gateway.
That was the explanation !
Maybe it will help future usages.
Hi FXFelix,
According to your decision, it seems like PowerShell has cached the credentials that you inputted at the first operations. When you work with the second operation which requires different credentials, PowerShell uses the cached one for authorization and it failed due to credentials not matching.
If that is the case, I think you may need to do some cache clear or sign-out operations before you do the second one.
Regards,
Xiaoxin Sheng
- FXFelix4 years agoResolver I
Hello and thanks for the answer.
I found what was wrong in my api calls.
I was using the api "Datasets - Bind To Gateway" (Datasets - Bind To Gateway - REST API (Power BI Power BI REST APIs) | Microsoft Docs) but by design :
Binds the specified dataset from the workspace to the specified gateway, optionally with a given set of data source IDs. If you don’t supply a specific data source ID, the dataset will be bound to the first matching data source in the gateway.
That was the explanation !
Maybe it will help future usages.