How to generate error-message if nothing found in report by using query string parameters in URL

[frankvb]

Hi,

The set-up

I have two separate reports. It is possible to jump to the corresponding data between the reports using buttons that are present in both reports.

These buttons have url's using a filtered value in the report, as a query string parameter: https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-url-filters

The problem

Sometimes however, report A does not have the corresponding value in report B. So after clicking the button you land in an empty report.

Now my end-users would like to have an error-message when this happens, but how can I do this, without adding any of the data from the dataset of report A to the dataset of report B?

I cannot add the missing data from report B to the data of report A (not even just the keys, or guids or anything like that).

[frankvb]

This would solve it indeed, but it requires something that makes the whole thing obsolete: merging data from A to B (or the other way around). In order to make the column that can be used to filter (whether or not the data is present in the other dataset), you need to merge both datasets. How else can I tell my query string parameter that there is no data with this filter in the other report?

[rajendraongole1 · Accepted solution]

Hi @frankvb - you can implement a solution that provides user feedback without merging datasets.

Design an error page within Report B that is shown when there is no data available.

Dynamic Visibility: In Report B, use a measure that checks if the relevant data exists based on the filter applied from Report A. If no data exists, display the error message. This could be done using a card visual or a text box that shows a message like "No data available for the selected criteria."

When creating the URL in Report A, you could add an additional query string parameter that indicates a "check" for data existence.

Check Parameter: In Report B, use this parameter to determine whether to display the error message. For instance, if the parameter is "check=true" and no corresponding data is found, show the error message.

If you embed the reports in an application, you can manage the navigation logic from the host application. Check for data presence in Report B before allowing the navigation to that report.you can create a better user experience without merging datasets. The key is to use DAX measures and conditional formatting in Report B to inform users when no corresponding data exists.