Forum Discussion

Mat42's avatar
Mat42
Resolver I
4 years ago
Solved

Drilldown Chloropleth Publishes while Uncertified

Does anyone know why the Drilldown Chloropleth map visual will publish on the Power BI service despite being an uncertified visual?

 

Our tenant settings have 'Add and use certified visuals only' set to Enabled so only certified visuals can be published and . But a member of staff noticed that the drilldown chloropleth can be published, despite being uncertified. I thought that it may have been due to it being a Microsoft visual, so tested it against another uncertified Microsoft visual (Drilldown cartogram). The chloropleth publishes but the cartogram doesn't.

 

Can anyone tell me why an uncertified visual is publishing?

Need Help

2 Replies

  • Mat42's avatar
    Mat42
    Resolver I
    4 years ago

     I only realised that I hadn't replied to this thread when the 'A solution has been accepted' email came through, so apologies for that.

     

    Thanks for the replies. I had reviewed that information previously, and everything had been set so that the only visuals that should have published in the service were either certified visuals or those we had agreed could be used. However, the chloropleth visual seemed to sit outside of those settings. It isn't PBI certified and we haven't approved it for use, yet it still published online. As far as we were concerned, everything had been set as it should.

     

    I ended up just fiddling with every single setting - turning them on/off, publishing the report, and seeing if the visual published - until I turned up the problem: It doesn't publish if we set the 'Allow visuals created using the Power BI SDK' setting to 'disabled'.

     

    Now, I know nothing about the SDK, so I don't know how to find out which visuals have been created using it. As far as I can see, nothing in the visual write-up or description explains that is was created using the SDK. Maybe I'm missing something fundamentally obvious. Maybe hundreds of visuals are created using it and turning it off will crash a bunch of reports, but without an implicit stamp on the visual description explaining that the SDK was used I have no idea which visuals will publish and which won't with that setting enabled.