How to Create a Single Report Schedule for Power BI in PBRS

Applies to

This article applies to:

Power BI reports and dashboards in Power BI Service

The Single Schedule is the simplest and easiest way to schedule a report for delivery. It involves defining the report you wish to schedule, determine its timing, selecting parameters (if any), and setting the destination (s) of the report.

Use Case: Example: Jamie is a reports developer that must send a daily report to management detailing the number of support tickets currently open. She requires a report to be sent in PDF format at 8:30AM to three individuals.

Before you begin

Before creating a Single Report Schedule, make sure PBRS can access the Power BI Service account and content you want to schedule.

Make sure you have:

A Power BI account configured in PBRS.
Access to the Power BI workspace containing the report or dashboard you want to schedule.
Permission to access the Power BI report or dashboard.
At least one destination configured or the information required to configure the destination where PBRS should deliver the report.

If you have not yet configured a Power BI account, see How to Add a Power BI Account to PBRS.

Create a Single Report Schedule

Create a new schedule and select the Single Report Schedule type to begin configuring the Power BI report or dashboard.

Select Single Report Schedule as the schedule type.
Select Reports and Dashboards or Paginated Reports, depending on the Power BI content you want to schedule.
The Schedule Wizard opens. Use the wizard to select the Power BI content, configure when the schedule runs, define the report output, and select the delivery destination.

Select the Power BI content

Select the Power BI account and the report, dashboard, or paginated report that you want PBRS to run when the schedule executes.

On the General screen, select the Power BI content you want to schedule and enter the basic information used to identify the schedule in PBRS.

In Create In, select the PBRS folder where you want to create the schedule.
In PowerBI Account, select the Power BI account PBRS should use to access the report or dashboard. If the required Power BI account is not available, select Add New to configure an account. For complete setup instructions, see How to Add a Power BI Account to PBRS.
Select Reports or Dashboards, depending on the type of Power BI content you want to schedule.
In Select Report, select the Power BI workspace, and then select the report or dashboard you want to schedule.
In Schedule Name, enter a descriptive name for the schedule.
Optionally, enter a Description to provide additional information about the schedule.
Optionally, enter a Keyword to help identify or organize the schedule.
Select Next.

Configure the schedule

On the Schedule screen, specify when and how often PBRS should execute the schedule. You can define the schedule's start and end dates, recurrence pattern, execution time, and other scheduling options.

In Start Date, select the date when PBRS should begin running the schedule.
To stop the schedule automatically after a specific date, select End Date and specify the final date.
Select the required scheduling option: Daily, Weekly, Week Days, Working Day, Monthly, Annual, Custom Calendar, or Other.
Configure the recurrence settings displayed for the selected option. For example, when Daily is selected, use Repeat every to specify the number of days between executions.
In Schedule time, specify the time when PBRS should execute the schedule.
If required, select Exception calendar and choose the calendar PBRS should use to exclude specified dates from the schedule.
To execute the schedule multiple times during the scheduled period, select the lower Repeat every option, specify the repeat interval, and set the until time.
Select Enable this schedule to allow PBRS to execute the schedule automatically. Clear this option to disable automatic execution.
Select Next.

Note: Disabling a schedule does not delete it. A disabled schedule remains available in PBRS but does not execute automatically. You can disable a new schedule while you review or manually test its configuration before making it live.

To enable automatic execution later, select Enable this schedule in the Schedule Wizard. You can also right-click the schedule from the PBRS main screen and select Enable.

Configure report rendering settings

On the Settings screen, configure how PBRS renders the Power BI report. You can adjust rendering properties, specify which report pages to render, preview the output, and optionally retain report snapshots.

On the Settings tab, review and configure the rendering properties required for the report.
To configure rendering settings using JSON instead, select Use JSON string for rendering settings, and then enter the required settings on the JSON tab
In Pages To Render, specify which Power BI report pages PBRS should include in the output. You can drag and drop Inserts constants into Pages To Render textbox. The available rendering properties include settings for page dimensions, margins, PDF cropping, and other report rendering options.
Select Preview to review how the report will render using the current settings.
To retain snapshots of the rendered report, select Enable snapshots and keep snapshots for, and then specify the number of days PBRS should retain the snapshots.
Select Next.

