Error "slicerTargetDoesNotMatch" while embedded report with custom visual slicer loads

Hello,

yes, it is correct. The table name and column name are identical in this case. Changing from custom visual slicer to the standard slicer for this target the error does not occur and the standard slicer is showing the correct values set by the slicer filter from embed configuration and the report is filtered correctly.

Removing the slicer completely so that no visual matches the target error message "slicerTargetDoesNotMatch" also appears. So I think this the type of error is thrown in the case where no visual in a report matches the target.

So I think that the part (probably server side) of power bi which applies slicer filters from embed configuration to the report does not take the custom visual slicer into account. Perhaps because the type of the custom visual slicer is not "slicer" as by the standard slicer but the class name of this custom visual.

Maybe it is a limitation of Power BI embedded at the moment that custom visual slicers are not considered having slicer filters preapplied on report load.

Best regards