Http error 406 when calling reporting API

Officially Answered

Comments

2 comments

  • Avatar
    7pace tech support

    Hi!

    Thank you for your message and my apologies for the issues you are experiencing.

    It is a known issue, it is presented in the latest versions of Excel and Power BI and it was already reported to Microsoft.

    Here is a related topic in Power BI 

    As a workaround, you could use the Advanced Query Editor in Excel:

    Enter the function invocation by hand from looking at the function definition within the Excel advanced query editor view e.g.

    Replace Odata url with correct one (without query like "api-version"="2.1")

    ---

    let
    Source = OData.Feed("Timetracker Odata url address", null, [Query=[#"api-version"="2.1"]]),
    #"TimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table" = Source{[Name="TimeExport",Signature="function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table"]}[Data],
    #"Invoked FunctionTimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table1" = #"TimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table"("2018-01-01", "2018-12-31", null, null, null)
    in
    #"Invoked FunctionTimeExport_function (startDate as text, endDate as text, populateTopParentColumns as nullable logical, groupTimeByDateByUser as nullable logical, includeBillable as nullable logical) as table1"

    ----

    Let me know if this can help you.

    Kind regards,

    Andarth

    1
    Comment actions Permalink
  • Avatar
    Cédric Noureau

    Hi again,

    Thank you for your quick answer !

    It works with the workaround you provided.

    Many thanks !

     

    Regards,

    Cédric

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk