Dynamics AX Business Intelligence https://docs.microsoft.com/archive/blogs/dynamicsaxbi/feed.xml Sat, 28 Apr 2018 01:16:25 GMT en-US hourly 1 How To: Viewing reports as PDF documents https://docs.microsoft.com/archive/blogs/dynamicsaxbi/how-to-viewing-reports-as-pdf-documents Sat, 28 Apr 2018 01:16:25 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1605 OVERVIEW This article describes alternate viewing options for document reports in Dynamics 365 for Finance & Operations applications. The following scenario refers to the Customer base data report, however, these report management capabilities are enabled by default for most application solutions. Network printing instructions initiated using D365 applications are managed by an asynchronous service. The performance of this operation is largely influenced by network activity, size of the document, number of active printer jobs, and other non-deterministic factors.  As a result, this Print Destination method is problematic for business operations that require rapid (i.e. <30 second) document publishing.   To accommodate these scenarios, it is recommended that users render the document as a PDF file before sending it to a locally connected printer device. Let's start out by running an application report. For instance: [Accounts receivable > Inquiries and reports > Customers > Customer base data report] Unless over-ridden, the default Print Destination option for application reports is Screen.  The service produces an HTML rendering of the report as part of the user's interactive session. This allows users to take advantage of embedded links and non-paginated formatting. Here's the output… Viewing reports on Screen is recommended when using document reports to navigate the application. However, for companies where the preferred viewing option is PDF file, the D365 service platform offers options to change the default viewing experience for users.

VIEWING OPTIONS

Users may change the viewing experience when interacting with document reports using the Print Destination options provided in the report parameter dialog. Simply expand on the Destination section to update the viewing experience for the document report. Here's a screen shot of the dialog…. Note: these settings will be applied the next time you run the application report. After running the report, you'll be prompted to download the PDF file to your local device using your browser. Many browsers offer user the option to automatically open PDF files in another tab window. Here's the same report as a PDF file…

For more details, we have a walk-thru available that describes the viewing reports using non-interactive options.

ADMINISTRATOR OPTIONS

For organizations that prefer to print using locally connected devices, it’s recommended that they render documents as PDF files instead of HTML (e.g. screen).  This will allow for direct access to printers directly connected to the user's client device.  We've introduced a new Legal Entity configuration setting for businesses that prefer interacting with PDF files rendered by the D365 service.  It’s available under [Organization administration > Organizations > Legal entities].applications.

Here's a screen shot.... Select the “PDF File” option to switch the default document rendering experience for document style reports. This setting establishes the default viewing experience for users when accessing document reports in the D365 applications. Note: this Legal entity configuration option does NOT override the user’s previous settings where present.]]> Viewing reports using non-interactive options https://docs.microsoft.com/archive/blogs/dynamicsaxbi/viewing-reports-using-non-interactive-options Wed, 25 Apr 2018 21:39:36 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1525 TARGET - Microsoft Dynamics 365 for Finance & Operations The following article walks the reader through the process of running document style reports produced by Dynamics 365 applications using a background task. This is a great option for users that often finding themselves waiting for reports to render. By utilizing a background task to manage long-running reports, users are able to continue performing other activities while the service prepares the documents on the user's behalf. The following scenario discusses the Customer base data report, however, these report management capabilities are enabled by default for all document style application reports. Let's start out by running an application report for instance [Accounts receivable > Inquiries and reports > Customers > Customer base data report] Unless over-ridden, the default Print Destination option for application reports is Screen. This returns an HTML rendering of the report as part of the user's interactive session. However, for scenarios where a non-interactive session is preferred, the Dynamics 365 for Finance & Operations platform offers users the option to render reports using a background thread. Click here for 3-minute demonstration of the steps outlined below. Now, let's run the same report again. This time let's utilize a background task to assume responsibility for rendering the document with the parameters supplied by the user. In preparation, click on an application link used to access the report parameter dialog. Step #1) Create the non-interactive session for the report
  • In the report parameter dialog, expand the Run in the background section
  • Set the Batch processing flag to Yes
  • Update or take note of the Task description used to identify the operation
Step #2) Update the print destination settings
  • In the report parameter dialog, expand the Destination section
  • Select from Archive, Printer, or Email options
