User Profile
Paulo_Abreu
Frequent Visitor
Joined 3 years ago
User Widgets
Contributions
Power BI to CISCO Intersight
Anyone succeeded this connection? AFAIK you need a API key + Secret code to generate a HMAC signature and then access the endpoints of the API; Used some python code to accomplish that, without success; with a 401 error response from the API: Response body: {"code":"AuthenticationFailure","message":"Cannot process the request. The cookie 'X-Starship-Token' is invalid.","messageId":"iam_cookie_invalid","messageParams":{"1":"X-Starship-Token"},"traceId":"kPBKTK_HCM3RGHTCxjKAdUCKkdm0LZINYeJ0z6ygPg2QMGRPz9e9ag=="} Like if I still needed a token to make the connection? (I'm using the API key + Secret Code to generate the HMAC signature). Anything more simple?? (I'm not a programmer). ThanksSolved750Views0likes1CommentRe: Reload data problem via on premises gateway (Excel, Portugal locale)
Update! Hi again, Sorry, problem now has nothing to do with the column data or what I posted above, I thought it was because of the 1st problem but it isn't - sorry for that Problem now with the empty value is because the gateway can't access the network path where are the excel files, it complains with a DatasSource.Error I/O error 67 acessing the "Example file" on path "\\servername\Folder\ExampleFile.ls" ... Details: \\servername\folder It works internally and gateway has the correct permissions... if anyone has a light ... but I'll check this, maybe something very obvious. Thanks1.1KViews0likes1CommentRe: Reload data problem via on premises gateway (Excel, Portugal locale)
Hi GilbertQ Latest versions of PBI and gateway, this is a fresh new installation, latest downloads. Let me elaborate a little more, maybe there's a clue: When loading the excel tables I was getting an error converting the "sales" to decimal because the numbers had a "." separating thousands (a "," as decimal value) - this was strange since the version I had on my PC didn't exhibit that - so I replaced the "." with null on that column and numbers converted and showed correctly (PBI Desktop). After publishing the reload imediately showed a problem, these values were abnormally high, like 10x. I downloaded the .pbix and noticed the numbers were inflated like 10x, 8,20€ was showing as 820,00€ and so on. Only then I realized the "." was due to the locale region on server which was "Portugal (Pre-reform) or something like that, this format implied dots "." as thousands, so I changed the server to Portugal normal and it was ok, no more "." so I removed the step that was replacing these values. So, PBI desktop is fine (as it ever was), but afther publishing on service now all the values are gone, null. Bottom line: PBI Desktop perfect, refresh via Service is messing things up. My logic is they should be the same, unless something at the gateway level should be set differently, which I can't figure. I can try setting the excel column as number before reloading and see if this solves the problem... ? Thanks1.1KViews0likes2CommentsReload data problem via on premises gateway (Excel, Portugal locale)
Hi, need some help here, TIA! Folder data source, excel files, column with decimal value converts fine, everything OK in Power BI Desktop Publish to Service, when it refreshes data (just after publishing) values get garbled or just get null Server (the machine I have PBI Desktop and On premises Gateway) Region is Portugal, locale settings default, "," as decimal separator, "space" as thousands. Aparentely the gateway is not reading correctly this or some setting for Region on tenant I am missing? Re-installed on premises gateway, the closest region I see is "West Europe", let it be as it was. For now I have the on premises service stopped so that it doesn't update data and users can acess PBI service to check the report correctly. Will I have to change the Region settings on server to US and review the transform data accordingly or, what else? ThanksSolved1.2KViews0likes6Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.