Pages to Render Examples:

1-5 — renders pages 1 through 5.
1,3,5 — renders pages 1, 3, and 5.
Monthly Report Page,Weekly Summary Report — renders the specified report pages by name.

Note: Pages To Render applies to Power BI reports. It does not apply to dashboards.

Rendering options

Use the rendering settings to control the dimensions, margins, cropping, loading behavior, and other properties PBRS uses when rendering the Power BI report.

Setting	Description
Left margin (% of width)	Specifies the size of the left margin as a percentage of the page width.
Page Height (pixels)	Specifies the height, in pixels, of the rendered output.
Page Width (pixels)	Specifies the width, in pixels, of the rendered output.
Right margin (% of width)	Specifies the size of the right margin as a percentage of the page width.
PDF Cropping	Allows you to crop PDF report output by specifying the amount to crop from the top, bottom, left, and right of the rendered page.
Maximum Loading Time (secs)	Specifies the maximum amount of time PBRS waits for the report to load before the rendering attempt times out.
Minimum Loading Time (secs)	Specifies the minimum amount of time PBRS waits before completing the report rendering process.
Minimum Report Size (Bytes - Optional)	Specifies the minimum expected size of the rendered report.
PDF Compression	Specifies the compression setting PBRS uses when generating PDF output.
Rendering Method	Specifies the method PBRS uses to render the Power BI report.
Transparent Background	Determines whether PBRS renders the report with a transparent background where supported.
View Style	Specifies how PBRS sizes or displays the report during rendering.

Configure rendering settings using JSON

JSON

PBRS also allows you to configure Power BI rendering settings using a JSON string instead of the individual options on the Settings tab. This is useful when you want to define the rendering configuration directly or reuse a specific set of rendering values.

Select Use JSON string for rendering settings.
Select the JSON tab.
Enter or edit the JSON rendering settings.
Review the JSON to make sure the required rendering properties and values are specified correctly.
Select Preview to test the report using the configured rendering settings before continuing.

The JSON configuration can contain the same types of rendering properties available on the standard Settings tab, including rendering method, PDF cropping, loading times, page dimensions, margins, and other rendering options.

Note: When Use JSON string for rendering settings is selected, PBRS uses the JSON configuration to define the report rendering settings. Make sure the JSON contains valid property names, values, and syntax.

Important to Note: Settings and JSON Rendering settings may overwrite each other, so it is best to only set one or the other.

Configure Report Filters and Bookmarks

Use Report Filter to control the Power BI data and report view PBRS uses when the schedule executes. You can configure report filters, apply bookmarks, and specify Row Level Security settings as required.

Add

The Report Filter screen provides the following options:

Option	Description
Filters	Apply filters to control the data included when PBRS renders the report.
Bookmarks	Apply a Power BI bookmark to render a predefined report view or state.
Row Level Security	Apply Row Level Security settings when rendering reports that use Power BI RLS.

Configure a report filter

Select the Filters tab.
Select Add.
Select the type of filter you want to create: Basic, Advanced, or JSON.
Configure the filter settings.
Repeat these steps to add additional filters as required.
To change an existing filter, select it and then select Edit.
To remove a filter, select it and then select Delete.
Select Preview to review the report using the configured filters.

Filter type	Use for
Basic	Create a standard report filter using the available field and value selections.
Advanced	Configure more advanced filter criteria when a Basic filter does not meet the filtering requirement.
JSON	Define the report filter using a JSON filter definition.

Configured filters appear in the filter list. The Field column identifies the Power BI field being filtered, and the Type column identifies the filter type.

Use a Basic filter to filter a Power BI field by one or more specified values.