Note: In case you're wondering, the service prevents users from rendering report to Screen or File when running in the background. Step #3) Monitor the progress of the background task (Optional)
  • If you have sufficient permissions in the system, you can check the status of the Batch job
  • Use the Batch Job form [System administration > Inquiries > Batch jobs]
  • Search for the background task using the Task description from step #1
  • Verify that the background task is complete
Step #4) Retrieve the document from the Print Archive
  • Locate the background task using the Print archive form [Common > Inquiries > Print archive]
  • Select the document from the list and then click on the Print preview button to access the report
Reminder - the service prevents users from rendering the report to Screen & File when running in the background. ]]> How To: Upgrading Document Routing Agents https://docs.microsoft.com/archive/blogs/dynamicsaxbi/how-to-upgrading-document-routing-agents Thu, 15 Feb 2018 05:25:39 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1485 Platform Update 12 Release includes a number of significant enhancements in components used to deliver network printing capabilities for Dynamics 365 for Finance & Operations applications.  These updates include a re-imagined print job queue management solution that provides customers with a more robust service capable of scaling to satisfy the needs of enterprise deployments. Although, the Cloud service is backwards compatible with existing deployments of the Document Routing Agent (DRA), it is highly recommended that customers upgrade servers used to host the DRA to align with version of the Cloud service. Failure to upgrade existing installments of the Document Routing Agent to PU12 or later may result in the following:
  • Observable performance degradation in the Dynamics 365 for Finance & Operations applications
  • Potential loss of documents associated with orphaned print jobs
  • Inconsistent handling for printed documents with custom margins
IT Admins must perform the following steps on each domain resource used to host a Document Routing Agent for Dynamics 365 for Finance & Operations. Getting started… To continue running the Document Routing Agent as windows service, you'll need both the user name and password of the domain account used to run the service. This information must be available after completing the upgrade process. The active service account information can be accessed in the open “Services” window and find the “Microsoft Dynamics 365 Document Routing Service”.

Step 1) Uninstall existing Document Routing Agent (DRA)

Open the Programs and Features window, find Microsoft Dynamics 365 for Finance and Operations: Document Routing, and then click the Uninstall button During the uninstallation process, you'll likely be prompted with the following dialog… Important: select “Automatically close applications and attempt to restart them after setup is complete.”

Step 2) Now, reinstall the latest Document Routing Agent available in your deployment

Use the instructions provided here to download and install the latest version of the Document Routing Agent available with your subscription.]]> Adding analytical reports to Dynamics 365 for Operations https://docs.microsoft.com/archive/blogs/dynamicsaxbi/adding-analytical-reports-to-dynamics-365-for-operations Thu, 02 Nov 2017 18:24:28 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1445 INTRODUCTION This article provides a walk-thru for Application Developers seeking to add an analytical report to a Dynamics 365 application.  For this scenario, we will extend the Reservation Management Workspace in the Fleet Management application to include a direct link to an analytical report authored against the Entity Store using Power BI Desktop.

OVERVIEW

Whether you are extending an existing application Workspace or introducing one of your own, analytical reports can be used to deliver insightful and interactive views of your business data.  The process for adding an analytical reports is broken down into the following actions:
  • TASK #1 - Add the PBIX file as a resource to your model
  • TASK #2 - Introduce a Menu Item to control access to the report

PRE-REQUISITES

  • Access to a Dynamics 365 developer environment running on Platform Update 8 or later
  • Analytical report (.PBIX file) authored using Power BI Desktop with a data model sourced from the Dynamics Entity Store Database
  • IMPORTANT:  Use the steps described here to enable Analytical solutions in a 1Box environment
Note:  For detailed instructions on authoring Analytical Workspaces & Reports using Power BI Desktop take a look at the article Authoring Analytical Workspaces & Reports.

WALK-THROUGH

TASK #1 - Add the PBIX file as a resource to your model To begin, you'll need to author or obtain the Power BI Report to embed in the workspace.  For more information on creating analytical reports, review the Getting started with Power BI Desktop literature. Use the following steps to add a PBIX file as an Operations Resource artifact:
  • Create a new project in the appropriate model
  • Select the Project in the Solution Explorer, then right + click and select Add > New Item
  • In the Add New Item form, select the Resource template under Operations Artifacts
  • Provide a Name to use when referencing the resource then click Add
  • Now, locate the PBIX file containing the Analytical report definition and then click Open
