Forum Discussion
datasets.setAllConnections not working in Node SDK and CLI Tool (BUG?)
ok. I will. I wonder that this basic Function is not working.
michael
Thanks for fixing the issue. I now can upload the connection string.
Below my Request
WebResource {
rawResponse: false,
queryString: {},
method: 'POST',
headers:
{ 'Content-Type': 'application/json; charset=utf-8',
authorization: 'AppKey cAY0b0dCSSbg.......NzKAHhr7sukaxkZ9BfOL94gopjilKcdpLTKz0v2qMlw==' },
url: 'https://api.powerbi.com/v1.0/collections/powerbistart/workspaces/112efff......60-05da61ded3ba/datasets/a1baf74f-8831-....e1ea91fbfe8b/Default.SetAllConnections',
body: '{"connectionString":"data source=ServerName.database.windows.net;initial catalog=MyDB;persist security info=True;encrypt=True;trustservercertificate=False"}' }
Jsonstring [object Object]perhaps i missunderstood "initial catalog" ? I insert the db name there.
It seams not to work. I double checked everysting. The report is not updated. Yes i use directQuery.
Did anybody got this to work ?
P.S: If i reload the ifame everything is uptodated. Also if i check when the report was last refreshed it shows me the date of i triggered setAllConnections(). But the Data is still the same.
michael
- wabreza10 years ago
Microsoft Employee
Can you explain the new issue? You mentioned everything is up-to-date, but the data is the same...? Has the underlying data changed in your datasource?
- kobaldm10 years ago
Helper I
Yes the data changed. A new row is added every 30 sec. I would expect all visuals get updated when I trigger updateallconnections. They are not.
But if you go into zoom mode of a specific visual you get the time when the dataset was updated. It is the time I triggered updateallconnections. But still all visuals rely on the old data initial data i loaded powerbi embedded.
Does this help ?- wabreza10 years ago
Microsoft Employee
The report will not automatically update on the client side when new data becomes available. We are working on enhancements to the JavaScript SDK that will make this easier. Also - you should not have to call `setAllConnections` again. Assumming you setup your dataset as a direct query dataset then the data should be pulled on each report load as well as each intersection reqeust for new data (aka applying a filter).