Select Add, and then select Basic.
On the Definition tab, in Field (Table.Column), enter or select the Power BI field you want to filter.
In Field Data Type, select the data type for the field.
If required, select Ignore filter when insert values are blank to prevent PBRS from applying the filter when no filter values are provided.
Under Show items when the value matches, select the filter operator you want to use.
Enter the value to use for the filter, and then select Add.
Repeat the previous step to add additional values as required.
Review the values in the Values list.
Select OK to save the Basic filter.

Setting	Description
Filter Type	Displays the type of filter being configured. For this procedure, the filter type is Basic.
Field (Table.Column)	Specifies the Power BI table and field to which the filter applies.
Field Data Type	Specifies the data type of the selected field, such as String.
Ignore filter when insert values are blank	Prevents PBRS from applying the filter when the inserted filter values are blank.
Show items when the value matches	Specifies the operator PBRS uses to compare the report data with the filter values.
Values	Displays the values that PBRS uses when applying the filter.

Configure the filter level

After configuring the filter definition, use the Filter Level tab to specify how PBRS applies the filter.

Select the Filter Level tab.

Select Report to apply the filter at the report level.

Select Slicer to apply the filter to a specific Power BI slicer.

If you select Slicer, choose how PBRS should identify the slicer:

Visual Title — identifies the slicer using its visual title.

Filter Field — identifies the slicer using the field associated with the slicer.

Select the required slicer from the list.

Return to the filter definition if additional configuration is required, and then select OK to save the filter.

Filter level	Description
Report	Applies the configured filter to the Power BI report.
Slicer	Applies the filter through a specific slicer in the Power BI report.
Visual Title	Identifies the slicer by its visual title.
Filter Field	Identifies the slicer by the field used by the slicer.

Important: Power BI report filters are intended for presentation and filtering, not for data security. Filters can fail or be bypassed in some scenarios. To restrict access to data, implement Row-Level Security (RLS) at the dataset level in addition to any report filters.

Configure an Advanced Filter

Use an Advanced filter when you need to filter a Power BI field using one or two conditions. When two conditions are configured, you can combine them using And or Or logic.

On the Filters tab, select Add, and then select Advanced.
On the Definition tab, in Field (Table.Column), enter or select the Power BI field you want to filter.
In Field Data Type, select the data type for the selected field.
If required, select Ignore filter when insert values are blank to prevent PBRS from applying the filter when the inserted filter values are blank.
Under Show items when the value, select the operator for the first filter condition.
Enter or select the value for the first condition.
If you need a second condition, select And or Or to specify how PBRS should evaluate the two conditions. With And, you might configure a field to include values that meet both specified conditions. With Or, a value can meet either condition to be included.
Select the operator for the second condition, and then enter or select its value.
Configure the Filter Level as required. Configure the Filter Level to determine whether PBRS applies the filter at the report level or to a specific slicer. See Configure the filter level above for details.
Select OK to save the Advanced filter.

Option	Description
And	Both filter conditions must be true for the data to match the filter.
Or	Either filter condition can be true for the data to match the filter.

Setting	Description
Filter Type	Displays Advanced for an Advanced filter.
Field (Table.Column)	Specifies the Power BI table and field to which the filter applies.
Field Data Type	Specifies the data type of the selected field.
Ignore filter when insert values are blank	Prevents PBRS from applying the filter when inserted filter values are blank.
Show items when the value	Specifies the operator used to evaluate each filter condition.
And / Or	Determines how PBRS combines the first and second filter conditions.

Advanced filter operators:

In Show items when the value, select the operator PBRS should use to compare the Power BI field with the filter value. The available operators determine which report data matches the filter.

Operator	Description
Contains	Includes values that contain the specified value.
LessThan	Includes values that are less than the specified value.
LessThanOrEqual	Includes values that are less than or equal to the specified value.
GreaterThan	Includes values that are greater than the specified value.
GreaterThanOrEqual	Includes values that are greater than or equal to the specified value.
DoesNotContain	Includes values that do not contain the specified value.
StartsWith	Includes values that begin with the specified value.
DoesNotStartWith	Includes values that do not begin with the specified value.
Is	Includes values that match the specified value.
IsNot	Includes values that do not match the specified value.
IsBlank	Includes records where the selected field has a blank value.
IsNotBlank	Includes records where the selected field does not have a blank value.