Now that you've added the file named AnalyticalReport.PBIX as a model resource called 'PowerBIReportName', you can begin adding menu items that reference the report. TASK #2 - Adding link to Analytical Report from Reservation Management Workspace Use the following steps to extend the form definition for the Reservation Management Workspace
  • Select the Project in the Solution Explorer, then right + click and select Add > New Item
  • In the Add New Item form, select the Display Menu Item template under User Interface
  • Provide a name to use when referencing the report in X++ metadata then click Add
  • Open the Menu Item designer for the new item
  • In the Properties window, set the Object Type value to Class
  • In the Properties window, set the Object value to PBIReportControllerBase
  • In the Properties window, set the Parameters value to the name of the new Resource (note: this item was created in Task #1 'PowerBIReportName')
  • Now, rebuild the project and open the application
  You're done.  You can now access the Analytical Report directly using the new application menu item. Either add the Menu Item to an existing Application Menu or business logic to embed the solution into your application.]]> Accessing Analytical Workspaces and Reports on 1Box environment https://docs.microsoft.com/archive/blogs/dynamicsaxbi/accessing-analytical-workspaces-on-1box-environment Sat, 29 Jul 2017 19:04:30 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1395 INTRODUCTION This article describes the process for enabling Analytical Workspaces & Reports in Dynamics 365 for Operations 7.2 Release on a 1Box environment.  This information is intended for partners, VARs, and ISVs that wish to showcase Analytical Applications using a 1Box environment.  As described in the Power BI Embedded Integration article, the hosted service used to deliver embedded analytics is only available on High-Availability deployments.  The Power BI Embedded service is not configured for 1Box environments.  As a result, the embedded Analytical Applications only available in High-Availability environments. The following describes a *hack* that can be used to access the Analytical Workspaces & Reports on a 1Box environment.  To utilize this solution, you will need to deploy resources using the Azure portal on your subscription including an Azure SQL Server Database Premium (P1) edition to host the Entity Store.  To keep costs at a minimum, be sure to turn on the Azure services only when needed. Note:  This configuration process an only be performed on a 1Box environment.  The service configuration settings are inaccessible in multi-box deployments.

OVERVIEW

In short, to access the Analytical Applications on a 1Box deployment, you'll need to deploy your own Power BI Embedded Service and Entity Store Database.  It's simple to do.  However, you'll need Administrative access to an Azure Subscription and a Dynamics 365 for Operations 1Box environment. Essentially, this process includes the following steps:
  1. Deploy the Power BI Embedded service on your Azure subscription
  2. Deploy a SQL Database on your Azure subscription
  3. Publish the Entity Store database on your Azure subscription
  4. Configure the local 1Box environment to point at your Power BI Embedded service
Here's a screen shot of an Analytical Workspace in the Application Suite The first step, is to Deploy the Power BI Embedded service on your Azure subscription.]]> Deploy Power BI Embedded Service for Dynamics 365 for Operations https://docs.microsoft.com/archive/blogs/dynamicsaxbi/deploy-power-bi-embedded-service-for-dynamics-365-for-operations Sat, 29 Jul 2017 19:03:15 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1375 Analytical Workspaces and Reports in a Dynamics 365 for Operations 1Box environment. Major "Thanks" to Helmut Wimmer for co-authoring this content

What happened to the legacy Power BI Embedded product in Azure?

The Azure gallery item for Power BI Embedded has been renamed to Power BI Workspace Collections. The resource itself was called Power BI Workspace Collection and remained as is. "Workspace Collections" will denote the previous service in documentation and UI.  Power BI Workspace Collections is on a deprecation path.  Those who are already using "Workspace Collections" solution can continue to use it till end of June 2018.  New Power BI embedded solution has many new features, and Dynamics 365 for Operations will be shifting to the new service soon.

Service Availability

The Power BI Workspace Collection service is available in the following regions:  Australia Southeast, Brazil South, Canada Central, East US 2, Japan East, North Central US, North Europe, South Central US, Southeast Asia, UK South, West Europe, West India, West US  

Deploy the Power BI Workspace Collection in your Azure Subscription

  • Access the Microsoft Azure Portal:  https://portal.azure.com
  • Select the New button in the left navigation to create a new Azure Resource
  • Enter Template deployment in the search box to begin
  • Click on the Create button

  • In the Custom deployment, click on Build your own template in the editor

  • Paste the following in the template editor, then replace the ***VALUES*** with your choices:

  • IMPORTANT

    • Select the target ***Region*** from the Service Availability list above
    • Take note of the Workspace Collection resource ***Name*** value for later
    • Make sure there are no extra line breaks when you paste into the Azure portal editor

{ "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": {}, "resources": [ { "type": "Microsoft.PowerBI/workspaceCollections", "sku": { "name": "S1", "tier": "Standard" }, "name": "***ADD YOUR AZURE RESOURCE NAME HERE ***", "apiVersion": "2016-01-29", "location": "***SELECT YOU REGION***" } ] }

Here's a screen shot of the edit with the template supplied:

  • Click on the Save button
  • After saving the template, choose a Resource group or create a new one, choose the Azure location of your Power BI Embedded Workspace
  • Click on the link to Purchase button
  • Once the service is created, access the new Power BI Workspace Collection from the Azure Dashboard
  • In the left navigation, under the General section click on the Access keys link
    • Important:  Take note of the values captured in the KEY 1 and KEY 2 text boxes
Now, you are ready to deploy the SQL Database Server onto your subscription using the Azure Portal.]]> Deploy Azure SQL Server for hosting Entity Store Database https://docs.microsoft.com/archive/blogs/dynamicsaxbi/deploy-azure-sql-server-for-hosting-entity-store-database Sat, 29 Jul 2017 19:01:48 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1346 previous step.  Entity Store Database utilizes non-clustered column index store (NCCI) which is only supported on the Premium tier of SQL.  For more details review the article here. Deploy a SQL Database Server in your Azure Subscription

1. Access the Microsoft Azure Portal:  https://portal.azure.com 2. Select the New button in the left navigation to create a new Azure Resource 3. Enter SQL Database in the search box to begin

4. Provide a Database name for the new resource 5. In the Select source property, select Blank database 6. Expand the Server fly-out to Configure required settings 7. Provide a Server name, Server admin login, and Password for the SQL Server Important:  Take note of the Server Name, Server admin login and Password provided here

8. Click on the Select button to use the newly created server 10. Expand the Pricing tier fly-out menu 11. Select Premium pricing tier for the new SQL Database with the minimal allocations Note:  Premium tier supports Non-clustered column index store (NCCI) which is required by the Entity Store database.  For more details review the article here.

12. Click on the Select button to close the fly-out 13. Click on the Create button to create the SQL Server Database

Now, you are ready to publish the Entity Store database from a local 1Box development environment.]]> Publish the Entity Store database on Azure SQL Server https://docs.microsoft.com/archive/blogs/dynamicsaxbi/publish-the-entity-store-database-on-azure-sql-server Sat, 29 Jul 2017 19:00:03 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1335 previous step. Before you proceed, be sure to process the Aggregate Measurements using the Dynamics 365 Administrative Tools to populate the database.  Use the following steps to seed the Entity Store database with sample data for the Application Suite's Analytical Workspaces & Reports.

Processing Aggregate Measurements in Dynamics 365 for Operations (15 mins)

1. Log into the Dynamics 365 instance running locally: https://usnconeboxax1aos.cloud.onebox.dynamics.com Note:  Ensure that you are using an account with Admin privileges

2. Navigate to the Aggregate measurements admin form [System administration > Setup > Entity Store] 3. Click on the check box next to Name to select all items in the list 4. Once you've selected the models you need, click on the Refresh button in the ribbon

5. Click on the OK button in the fly-out to trigger a refresh

Allow this process to complete in the background (~5 - 10mins).  You can monitor the status of the background process using the Batch jobs form [System administration > Inquiries > Batch jobs].  Search the list for the Deploy measurement jobs in the list to track progress. Once the Progress of the Batch job reaches 100.00 you are ready to publish the local Entity Store database onto your Azure SQL Server.  Use local tools on your 1Box machine to export the local Entity Store database as a BAK file

