Agostinho Ferreira

My feedback

  1. 14 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 →
    Agostinho Ferreira shared this idea  · 
  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Agostinho Ferreira shared this idea  · 
  3. 27 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 →
    An error occurred while saving the comment
    Agostinho Ferreira commented  · 

    This would be great to monitor cost by departments.
    Really hard to estimate the usage of resources by groups of models

    Agostinho Ferreira supported this idea  · 
  4. 16 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Agostinho Ferreira commented  · 

    Now is tricky but there are still some workarounds...

    Open only one Power BI model and then open the folder:

    %LocalAppData%\Microsoft\Power BI Desktop\AnalysisServicesWorkspaces

    • There should be an “AnalysisServicesWorkspaceXXX” folder which *** is a random number. Open that folder
    • Open “Data” folder
    • Find “msmdsrv.port.txt” in the folder and open it. It contains the random local SSAS instance port number used by Power BI Desktop
    • Open SQL Server Management studio and connect to the Analysis Services: localhost:XXXXX ( number you found on previous step)
    • Right click on database and Script -> Script Database as -> Create to-> New Query Editor

    Now you should have the XMLA query with the code so now you can copy and paste it against your Azure Analysis Services (give it a decent name instead of the Guid).

    From there you can download it to use the SSDT in Visual Studio 2017… but sometimes you can't because since the release of composite models the compatibility mode went from 1400 to 1465 which is not supported by the SSDT of Visual Studio 2017...

    The Web designer was good to accelerate design in Power BI (more friendly then SSDT)

    Agostinho Ferreira supported this idea  · 
  5. 210 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    Agostinho Ferreira supported this idea  · 
  6. 33 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 →
    Agostinho Ferreira supported this idea  · 

Feedback and Knowledge Base