Retention Policy for PowerBI Rest API not working

[mthsdiniz]

Hello guys,

I'm trying to use the PowerBI Rest API to create a live connection that update's the data everytime a new register is added on my oracle database...

I've created a streaming dataset with the "Historic Data Analisys" on, although i'm having trouble with the retention policy of this dataset.... Reading the Rest API documentation is said that the standard Retention Policy is FIFO, which would delete the first rows whenever i tried to push data into a 200k rows + dataset, although my dataset already contains 523627 rows and is causing me troubles limitind my push requests to 120 an hour.

Does anyway knows how to set / verify my retention policy or how to execute a DELETE action on this type of dataset?

Thanks!

[Anonymous]

Hi @mthsdiniz ,

AFAIK, REST API not able to effect streaming dataset records.(they not real stored in dataset tabels)
If you turn on Historic option, power bi will record history data from streaming dataset, you can try to use 'Datasets Delete Rows' API to remove these history records.

Push Datasets - Datasets DeleteRows

Regards,

Xiaoxin Sheng

[mthsdiniz]

Hey @Anonymous , 

I tried to use this command but the powershell says that this command is not recognized as the name of a cmdlet...

DELETE : The term 'DELETE' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I'm using power bi through my Organization (Cargill), so i do not have any Organization admin rights on power bi, i only have a premium workspace, although if admin rights are needed i can chat with the team responsible for that.

What should i do?

[Anonymous · Accepted solution]

Hi @mthsdiniz ,

For use power bi rest api, you need to register on azure side first.

Register an Azure AD application to use with Power BI

Then you need to find out correspond guid of your dataset.(you can navigate to that dataset to find out this key)

Regards,

Xiaoxin Sheng