Articles in this section

5 - Setting Up Power BI Reports for QorusDocs Reporting and Analytics

This article applies to:Available in these QorusDocs Editions:

Target Audience: Business team champions, Power BI report builders, and IT administrators.

Objective: This guide explains the reporting options available during QorusDocs onboarding, what each option is used for, who should complete the setup, and which parts are supported by QorusDocs. It covers the standard QorusDocs Power BI report, optional pursuit and bid tracking reporting using Pursuits and Pursuit Smart Fields, and advanced custom reporting scenarios that may involve CRM, SharePoint, or other customer-owned data sources.


Why reporting matters

Reporting helps your team understand how QorusDocs is being used and where proposal, pursuit, and content activity is happening. The standard QorusDocs Power BI report can help teams review usage, searches, content activity, document activity, user activity, pursuits, assignments, and other standard QorusDocs activity data.

Some teams also want management or executive-level reporting for pursuit and bid tracking, such as active pursuits, win/loss status, proposal volume by industry, service line, product line, region, customer type, or other business categories. This type of reporting depends on the pursuit data and Smart Fields your team chooses to capture in QorusDocs.

Power BI is the recommended reporting tool for this work. Excel can be useful for reviewing or testing data, but it is not recommended as the long-term reporting solution for dashboards, scheduled refreshes, shared management reporting, or executive reporting.

Reporting options at a glance

There are three common reporting paths:

  1. Standard QorusDocs Power BI report

Use this first. This report uses QorusDocs OData and the standard QorusDocs Power BI report template. It is used for standard QorusDocs activity, usage, content, pursuit, assignment, and user reporting. This is the recommended starting point for reporting.

  1. Pursuit and bid tracking dashboard

Use this when your proposal, pursuit, or business development team wants reporting on win/loss, active pursuits, pursuit status, industry, service line, product line, region, customer type, or other pursuit-specific Smart Fields. This is customer-owned Power BI/reporting work because the dashboard depends on the Smart Fields and reporting requirements your team chooses to capture.

  1. (Optional) Advanced CRM, SharePoint, and QorusDocs reporting

Use this only when your organization wants to combine QorusDocs data with external systems, such as CRM opportunity data, SharePoint content data, or other business systems. This is an advanced custom reporting scenario and should be handled by your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner.


In this article

This article is organized into the following sections:

Important notes

  • The standard QorusDocs Power BI report should be set up first. This gives your team a working report connected to QorusDocs OData before any custom dashboard work begins.
  • The standard report requires OData credentials from QorusDocs Hub Management, the QorusDocs Power BI report template, publishing the report to Power BI Service, configuring scheduled refresh, and embedding the report in QorusDocs Hub if the report should be accessed from QorusDocs.
  • Pursuit and bid tracking dashboards are customer-owned. QorusDocs provides the QorusDocs data through OData, including Pursuits and Pursuit Smart Fields, but the dashboard design, business logic, visuals, measures, and reporting requirements should be handled by your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner.
  • Advanced reporting that combines QorusDocs with CRM, SharePoint, or other systems is optional and customer-owned. These reports depend on your organization’s external systems, data model, permissions, and reporting requirements.
  • Microsoft Power BI licensing is managed by your organization. In general, report creators and publishers need an appropriate paid Power BI license. Viewers usually need Power BI Pro or Premium Per User unless the report and semantic model are hosted in Premium capacity or Fabric F64 or greater capacity, where free users may be able to view shared content. Always confirm current licensing requirements using Microsoft’s published documentation.

Power BI Requirements

Your organization should confirm licensing and access with your Microsoft administrator or Microsoft partner.

At a minimum, the person creating, publishing, editing, or republishing reports typically needs an appropriate paid Power BI license, such as Power BI Pro or Premium Per User.

For viewers, licensing depends on how your organization publishes and shares Power BI content. If reports are shared through standard Power BI workspaces, viewers typically need Power BI Pro or Premium Per User. If the report and semantic model are hosted in Premium capacity or Fabric F64 or greater capacity, users with free licenses may be able to view and interact with the content.

Because Microsoft licensing can change, always confirm the current requirements using Microsoft’s Power BI licensing documentation.

Suggested Skill Level

Intermediate to Advanced Power BI proficiency. The resource should have experience in:

  • Data modeling
  • Advanced Power Query transformations
  • DAX (Data Analysis Expressions)
  • Integration with multiple data sources (e.g., SharePoint, CRM systems like Salesforce, and QorusDocs)

Prerequisites

  1. Intermediate proficiency in Power BI, including knowledge of:
    • Connecting to OData feeds and other data sources.
    • Managing relationships between tables.
    • Building calculated measures and custom columns using DAX.
    • Developing interactive reports with filters and visuals.
  2. Familiarity with QorusDocs, CRM systems, and SharePoint is a plus, but not mandatory.
  3. Access to Power BI Pro and necessary credentials for QorusDocs, CRM, and SharePoint data connections.

Section 1: Set up the standard QorusDocs Power BI report

Overview

The standard QorusDocs Power BI report is the recommended starting point for reporting. It uses QorusDocs OData and the standard QorusDocs Power BI report template to report on standard QorusDocs activity and usage data.

This report can help your team review user activity, content usage, searches, document activity, pursuit activity, assignments, and other standard QorusDocs data available through OData. It does not require CRM or SharePoint connections.

The standard report should be connected to QorusDocs OData, published to Power BI Service, configured with scheduled refresh, and embedded in QorusDocs Hub if users should access it from QorusDocs.

QorusDocs Support

QorusDocs can provide guidance for connecting the standard QorusDocs Power BI report template to QorusDocs OData and confirming the standard report setup path.

Your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner should own publishing the report to Power BI Service, configuring Power BI workspace access, managing Microsoft licensing, setting scheduled refresh, and embedding the report in QorusDocs Hub.

QorusDocs Support can assist with QorusDocs-specific items, such as OData access and the standard QorusDocs report template. Microsoft Power BI administration, licensing, workspace permissions, custom report design, and customer-specific dashboards are customer-owned.

Guidance Resources

Help Center Articles: Help Center articles are available to guide report builders through connecting to the OData feed and configuring Power BI to visualize QorusDocs activity data.
Using OData to analyze your QorusDocs activity – Help Center
Power BI: How to Filter Pursuits by Smart Fields – Help Center

Steps

  1. Set up QorusDocs OData credentials in QorusDocs Hub Management.
    • The user completing this step must have access to the required QorusDocs Hub Management area.
    • The OData credentials are used by Power BI to connect to QorusDocs reporting data.
  2. Download the latest standard QorusDocs Power BI report template from the QorusDocs reporting Help Center article.
    • Use the standard template as the starting point rather than building the standard report from scratch.
  3. Open the template in Power BI Desktop.
    • When prompted, enter the QorusDocs OData URL and OData credentials.
  4. Confirm the report loads QorusDocs data.
    • Review the report pages and confirm that data appears.
  5. Publish the report to Power BI Service.
    • This is completed by your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner.
  6. Configure scheduled refresh in Power BI Service.
    • The refresh uses the QorusDocs OData credentials.
    • Choose the refresh cadence that matches your organization’s reporting needs.
  7. Embed the report in QorusDocs Hub, if users should access the report from QorusDocs.
    • Use the Power BI embed URL and add it as a page in QorusDocs Hub.
  8. Confirm access with the users who need to view the report.
    • Confirm the report loads successfully for intended viewers.
    • If a user cannot view the report, check Power BI licensing, workspace/report permissions, and whether the report and semantic model are hosted in the correct workspace or capacity.