Note: Operators such as IsBlank and IsNotBlank evaluate whether the field contains a value and therefore do not require a comparison value.

The operators available or appropriate for a filter may depend on the Field Data Type. Select an operator that is appropriate for the type of data being filtered.

Configure a JSONFilter

Use a JSON filter when you need to define Power BI filtering logic using a custom JSON filter definition. This option provides greater flexibility for filtering scenarios that cannot be configured using the Basic or Advanced filter options.

On the Filters tab, select Add, and then select JSON.
On the Definition tab, review the Field (Table.Column) value. PBRS uses {JsonFilter} to identify the JSON filter.
If required, select Ignore filter when insert values are blank to prevent PBRS from applying the filter when inserted values are blank.
In the JSON editor, enter or modify the filter definition that PBRS should use when the schedule executes.
Make sure the filter function returns an array containing the filters PBRS should apply.
Select Build to process the JSON filter definition.
Configure the Filter Level as required. Configure the Filter Level to determine whether PBRS applies the JSON filter at the report level or to a specific slicer. See Configure the filter level above for details.
Select OK to save the JSON filter.

Important: JSON filters control report presentation and filtering. They should not be used as a substitute for Power BI Row-Level Security when data access must be restricted.

Setting	Description
Filter Type	Displays JSON when configuring a JSON filter.
Field (Table.Column)	Uses `{JsonFilter}` to identify the custom JSON filter definition.
Field Data Type	Displays the data type associated with the filter configuration.
Ignore filter when insert values are blank	Prevents PBRS from applying the filter when inserted values are blank.
JSON	Contains the custom filter definition PBRS uses to build the Power BI filters.
Build	Processes the JSON filter definition.
Filter Level	Determines whether the filter is applied at the report level or to a specific slicer.

The JSON editor provides a starter getFilters() function. Add your filter definitions to this function and return the filters as an array.

Note: JSON filters and JSON rendering settings serve different purposes. JSON rendering settings control how PBRS renders the report. A JSON filter controls which Power BI data PBRS includes when rendering the report.

Configure a filter for a slicer

PBRS can apply a filter to a specific Power BI slicer instead of applying the filter at the report level. Use the Slicer filter level when you want the scheduled report to render using a particular slicer selection.

Power BI single slicer

Filter level	Use when
Report	You want PBRS to apply the filter to the report rather than target a specific slicer.
Slicer	You want PBRS to apply the configured value to a specific Power BI slicer.

Note: When using Slicer, make sure the selected Visual Title or Filter Field uniquely identifies the slicer you want PBRS to use.

In order to use the Slicer filter, you must have a Slicer visual in your Power BI Report.

Create or edit a Basic, Advanced, or JSON filter.
Select the Filter Level tab.
Select Slicer.
Under Slicer selection based on, select how PBRS should identify the slicer:
1. Visual Title — identify the slicer by the title of the visual.
2. Filter Field — identify the slicer by the Power BI field used by the slicer.
Select the required slicer from the dropdown list.
Return to the filter definition and complete any remaining filter settings.
Select OK to save the filter.

Option	Description
Visual Title	Identifies the Power BI slicer by the title assigned to the slicer visual.
Filter Field	Identifies the Power BI slicer by the field used by the slicer.

Important: Power BI report filters and slicer selections are intended for report presentation and filtering, not for data security. Filters can fail or be bypassed in some scenarios. To restrict access to data, implement Row-Level Security (RLS) at the dataset level in addition to report filters.

Apply a Power BI Bookmark

Use a Power BI bookmark to render the report using a predefined report view or state. PBRS can apply a bookmark when the schedule executes so that the delivered report reflects the view saved in the bookmark.

If you have a Bookmark in the report you have the ability to select the bookmark using the drop-down menu.