Export Entity Store database hosted on the 1Box (20 mins)

1. Open Microsoft SQL Server Management Studio (SSMS) on the local 1Box environment Note:  Ensure that you are using an account with Admin privileges

2. Connect to the local Database Engine - you'll notice a collection of databases present in the local instance. 3. Select the database named AxDW, this is the local Entity Store database 4. Right + click on the AxDW, select Tasks, and then select Export Data-tier Application 5. Click on the Next button in the wizard 6. Supply a file path and a file name for the exported database (*.BACPAC file) 7. Click Finish to initiate the process

Publish Entity Store database BAK file to Azure SQL Database (70 mins)

1. Open Microsoft SQL Server Management Studio (SSMS) on the local 1Box environment Note: Ensure that you are using an account with Admin privileges

2. Connect to the Azure SQL Database Server created in the previous step using the database connection string:  *.database.windows.net 3. Update the Authentication: method to SQL Server Authentication 4. Provide the Login and Password credentials used when creating the Azure SQL Server 5. Click the Connect button to access the Azure SQL Server Note: You'll be prompted to log into your Azure subscription to connect to the Azure SQL Server

6. Once connected, expand the root node and selecte Database 7. Right + click the folder and select Import Data-tier Application 8. Click on the Next button in the wizard 9. Locate the Entity Store database back-up file (*.BACPAC file) 10. Click on the Next button in the wizard 11. Provide a New database name like AxDW Important:  Take note of the Database Name provided here

12. Update the Edition of Windows Azure SQL Database value to Premium Note: Entity Store Database utilizes Non-clustered column indexes (NCCI) which is only supported in Premium edition

13. Click on the Next button to begin importing Entity Store Database

As a final step, you'll need to modify the web configuration settings on the 1Box development environment to utilize the new Azure resources.]]> Configuring 1Box to enable Analytical Workspaces and Reports https://docs.microsoft.com/archive/blogs/dynamicsaxbi/configuring-1box-to-enable-analytical-workspaces-and-reports Sat, 29 Jul 2017 18:57:40 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1316 previous step.  Use the instructions below to enable Analytical Workspaces & Reports in a 1Box environment using the Power BI Embedded service hosted on your Azure subscription. To continue make sure you have the following information: Entity Store Database Service details:
  • Database name:  Name provided in the database settings
  • Server name:  Azure SQL Server name (*.database.windows.net)
  • Server admin login:  User name supplied in the SQL Server settings
  • Password:  Account password supplied when configuring SQL Server
Power BI Embedded Service details:
  • Workspace Collection Name: The name of the Workspace Collection created when deploying the Power BI Embedded Service
  • Access Key1:  The secret key #1 used to access the Power BI Embedded service
  • Access Key2:  The secret key #2 used to access the Power BI Embedded service
KEEP THESE KEYS CONFIDENTIAL...!  You'll want to protect this information as appropriate to prevent exposing Azure services to others.  Developers can use this information to remotely access the Power BI Embedded Service and SQL Azure Database Server.  Microsoft is not responsible for the implications of sharing these service keys with others.  Should this information become compromised, use the Azure Service Portal tools to regenerate the Power BI Embedded service security keys.

Configure 1Box environment to enable Analytical Workspaces & Reports

  1. Open the File Explorer on the local 1Box environment
  2. Navigate to the root folder for the local Dynamics 365 for Operations deployment (e.g. C:\AOSService\webroot)
  3. Recommend that you make a copy of the web.config file before making any changes
  4. Edit the web.config file in the folder using Notepad
  5. Update the Entity Store Database configuration settings:

<add key="BiReporting.DW" value="[Database name]" /> <add key="BiReporting.DWServer" value="[Server name]" /> <add key="BiReporting.DWRuntimeUser" value="[Server Admin login]" /> <add key="BiReporting.DWRuntimePwd" value="[Password]" />

6. Update the Power BI Embedded Service configuration settings:

<add key="PowerBIEmbedded.AccessKey" value="[Access Key1]" /> <add key="PowerBIEmbedded.AccessKey2" value="[Access Key2]" /> <add key="PowerBIEmbedded.ApiUrl" value="https://api.powerbi.com" /> <add key="PowerBIEmbedded.IsPowerBIEmbeddedEnabled" value="true" /> <add key="PowerBIEmbedded.WorkspaceCollectionName" value="[Workspace Collection Name]" />

