julian

My feedback

  1. 51 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    julian supported this idea  · 
  2. 71 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    julian supported this idea  · 
  3. 81 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    julian supported this idea  · 
  4. 95 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    julian supported this idea  · 
  5. 92 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    julian supported this idea  · 
  6. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    julian supported this idea  · 
  7. 118 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →

    Pleas see Kay’s comment below. Now that AS works on PQ, this of course becomes much easier. However still some work & testing to make each connector available, so likely will evaluate which are more suited to traditional BI and prioritize accordingly

    julian commented  · 

    This is a critical issue for my organization. We have our own internal APIs and they will not work in AAS Tabular 1400 level, but they do work in Power BI. In Power BI I was able to create a new "blank query" and copy M Query code from VS, and it worked instantly.

    In VS I can connect to my api/web service, create a query, and create a table, but no data will load. This is absolutely critical to our solution. There is an M Query function to call apis/web services (generic), which is the Web.Content function. But there is no Protocal for an api/web service in the Data Source Definition library.

    After all of my research, I can find examples of the json code for the .bim file to add a Data Resource Definition, but it appears that there exists no Protocol property specifically for apis/web services, and thus I cannot add my web service to the Data Sources section of the model. And therefore, my queries will not load the data, even though they will connect to the data surce (api) and allow me to navigate them and edit them, even showing the records in the Query Designer. But when I close and "process" the table, no records are imported.

    Please help and add "Web" and web service / api connectors protocols to the data source definition library asap for AAS Tabular 1400 level.

    julian supported this idea  · 

Feedback and Knowledge Base