On the Report Filter screen, select the Bookmarks tab.
Select Apply the following bookmark.
Select the Power BI bookmark you want PBRS to apply when the schedule executes.
Confirm that the selected bookmark represents the report view you want PBRS to render.
Select Preview where available to verify the report output before completing the schedule.

Important: Bookmarks and report filters can overwrite each other's settings. To avoid unexpected report output, we recommend using either a bookmark or report filters for a schedule rather than configuring both.

A Power BI bookmark can store report state, including filter and slicer selections. Applying additional PBRS filters to the same report may therefore change the state defined by the bookmark, or the bookmark may override the filter selections.

Configure Row-Level Security

Use Row Level Security to apply Power BI Row-Level Security (RLS) settings when PBRS renders the scheduled report. In PBRS, this option is available for Power BI accounts configured using a Service Principal.

Important: Row-Level Security and report filters serve different purposes. Row-Level Security restricts which data a user is authorized to access. Report filters, slicers, and bookmarks control the data or report view presented when PBRS renders the report and should not be used as a substitute for RLS.

Select the Row Level Security tab.
Select Use the following Row Level Security Settings (Service Principal accounts only).
In the JSON editor, enter the Row-Level Security settings PBRS should use when rendering the report.
Review the JSON configuration to make sure it contains the required RLS values and valid syntax.
Select Preview to verify that the report renders using the expected Row-Level Security settings.

Note: This option applies to Service Principal accounts only. Row-Level Security must already be configured for the Power BI semantic model. The settings entered here tell PBRS which RLS context to use when rendering the scheduled report; they do not create the Row-Level Security rules in Power BI.

Important: Row-Level Security is different from the filters, slicers, and bookmarks configured elsewhere on the Report Filters screen. RLS controls which data the specified identity is authorized to access. Filters, slicers, and bookmarks control how the report is presented and should not be used as a substitute for RLS.

For details about the required JSON structure, see Row-Level Security JSON Configuration for Power BI.

Configure destinations

On the Destinations screen, specify where PBRS should deliver the report when the schedule executes. You can add one or more destinations to the schedule and configure the report output for each destination.

Select Add.
Select the type of destination you want to add.
Configure the selected destination, including its delivery, report Format, and Naming options.
Save the destination.
Repeat these steps to add additional destinations as required.

You can add multiple destinations to the same schedule. For example, a schedule can deliver report output by email and also save report output to another supported destination.

Configured destinations appear in the destination list. Name identifies the destination, and Format identifies the report output format configured for that destination.

Control	Description
Add	Adds a new destination to the schedule.
Edit	Opens the selected destination so you can change its configuration.
Delete	Removes the selected destination from the schedule.
Import	Imports destination configuration into the schedule.
Up arrow	Moves the selected destination higher in the destination list.
Down arrow	Moves the selected destination lower in the destination list.

For detailed instructions for a specific destination, see the appropriate destination setup article.

Format: Select the output format in which PBRS should export the report. The selected format determines the type of report file attached to the email.

For details about the available export formats and their settings, see Configure Report Output Formats in PBRS.

Naming: Configure how PBRS should name the exported report file. Use the available naming options and PBRS constants to create static or dynamic file names as required.

For details about report file naming options, see Configure Report File Naming in PBRS.

Finally, Review the destination list and confirm that all required delivery locations have been configured then select Next.

Configure exception handling

On the Exception Handling screen, configure how PBRS should respond when a schedule takes too long to complete or encounters an error. You can configure execution timeouts, automatic retries, and custom tasks that run when specific exceptions occur.

Treat as “error” if not completed in X minutes: If a report takes longer than the specified amount of time to run, this option will treat the schedule as an error and follow the appropriate action. The “Auto-calculate” option instructs PBRS to automatically determine how long a schedule should take to run the report. If it takes longer than the calculated amount of time, then it is an error.
In On error, retry executing schedule every, specify how long PBRS should wait between retry attempts and the maximum number of times PBRS should retry the schedule.
On error, retry executing schedule every: If set to 0, PBRS will deem the schedule as "Failed" the first time it encounters an error. The schedule will not run again until its next scheduled time. Change the value to tell PBRS how many times you want it to retry running the report before declaring it as "Failed."

