Good afternoon,
I have been toying with PowerBI, importing BAQs with REST API. The last time I played around with this was a few months ago. Since then, I had to update my Epicor password. I guess my odata connection stored my authentication data, because when I tried to open PowerBI to one of my reports today, I got a locked-out error. I was actually logged into the desktop client at the time, and that’s where the user lockout error showed up. I think that odata tried to use my old credentials and attempted three times forcing Pilot to lock out my user for 15 minutes. It would have been nice if PowerBi noticed my credentials didn’t match and asked me for new creds, but it just silently maxed out my password attempts, locking me out of Epicor.
Has anyone else experienced this? Is there a good way to deal with it?
In the future I intend to have many PowerBI reports pulling data from Epicor and massaging it into nice charts to display around the shop. It would be rather impractical to find every report I made in PowerBI and open it to update the credentials. What’s the right way here?
(Please don’t say REST v2 and put in an API key…)
Thanks!
Nate
Since I am on a ChatGPT kick, I wanted to see what the robots think about this exact question. Here is the reply:
It sounds like you may have encountered an issue with your OData connection in PowerBI using outdated credentials. This can happen if the credentials stored in the connection are no longer valid or if the password has been changed since the connection was established.
One option you can consider is to update the stored credentials in the OData connection in PowerBI. To do this, you can follow these steps:
Open PowerBI and select the report or dashboard that is connected to the Epicor data source.
In the ribbon at the top, select the “Edit Queries” option. This will open the Query Editor.
In the Query Editor, select the “Data source settings” option.
In the Data Source Settings window, select the Epicor data source and then click the “Edit” button.
In the Edit Data Source window, enter your updated credentials and click “OK”.
This should update the stored credentials in the OData connection and allow you to refresh the report data without encountering the locked-out error.
It’s also a good idea to make sure that you are using the most recent version of the OData connector, as this may help to prevent similar issues from occurring in the future.
Alternatively, you could consider using an API key or a different authentication method for your OData connection, as you mentioned. This can help to avoid issues with outdated credentials and may offer additional security for your data.
