Not able to creat alert over a table chart without removing columns

Hi dcadena,

Alerts from Power BI report visuals are officially supported using Fabric Activator. Activator reuses the underlying table visual query and combines all dimension columns into a single object key. When columns are removed, the object complexity is reduced, which allows the alert to be created, this explains the observed behaviour. As I can see this scenario is not documented under Activator limitations.

If this behavior is blocking your scenario, we recommend opening support ticket here: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

including a minimal repro (alert fails on a table with multiple columns but succeeds after removing columns) so the product team can investigate further.

Create Power BI alerts and refine them in Fabric Activator - Microsoft Fabric | Microsoft Learn

Activator limitations - Microsoft Fabric | Microsoft Learn

Activator ingestion from Power BI - Microsoft Fabric | Microsoft Learn

Thanks,
Prashanth

Hi dcadena,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

hi dcadena not sure if you have managed to resolve this issue.

As above, this seems to be a known limitation with data alerts on Table visuals in Power BI Fabric, and you're experiencing it now.

When a Table visual has too many columns (includes non-numeric columns, uses measures mixed with calculated columns), the alert creation UI lets you select a column, but somewhat fails in the background when saving the alert.
My recommendation is to replicate the table into a Card visual (or KPI) using the same measure and then create the alert on the Card instead. Because Card visual is more stable than Table visual. If you want to stick to using Table visuals, then the alternative is to simplify the table (less columns / complexity).

Appreciate if you can 'Kudos' and/or 'Accept as Solution' if this answered your query.

Hi,

Based on your description, this doesn't sound like an issue with the alert definition itself, especially since the same visual works after removing a few columns.

A few things you could check:

• Try recreating the table visual from scratch rather than editing the existing one, as the visual metadata may have become corrupted.

• Verify whether the issue occurs only with this specific table or with other table visuals in the same report.

• Check if adding a particular column consistently causes the alert creation to fail. If so, that may help identify whether a specific field or measure is triggering the issue.

• Publish a copy of the report to a test workspace and see if the behavior is reproducible there.

Since this started only a few days ago and previously worked without changes, it could also be related to a recent service update affecting alert creation on table visuals.

A few questions that may help narrow it down:

• Are the columns you're adding regular fields or DAX measures?

• Is the report using Import, DirectQuery, or Direct Lake?

• Does the problem occur in both the Power BI Service and Microsoft Fabric?

If the issue persists, I'd recommend opening a Microsoft Support ticket with:

• The report and workspace IDs

• Screenshots of the alert creation process

• A copy of the PBIX (if possible)

• The list of columns that reproduce the issue

If Microsoft identifies the root cause or provides a workaround, please consider sharing it here. It would be very helpful for others encountering the same behavior.

If you found this reply helpful, please consider giving it a Kudos. If it helps resolve your issue, marking it as the Accepted Solution will help other community members facing the same problem.