topic Re: Creating Trigger within Power BI Report in Activator

Creating Trigger within Power BI Report

kerski — Tue, 27 Jun 2023 20:55:08 GMT

I verified I am on premium in US East 2, my dataset and report are on a Fabric workspace, and I'm using a horizontal bar chart with an x-and-y axis that are not date based. I don't see the option to create a Trigger. Am I missing a step?

Re: Creating Trigger within Power BI Report

WillT — Wed, 28 Jun 2023 15:34:55 GMT

Hi - thanks for getting in touch. You'll need to make sure your admin has enabled Data Activator for you as it's a private preview feature. In the tenant admin settings page there's an option to enable it. More details in the docs here: dataActivator/ConsolidatedDocs.md at main · microsoft/dataActivator · GitHub

Re: Creating Trigger within Power BI Report

kerski — Wed, 28 Jun 2023 19:42:18 GMT

I did update the settings prior to posting this message. I could create a reflex artifact manually as well.

Re: Creating Trigger within Power BI Report

kerski — Thu, 29 Jun 2023 16:23:55 GMT

And to verify these are the settings I had turned on:

Re: Creating Trigger within Power BI Report

DKfromtheBay — Thu, 29 Jun 2023 17:23:10 GMT

My guess is you need to turn on Create Fabric Items as the data activator is a component of fabric, so even though you enabled the Trident preview, you still need to uncheck the default box above and turn on the Fabric item creation

Re: Creating Trigger within Power BI Report

Anonymous — Thu, 29 Jun 2023 18:23:26 GMT

Data Activator is part of Fabric. Enrollment in Microsoft Fabric's public preview is a requirement to participate in Data Activator's private preview.

Re: Creating Trigger within Power BI Report

kerski — Thu, 29 Jun 2023 19:19:45 GMT

Understood, but I shared a screenshot confirming I followed those steps and still can't setup a trigger in a Power BI Report in a Fabric workspace.

I can create a Reflex artifact for Azure Event Hub in that workspace, but not for a report in that workspace.

Re: Creating Trigger within Power BI Report

DKfromtheBay — Thu, 29 Jun 2023 19:20:31 GMT

Your screenshot shows that Fabric is deactivated for entire organization

Re: Creating Trigger within Power BI Report

kerski — Thu, 29 Jun 2023 19:23:34 GMT

Okay, so I turned it on. How was I able to create Fabric workspaces and Fabric items before then? I had several workspaces before May and June with Dataflow 2.0, Notebooks, etc. without this setting turned on.

Re: Creating Trigger within Power BI Report

DKfromtheBay — Thu, 29 Jun 2023 19:25:13 GMT

That is a bit of mystery and I can't speak to that 🙂 Was just pointing out a low hanging fruit that may have been impacting your ability to create the trigger.

Are you now able to see the option in Power BI reports?

Re: Creating Trigger within Power BI Report

kerski — Thu, 29 Jun 2023 19:52:24 GMT

I waited 15 minutes, created a brand new Fabric workspace, uploaded a dataset, created a report in the browser, saved it to the same Fabric workspace, made sure the x-and-y were not datetime, and this is the more options menu:

Re: Creating Trigger within Power BI Report

Anonymous — Thu, 29 Jun 2023 21:40:53 GMT

kerski , I discussed with the team.

1. do you see a Data Activator listed in the workload switcher in the lower-left?

2. Can you try refreshing the browser? It could be that there is some longer than normal delay for the tenant level setting to propagate.

Re: Creating Trigger within Power BI Report

kerski — Thu, 29 Jun 2023 22:35:48 GMT

1) I refreshed the browser and I see the Data Activator listed in the workload.

2) I thought maybe it was a dataset issue, so I created a Dataflow 2.0 loaded some CSV into a lakehouse, the dataset was automatically created for me. Then I created a report from that dataset (all in a Fabric workspace) and these are the more options I get:

Re: Creating Trigger within Power BI Report

kerski — Fri, 30 Jun 2023 16:46:47 GMT

I came back this morning, and now the option appears. I think we just had to let the provisioning work its way through. Problem solved! Thanks.