Context

On the Wiiisdom Cloud Platform, you can simulate their journey by selecting slicers and specifying the values they want to apply.

However, under certain conditions, slicers may not behave as expected. Instead of applying the selected value, the system appends a new value at the end of the slicer instead of using the existing one. For example, when selecting "Value 1" from the available values, the slicer may not be set correctly, leading to unintended results.

How to reproduce the issue

This issue occurs only on specific slicers, depending on the configuration of the underlying table in Power BI.

Table Configuration Impact

In Power BI Desktop, if a table is configured as follows:

• The slicer displays values using the "Full" column.

• However, in the background, Power BI requires the "ID" (key column) to be sent instead.

Under these conditions, the issue arises when selecting values in the slicer.

Comparison with Other Tables

For example, if another table uses its default configuration:

1. No label or key columns are explicitly set.
   

Because of this setup, slicers based on parameters from Table do not experience the same issue.

Impact

Currently, certain slicers are not functioning properly within our application. Unfortunately, the Wiiisdom Cloud Platform does not provide a way to identify which slicers will work and which will not.

1. Check the model view of the document in Power BI Desktop to see how the table is configured.

2. Review the execution report—if the system incorrectly adds a value at the end of the slicer instead of using the existing one, this indicates that the slicer is not compatible.

Since this issue depends on table configuration, you need to manually verify slicers before relying on them for accurate filtering.

Plan of Action

The Engineering Team has identified a potential solution to properly configure slicers, which could resolve the issue. This fix candidate will now proceed through our Software Development Life Cycle (SSDLC), as detailed in our Trust Center, to ensure it meets our quality standards.

If you would like to be notified when this issue is resolved, please contact the Support Team.

Temporary Workaround

Until then, if you encounter this issue, there will not be a functional workaround available. The only way to determine if a slicer is affected remains:

• Checking the model view in Power BI Desktop

• Reviewing execution reports to see if a value is incorrectly appended

Please be aware of this limitation when setting up their slicers.