Power BI API doesn't disable Direct Query, but example on reference says it should

[Anonymous]

There seems to either be a bug with the documentation or with the API.

https://docs.microsoft.com/en-us/rest/api/power-bi/datasets/update-direct-query-refresh-schedule 

When sending the "Disable a scheduled refresh example" I get:

{
  "error": {
    "code": "BadRequest",
    "message": "Bad Request",
    "details": [
      {
        "message": "Value cannot be null.\r\nParameter name: nullableType",
        "target": "datasetDQRefreshSchedule"
      }
    ]
  }
}

This is possibly an API error, since I get it directly from a Power Shell call, but if Direct Queries cannot have their Dashboard Tile and Metric Refresh disabled this way, it should be mentioned.

Is there something that I'm missing here?

[TomMartens · Accepted solution]

Hey @Anonymous ,

as you have noticed the API does not affect the Caching in DQ mode that helps to pre-populate Dashboard and Reports.
From my knowledge you can use this setting:

You will find this setting in the dataset settings, of course this setting is only available for DQ datasets.

Regards,

Tom

[Anonymous]

Hi @TomMartens Thanks for your response. I'm looking for a way to turn off the "Automatic dashboard tile and metric refresh" setting through the API. The documentation for DirectQueryRefresh (linked in the OP) states that you can do this ... but doing so has always created an HTTP 415 response. Looking through the C# source code (PowerBI-CSharp/DatasetsOperationsExtensions.cs at master · microsoft/PowerBI-CSharp · GitHub) I notice that the API command takes a DirectQueryRefreshSchedule object (serialized from the JSON payload) but that object doesn't take an "enabled" property (PowerBI-CSharp/DirectQueryRefreshSchedule.cs at b5882f53a7f5704fe70cbfb862b829e5bfc46472 · microsoft...)

public DirectQueryRefreshSchedule(frequency, days, times, localTimeZoneId)


This leads me to believe that either the documentation is faulty or that the API program is incomplete or that the behavior of something that intercepts the "enabled" setting isn't fully defined in the documentation (or is faulty).

I'm hoping someone out there can help me track down what exactly is going on and provide a way to modify this setting through automation.