If manually determining the error timing, please double-check the run time of the report in order to get the correct time estimate.

To run one or more tasks when a specific exception occurs, select Run custom tasks when the following exception occurs.

Select the exception condition that should trigger the custom tasks:

Report is blank — If a report is blank because it genuinely returned no data, recipients can misconstrue this as an error with the scheduler. This option allows you to identify genuine empty reports and instruct PBRS on what to do with them.
Report export fails — If the report is blank, do not send the report. The report will not be delivered to the destination. No custom tasks will be run.

On the Actions tab, select the task you want PBRS to perform when the exception occurs. Available actions include running programs, printing documents, executing another schedule, sending notifications, refreshing Power BI datasets, performing file operations, and other PBRS tasks.
Configure the selected task and add it to the action list. Configured exception Tasks appear in the action list. Use Edit to change a selected action or Delete to remove it. Use the ordering controls to change the sequence in which PBRS performs multiple actions.
Repeat these steps to add additional actions as required.

For detailed instructions for a specific task, see the appropriate task setup article.

Blank Report Check Method

When Report is blank is selected as an exception condition, use the Blank Report Check Method to define how PBRS determines whether the generated report should be treated as blank. PBRS can perform this check using a SQL query or the size of the generated file.

Method	Description
SQL Query	Uses the result of a SQL query to determine whether the report should be treated as blank.
File size check	Uses the size of the generated report file to determine whether the report should be treated as blank.

Use a SQL Query

Select SQL Query.
Enter the SQL query PBRS should use to determine whether the report is blank.
Select Build if you need to build or configure the query using the PBRS query builder.

Get values from a database window will appear. For details about these settings, see How to Get values from database

Configure a File size check

Use a File size check

Select File size check.
Configure the file-size criteria PBRS should use to determine whether the generated report is blank.
Review the configured threshold before continuing.

When PBRS determines that a report is blank using the selected method, the Report is blank exception is triggered and PBRS runs any actions you configured for that exception.

Tip: You can send a notification if a report is considered blank instead of sending the report. Simply select “check if a report is blank” then select “Ignore the report.” In the actions tab, select “Send Email” from the list. Compose your email and save.

Finally, review the timeout, retry, exception, and action settings.
Select Next.

Refresh datasets before running the report

On the Refresh Datasets screen, select any Power BI datasets that PBRS should refresh before executing the report. You can refresh multiple datasets, configure refresh notifications, and specify how long PBRS should wait after the refresh before running the report.

In PowerBI Account, select the Power BI account that contains the dataset you want to refresh.
In Workspace, select the workspace containing the dataset.
In Dataset, select the dataset you want PBRS to refresh.
Under Notification Options, select how PBRS should handle refresh notifications.
Select Add > to add the dataset to the refresh list.
Repeat these steps to add additional datasets as required.

Notification option	Description
Notify on Completion	Sends a notification when the dataset refresh completes.
Notify on Failure	Sends a notification if the dataset refresh fails.
Do not Notify	Does not send a notification about the dataset refresh.

Datasets added to the schedule appear in the refresh list. The list shows the dataset, Power BI account, workspace, and selected notification option.

Finally, In After refreshing the datasets above, wait, specify the number of seconds PBRS should wait after refreshing the datasets before running the report. Use this setting when additional time is required after the dataset refresh before PBRS renders the report. Then Click Next

Configure custom tasks

On the Custom Tasks screen, configure optional actions that PBRS should perform as part of the schedule workflow. Custom tasks can run before the schedule or after successful report production or delivery and can automate additional processes such as running programs, executing other schedules, refreshing datasets, managing files, and sending notifications.