7.   Close Notepad and Save your changes 8.   Open Command Prompt 9.   Reset IIS to apply the changes using the command:  iisreset 10. Once it completes, launch the Dynamics 365 for Operations instance running on the local 1Box, and access an Analytical Workspace [Manage customer credit and collections]

You're ready to go...!  You can now access the Analytical Workspaces & Reports in the Application Suite using the local 1Box deployment.  The Dynamics 365 application automatically deploys Power BI reports on-demand so there's no need to manually deploy reports.]]> Introducing the Power BI solution template for Credit and Collections https://docs.microsoft.com/archive/blogs/dynamicsaxbi/introducing-the-power-bi-solution-template-for-credit-and-collections Tue, 25 Jul 2017 20:36:35 GMT https://blogs.msdn.microsoft.com/dynamicsaxbi/?p=1306 Power BI solution template for Dynamics 365 Finance and Operations for Credit and Collections analytics. Purpose of this blog post is to explain who should use this solution template any why should they use it. Before we start, see this video for a quick tour. You probably know what Power BI solution templates are. If not, this blog post is a great introduction.

Analytical workspaces and solution templates

I trust that you read the blog post on Analytical workspaces posted by my colleague TJ. As mentioned in the blog post, Analytical workspaces offer an Analytical view of operational data. A single Analytical workspace combines information provided with many operational reports. Built using embedded PowerBI (or, a version of PowerBI included within Dynamics 365 for Operations), analytical workspaces appear as a new Tab within workspaces. If you have a PowerBI report that was authored using Entity store, an AX developer can convert that report into an Analytical workspace by following the links provided in the post. Analytical workspaces are available to all users of Dynamics 365 for Operations – whether they have a PowerBI.com license or not. In fact, a user does not need a PowerBI.com account to be able to use analytical workspaces within Dynamics 365 for Operations. Data shown in Analytical workspaces are sourced from Entity store – the operational data warehouse included with Dynamics 365 for Operations. You can extend ready-made analytical workspaces or create new ones using data in entity store. But what if you wanted to include your own data into reports – ie. data that’s not housed in Dynamics 365 for Operations into the same report? – what if you wanted to include data from your legacy data warehouse or perhaps data from cloud sources? The answer is ... Power BI solution templates. With the Solution template for Credit and Collections, In just a few minutes, you can stand up an end-to-end solution including data extraction, Azure SQL Server, Azure Analysis Services, and ready-made Power BI reports. This solution is provisioned in your own Azure subscription - you can extend the solution by incorporating other data and business logic. Credit and Collections Power BI solution template features the richness contained within the Credit and collections Analytical workspace included in the spring release of Dynamics 365 for Operations.

Kick-start your data mart project using Solution templates…

For Operational reporting on Dynamics 365 for Operations data, Entity store and analytical workspaces may be a cost effective option. But if you have an existing Data warehouse or want to develop a data mart for Credit and collections analysis, solution templates are a great starting point. As opposed to standing-up a database and developing ETL scripts to extract and transform data from dynamics 365 for Operations, solution template deploys a ready-made solution in your subscription. You can tweak the solution deployed and modify the components as you see fit.

Use Solution templates to package your BI solution

If you are an ISV or a partner, you may have built content to be distributed as Analytical workspaces with the spring update of Dynamics 365 for Finance and Operations. Now, you have an opportunity to package the same content as a Solutions template and make it available in AppSource. Using the code samples freely available on GitHub  you can package your content as a solution. You can submit your solution to existing gallery of solution templates by sending a mail to pbisolntemplates@microsoft.com If you have a custom data warehouse solution that was built using Dynamics 365 for Operations data, you could package and deploy the solution using solution templates – as opposed to writing your own deployment and installation code.

Give it a try…

This is the first of many solution templates to come. We plan to release solution templates corresponding to ready-made PowerBI content available as Analytical workspaces. Give it a try and tell us what you think. Also, please tell us which of the ready-made Analytical workspaces that you would like to see as solution templates soon.]]>