API - Default.GetBoundGatewayDataSources

[FrankT]

For some of my datasets the Get Bound Gateway Datasources operation will fail because the field 'isOnPremGatewayRequired' of the record wasn't found. At first sight this seems to be a bug!?

 [DataSource.Kind="PowerBIRESTAPI"]
 PowerBIRESTAPI.BoundGatewayDataSources = () =>
let
    source = Json.Document(Web.Contents("https://api.powerbi.com/v1.0/myorg/datasets")),
    value = Table.FromRecords(source[value]),
 selected = Table.SelectColumns(value, {"id", "name"}),
    BoundGatewayDataSources = Table.AddColumn(selected, "Call", each try Json.Document(Web.Contents( "https://api.powerbi.com/v1.0/myorg/datasets/" & [id]&"/Default.GetBoundGatewayDataSources", [
      Headers = [
                #"Content-type" = "application/json"
            ]])) otherwise null)
in
    BoundGatewayDataSources;
 

Expression.Error: The field 'isOnPremGatewayRequired' of the record wasn't found.
Details:
    id=25ec7826-1da2-4799-9dff-db84983ef86d
    name=RealTime
    addRowsAPIEnabled=TRUE
    configuredBy=XXXXXXXXXXXXX
    isRefreshable=TRUE
    isEffectiveIdentityRequired=FALSE
    isEffectiveIdentityRolesRequired=FALSE
 
Expression.Error: The field 'isOnPremGatewayRequired' of the record wasn't found.
Details:
    id=7ea173b5-1813-4bd9-9def-b40ecf89d0a3
    name=Report Usage Metrics Model
    addRowsAPIEnabled=FALSE
    configuredBy=XXXXXXXXXXXXX
    isRefreshable=FALSE
    isEffectiveIdentityRequired=FALSE
    isEffectiveIdentityRolesRequired=FALSE

The affected records seem to be either realtime or usage metrics or workbooks (Excel Services).

Indeed these records do not have the field isOnPremGatewayRequired.

Any ideas?

[v-jiascu-msft]

Hi @FrankT,

What data did you expect from this operation? Why not deleting the errors?

Best Regards,

Dale

[FrankT]

Naturally, I expect the API to give me the record fields available for each dataset. I do not ask for the missing field.

Furthermore, an error is returned despite " try ... otherwise"

[klinejordan]

Searching for help on this very topic - have you identified a workaround?