Detailed instructions for embedding the report in the QorusDocs Hub

  1. Embed the Power BI Report in QorusDocs Hub
    If you do not have access to the QorusHub, please ask the core team champion to add you as Admin.

    Step 1: Get the Power BI embed URL

    1. Go to https://app.powerbi.com and open the published report.
    2. Click File, then Embed Report, then select Website or portal.
    3. In the popup window, copy only the URL inside the quotation marks, not the iframe.

      Example URL: 

      https://app.powerbi.com/reportEmbed?reportId=...

    Step 2: Open QorusDocs Hub Central

    1. Go to https://www.qorushub.com and sign in.
    2. In the left-hand menu, click Hub Central.
    3. Navigate to Settings, then select Hub Management.
    4. Click on the Tabs & Pages tab.

    Step 3: Add a New Page in Hub Central

    1. In the Pages section, click Add Page.
    2. Complete the following fields:
    • Title: Enter a name for the page (e.g., "Power BI Dashboard").
    • Type: Select Website or Portal
    • URL: Paste the Power BI embed URL copied in Step 1.
    • Description (optional): Provide context for the report.
    1. Click Save to create the page.

    Step 4: Verify the Page Works

    1. Navigate to the newly created page in the Hub.
    2. Confirm the report loads without errors.
    3. If prompted, sign in to Power BI to view the content.

    Step 5: Confirm Access with Core Users

    1. Share the Hub page link with the core users who need to view the report.
    2. Ask each user to:
      • Open the page in QorusDocs.
      • Sign in to Power BI if prompted.
      • Confirm that the report displays correctly.
    3. If a user cannot see the report:
      • Verify they have the correct Power BI license (Pro or Premium).
      • Ensure they have access to the report or dataset in Power BI.
      • Check for any row-level security restrictions in the report.

 


Back to the top

Section 2: Create a pursuit and bid tracking dashboard

Overview

Some proposal, pursuit, business development, or leadership teams want reporting that goes beyond the standard QorusDocs activity report. Common examples include active pursuits, pursuit status, win/loss tracking, proposal volume by industry, service line, product line, geography, customer type, or other categories captured during the pursuit process.

This type of dashboard depends on how your organization configures Pursuits and Pursuit Smart Fields in QorusDocs. For example, an RFP pursuit type may capture one set of Smart Fields, while a proposal pursuit type may capture different Smart Fields.

The key QorusDocs data areas for this dashboard are:

  • Pursuits
  • Pursuit Smart Fields

This dashboard is optional and customer-owned because the reporting requirements, Smart Fields, calculations, visuals, and dashboard layout are specific to your organization.

Recommended approach

After the standard QorusDocs Power BI report has been connected, published, refreshed, and embedded, duplicate the report and use the copy as the starting point for the pursuit and bid tracking dashboard.

Duplicating the report can preserve useful setup work, such as the QorusDocs OData connection and existing model logic. From there, hide or remove pages that belong to the standard report and build the new dashboard pages around Pursuits and Pursuit Smart Fields.

Suggested setup steps

  1. Confirm the standard QorusDocs Power BI report is working first.
  2. Duplicate the working Power BI report.
  3. In the copied report, hide or remove the standard report pages that are not needed for the pursuit dashboard.
  4. Use the Pursuits and Pursuit Smart Fields tables as the starting point for the dashboard.
    Power BI: How to Filter Pursuits by Smart Fields – Help Center
  5. Identify the Smart Fields your team wants to report on, such as win/loss, industry, service line, product line, region, customer type, pursuit status, assigned team, or other fields captured in QorusDocs.
  6. Build the required tables, slicers, visuals, and measures in Power BI.
  7. Publish the dashboard to Power BI Service.
  8. Configure scheduled refresh using the same QorusDocs OData credentials, unless your organization requires a different credential strategy.
  9. Embed the dashboard in QorusDocs Hub if users should access it from QorusDocs.
  10. Confirm access with the users who need to view the dashboard.

Support boundary

QorusDocs provides the QorusDocs data through OData and can point your team to relevant Help Center guidance. The dashboard design, business logic, Power BI model changes, measures, visuals, workspace setup, publishing, refresh schedule, and user access should be handled by your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner.

 


Back to the top

Section 3: Advanced CRM, SharePoint, and QorusDocs reporting

Overview

Advanced CRM, SharePoint, and QorusDocs reporting is optional and customer-owned. This reporting path is only needed when your organization wants to combine QorusDocs data with other systems, such as CRM opportunity data, SharePoint content data, financial data, or other business systems.

This is an advanced reporting scenario because it depends on your external systems, data quality, permissions, relationships between systems, reporting logic, and Power BI data model. It should be handled by your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner.

QorusDocs Support

QorusDocs can provide access to QorusDocs OData and point your team to relevant QorusDocs reporting resources.

Customer-specific report design, CRM connections, SharePoint connections, external data relationships, Power BI measures, DAX, custom visuals, dashboard layout, publishing strategy, scheduled refresh, permissions, and long-term maintenance are customer-owned and should be handled by your internal Power BI/reporting resource, BI team, IT team, or Microsoft partner.

Guidance Resources

Steps

  1. Connect to Multiple Data Sources:
    • Connect to SharePoint libraries to retrieve content data, CRM (e.g., Salesforce) for opportunity data, and QorusDocs for pursuits.
    • Ensure all necessary tables from these systems are loaded.
  2. Create Relationships:
    • Build relationships between Opportunities in CRM, Pursuits in QorusDocs, and content stored in SharePoint.
  3. Develop Calculated Tables and Columns:
    • Create calculated tables for correlating content usage with win rates:
      • Content Used in Opportunities = Calculate content used in Closed Won and Closed Lost opportunities.
      • Content Link (for SharePoint): Create a custom column that links to the document stored in SharePoint.
  4. Create Key Metrics and Visuals:
    • Closed Won Rate: Use DAX to calculate win rates for opportunities and pursuits.
    • Content Usage by Industry, Practice Group, or Solution: Use filters to display content performance in different contexts.
    • Win Rate by Content Type: Show how certain types of content (e.g., proposals, presentations) affect win rates.
  5. Publish and Automate Report Refresh:
    • Publish the report to Power BI Service (requires Power BI Pro) and set up automated refresh schedules for CRM, QorusDocs, and SharePoint data.
    • Sharing the report: Ensure Power BI Premium Capacity is in place if sharing with team members without Power BI Pro licenses. Viewers will need a Power BI Free license to view the report in the QorusDocs Hub, Power BI Service, or SharePoint Online.

 

Back to the top

Final Steps

  1. Review Credentials and Permissions:
    • Ensure proper permissions for connecting to SharePoint, CRM, and QorusDocs.
    • Document credentials for future reference and security purposes.
  2. Maintain and Update Reports:
    • Regularly review the reports and data models to ensure they meet business requirements. Update as needed based on new content or data.

By following this guide, your Power BI/reporting resource can set up the standard QorusDocs Power BI report, create an optional pursuit and bid tracking dashboard, and understand when advanced CRM, SharePoint, and QorusDocs reporting may be needed. Sharing and viewer access should be configured according to your organization’s Microsoft Power BI licensing, workspace, and capacity model.

 

Back to the top

Suggested Courses for Power BI Resource

  1. Microsoft Power BI Guided Learning
    • Skill Level: Beginner to Intermediate
    • This free course provides a comprehensive introduction to Power BI, covering the fundamentals of connecting to data, creating reports, and building visuals.
  2. Power BI Essential Training on LinkedIn Learning
    • Skill Level: Intermediate
    • This course delves deeper into Power BI functionalities, including data modeling, DAX, and advanced reporting techniques.
  3. Power BI for Data Analysts by Microsoft Learn
    • Skill Level: Intermediate to Advanced
    • This path focuses on advanced techniques, such as connecting to multiple data sources, optimizing data models, and using advanced DAX for calculations.

 

Back to the top

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.