We have used the plugin succesfully, to embed a report in Dynamics 365 CE using context based filtering.
We are filtering on [account].[accountnumber], and experience that the filter attributes is not correctly passed to Power BI, when the value consists of numbers only, despite the field being a String.
We have fixed this, but editing the customizations.xml directly afterwards:
Changing:
<PowerBIFilter>...,\"operator\":\"In\",\"values\":[$a],\"filterType\":1}]","Alias":{"$a":"accountnumber"}}</PowerBIFilter>
To:
<PowerBIFilter>...,\"operator\":\"In\",\"values\":[\"$a\"],\"filterType\":1}]","Alias":{"$a":"accountnumber"}}</PowerBIFilter>
It would be nice, it this is being done by he plugin. So that if filtering attribute datatype is String, the "values" placeholder will be qouted.
Thanks.
We have used the plugin succesfully, to embed a report in Dynamics 365 CE using context based filtering.
We are filtering on [account].[accountnumber], and experience that the filter attributes is not correctly passed to Power BI, when the value consists of numbers only, despite the field being a String.
We have fixed this, but editing the customizations.xml directly afterwards:
Changing:
<PowerBIFilter>...,\"operator\":\"In\",\"values\":[$a],\"filterType\":1}]","Alias":{"$a":"accountnumber"}}</PowerBIFilter>To:
<PowerBIFilter>...,\"operator\":\"In\",\"values\":[\"$a\"],\"filterType\":1}]","Alias":{"$a":"accountnumber"}}</PowerBIFilter>It would be nice, it this is being done by he plugin. So that if filtering attribute datatype is String, the "values" placeholder will be qouted.
Thanks.