From the list of available tasks, select the task you want PBRS to perform.
Configure the settings for the selected task.
Add the task to the schedule.
Repeat these steps to add additional tasks as required.
To change a configured task, select it and then select Edit.
To remove a task, select it and then select Delete.

For detailed instructions for a specific task, see the appropriate task setup article.

Configure when a custom task runs

Each custom task includes an Options tab that controls when PBRS runs the task in relation to the schedule. Use these settings to determine whether the task runs before or after the schedule and, where applicable, whether it runs after successful report production or successful report delivery.

Configured tasks appear in the task list. The list identifies the task and when PBRS should run it in relation to other tasks in the schedule.

Timing option	Description
BEFORE THE SCHEDULE	Runs the custom task before PBRS executes the schedule.
AFTER THE SCHEDULE — After Successful Report Production	Runs after PBRS successfully generates the report output.
AFTER THE SCHEDULE — After Successful Report Delivery	Runs after PBRS successfully delivers the report output.

If you configure multiple tasks, use the ordering controls to arrange them in the required execution order. The execution order works together with the timing configured on each task's Options tab. Review both the task order and timing settings when configuring multiple custom tasks.

Note: When multiple custom tasks are configured, review both the task order and the timing configured on each task's Options tab. This determines the sequence in which PBRS performs the tasks as part of the schedule workflow.

Custom tasks are optional. If the schedule does not require additional actions, leave the task list empty.

Import: If you already have a default Custom Task List created you may import it using this option.
Export: If you wish to create a Default Task list from the tasks created here, simply click on the Export button, give the task list a name, when prompted and it is ready to be used again and again in other schedules.

Finally, review the configured custom tasks and select Finish to complete the Single Report Schedule setup.

Use the Single Report Schedule context menu

After creating a Single Report Schedule, right-click the schedule from the PBRS main screen to access additional management and execution options.

Option	Description
Properties	Opens the schedule properties so you can review or modify its configuration.
Copy	Copies the selected schedule.
Paste	Pastes a previously copied schedule where applicable.
Rename	Changes the name of the selected schedule.
Enabled	Enables or disables automatic execution of the schedule.
Move	Moves the schedule to another location in PBRS.
Preview	Generates a preview of the report using the schedule's current configuration.
Execute	Runs the schedule immediately.
Delete	Deletes the selected schedule.
Execute On...	Provides options for executing the schedule on a selected execution resource or environment.
Tools	Opens additional tools available for the selected schedule.

Note: Preview allows you to review the report output using the schedule configuration. Execute runs the schedule immediately, including the configured workflow and delivery options.

Select Tools to access additional actions for the selected schedule.

Tool	Description
Generate Script	Generates a script based on the selected schedule.
Test	Provides tools for testing the selected schedule.
Convert To Package	Converts the Single Report Schedule to a Package schedule.
Ad-Hoc Email to Recipients	Sends an ad-hoc email to the schedule's configured recipients. You can use this to alert recipients to a planned system outage, or any other useful information.
Create Shortcut	Creates a shortcut for the selected schedule. Use this option to create a shortcut you can save in any location on your PC. Execute the shortcut to execute the schedule in PBRS.
Ad-Hoc View	Opens an ad-hoc view using the selected schedule.

Single Report Schedule Properties

To review or change an existing Single Report Schedule, locate the schedule on the PBRS main screen, right-click the schedule, and select Properties. The Single Report Schedule Properties window opens, where you can review and modify the schedule configuration.

Hints and Tips:

You can view the Schedule Unique ID in the General Wizard.

Sharing

Inside the Sharing Tab you can share this schedule with multiple users. Sharing schedules allows other users to see these schedules.

Snapshots: A snapshot is a copy of each report a schedule or a package generates. Keeping snapshots enables you to resend past reports without generating them afresh - especially if the data has changed in the meantime.

Enable the Snapshots option and select the number of days to keep the snapshots.

History: Review the schedule's history. Successes, failures, and other data is located here.

Verify the Single Report Schedule

After configuring the Single Report Schedule, verify that the report renders correctly and is delivered to the expected destinations. You can preview the report before executing the complete schedule.

