This article explains how to deploy the PRE-BUILT OnePlan reports. OnePlan pre-built/configured reports align to the tables & general reporting elements of the OnePlan environments. Generally, to deploy, you'll need to update the data sources to your OnePlan group, make any additional changes, and publish to Power BI online to share with your team.
Follow the steps in this article for each report to deploy.
Important! First, download the pre-built OnePlan reports. Refer to the articles based on your OnePlan solution configuration: Report Templates
If you haven't done so yet, you'll need to get your OnePlan group's specific reporting OData feed & key. Refer to this article how to get your oData feed URL & Reporting Key details: Set up OnePlan oData Reporting
Open one of the downloaded pre-built OnePlan templates (.pbit files) in PowerBI Desktop. All the data in the standard OnePlan report comes from the OnePlan OData feed. If other Data sources are used, such as with data from SharePoint, PowerApps (CDS), etc., you would need to also update the data sources for those data sources as well.
As soon as you open the OnePlan report template, you will be prompted to enter your OnePlan group's oData feed URL. You need to update the data source to point to your specific OnePlan group/environment for your data.
Enter the URL into the prompt.
Enter the Reporting key name & key for your OnePlan group (as gathered in the article referenced above for Reporting Setup).
Select Basic as the type.
For the User Name & Password fields - Enter "Reports" for the User Name and the "OnePlan Key" that was generated in a previous step as the Password.
Select to which level to apply these settings - Select your FULL OData Feed URL.
Click the Connect button.
You may not be prompted for future reports connecting to this same OData Feed URL, as the credentials get saved in the Global Permission of your local instance of Power BI Desktop.
The report will refresh all the OnePlan data tables with your OnePlan data. A window will show the progress of applying your data source.
If any configuration of your reports need to be updated, now is the time to do it. It's a good idea to verify each tab/page to ensure the visuals don't have any issues or errors. Add/update any filters, etc.
After the report updates with your OnePlan group's data, and you have verified it all looks good, it is time to publish the report to PowerBI. If you don't yet have a workspace for your report, create one in Power BI online BEFORE publishing.
Be sure you are logged into Power BI Desktop with YOUR Office 365 account user name and password. Save your report file locally on your machine. On the Home tab, click the Publish button. Select the desired PowerBI workspace.
After the report publishes, open PowerBI online and go to the workspace where you published the report.
Click the Schedule Refresh icon.
Click edit credentials.
Enter the OnePlan reporting Key Name and Key as the User name and Password. Click the Sign In button.
Toggle ON the Schedule Refresh & set up as desired. Click the Apply button to save changes.
Now that your reports are published, refer to this article for how to show the reports embedding into the OnePlan Dashboard: Set up the Reporting Dashboard
Unable to Connect?
If you receive an error like the one in the screen shot below, you may have stored global permissions in your Power BI Desktop application that has a conflict with the updated OnePlan OData feed. This is a error that indicates you have a saved credential conflict in your Power BI file. There are different credentials for each OnePlan group, so if you’ve ever connected to another, or perhaps saved a different key, that gets saved in your Global Permissions in your Power BI desktop file. Every connection must include the level to which to connect, which has to be the full OData feed URL.
To resolve, you need to clear any global permissions for any OnePlan OData connections you’ve made in the past. Go to the Data Source settings in your report file & clear the global permissions. You can do Clear All Permissions or you can Clear just those that have a OnePlan OData feed URL. Then, close the report & start again.
The important step (to avoid this same error in the future) is that you must select the full URL for the level to which to connect. This will allow you to connect to multiple OnePlan groups in different reports.