Preview the report

From the PBRS main screen, locate the schedule.
Right-click the schedule and select Preview.
Review the report output and confirm that the report renders as expected.
If you configured report filters, slicers, bookmarks, or Row-Level Security, confirm that the expected data and report view are displayed.

Execute the schedule

Right-click the schedule and select Execute.
Allow PBRS to complete the schedule workflow.
Confirm that the report is generated successfully.
Verify that the report is delivered to each configured destination.
If the schedule refreshes Power BI datasets, confirm that the refresh occurs before the report is generated.
If Custom Tasks are configured, confirm that the tasks execute at the expected point in the workflow.

Unlike Preview, Execute runs the schedule workflow using its configured settings. This allows you to verify report production, destinations, dataset refreshes, Custom Tasks, and other schedule behavior before relying on automatic execution.

Tip: When creating a new schedule, you can clear Enable this schedule while testing. The schedule remains available in PBRS but does not execute automatically. After you have successfully tested the schedule, enable it from the schedule properties or right-click the schedule on the PBRS main screen and select Enabled.

Before enabling automatic execution, confirm that:

The correct Power BI report, dashboard, or paginated report is selected.
The report renders correctly.
Filters, slicers, bookmarks, and RLS behave as expected, if configured.
The schedule timing is correct.
Dataset refreshes complete as expected, if configured.
Report output is delivered to every required destination.
Custom Tasks execute at the expected time, if configured.
No unexpected errors appear in the Error Log.

Troubleshooting

If the Single Report Schedule does not execute or the report is not produced or delivered as expected, check the following common issues.

The schedule does not execute automatically

Confirm that Enable this schedule is selected. If the schedule is disabled, right-click it from the PBRS main screen and select Enabled.

Also verify the Start Date, Schedule time, recurrence settings, and Next to run on date and time.

The Power BI report does not render

Confirm that the correct PowerBI Account, workspace, and report or dashboard are selected. Select Preview to test the report rendering separately from the complete schedule workflow.

If the report does not render, check the PBRS Error Log for additional information.

The schedule times out

Review Treat as "error" if not completed in under Exception Handling. If Auto-calculate is enabled, PBRS determines the timeout automatically. If you specify the timeout manually, make sure the value allows enough time for the report to complete.

The report contains unexpected data

Review the settings under Report Filters. Confirm that Basic, Advanced, or JSON filters are configured correctly and that the appropriate Filter Level is selected.

If you are using a slicer, confirm that PBRS is targeting the correct Visual Title or Filter Field.

A bookmark does not produce the expected report view

Review the selected bookmark and any report filters configured for the schedule. Bookmarks and filters can overwrite each other's settings, so we recommend using either a bookmark or report filters when possible.

Row-Level Security does not produce the expected data

Confirm that RLS is configured correctly in Power BI and that the schedule uses the appropriate Service Principal account. Review the JSON configured on the Row Level Security tab.

Remember that report filters and slicers are not substitutes for Row-Level Security.

A dataset does not refresh before the report runs

Review the Refresh Datasets settings and confirm that the correct PowerBI Account, workspace, and dataset are selected.

If necessary, increase the configured wait time between the dataset refresh and report execution. Check the PBRS Error Log for dataset refresh failures.

The report is generated but is not delivered

Review the Destinations screen and confirm that each required destination is configured correctly.

Use the appropriate destination article to troubleshoot destination-specific settings, such as Email or SharePoint. Check the PBRS Error Log for delivery errors.

A Custom Task does not run

Review the task's Options tab and confirm whether the task is configured to run BEFORE or AFTER the schedule.

For an AFTER task, confirm whether it should run After Successful Report Production or After Successful Report Delivery. A task configured to run after successful delivery will not run if report delivery fails.

Check the Error Log

If the cause of the problem is not immediately apparent, check the PBRS Error Log. Review errors associated with the schedule execution, correct the affected configuration, and then select Execute to test the schedule again.