Forum Discussion
Power BI Embedded Custom Color Themes in Reports do not promote
GibsonPBI,
I am unable to reproduce this issue. Do you use Power BI Desktop August release? Could you please share the JSON file so that I can test?
Regards,
Lydia
I made sure that I had the August release.
I have attached screenshots of the 3 various steps in the process.
From PowerBI DesktopFrom PowerBI OnlineAfter getting the code from "Publish to the Web"
- GibsonPBI8 years agoFrequent Visitor
I could not see how to attach the JSON file, so I pasted it below:
{
"name": "CHPA Analytics",
"dataColors": [
"#0071B9",
"#A4CF5F",
"#DD8E07",
"#71B1D1",
"#AE94BA",
"#67B9AD",
"#FFF48B",
"#63666A",
"#5CBAE5"
],
"background": "#FFFFFF",
"foreground": "#8AA8D7",
"tableAccent": "#3A75C4",
"visualStyles": {
"*": {
"*": {
"*": [
{
"fontSize": 10,
"fontFamily": "Arial",
"color": {
"solid": {}
}
}
],
"general": [
{
"responsive": true
}
]
}
},
"filledMap": {
"*": {
"legend": [
{
"show": true,
"position": "Left",
"showTitle": true,
"labelColor": {
"solid": {
"color": "#561912"
}
},
"fontFamily": "Arial",
"fontSize": 8
}
]
}
}
}
}- Anonymous8 years agoNot applicable
GibsonPBI,
Based on my test, the issue is caused by triple wildcard in the JSON file. It is recommended to update the theme file to be more specific with the visualStyles section, replacing one of the wildcards with a specific entity (visual type or formatting card name). Please check attached JSON file. Using it, custom theme will retain after we publish report to web.
"visualStyles": {
"*": {
"*": {
"*": [I got response from PG:
As the Theme feature is in preview, and the triple wildcard is technically working as expected, there is no “fix” coming. We also identified a popular third-party Power BI Theme Generator website (non-Microsoft) and asked the owners to change their tool to avoid creating triple wildcards.
Regards,
Lydia- GibsonPBI8 years agoFrequent Visitor
I downloaded the JSON you provided, applied it to my desktop version, re-published to the web. All was fine (as it was initially). The problem behavior for me still remains the same in the final portal that I am using to "embed" the pages with the "publish to web" option. If I change the visuals (new graph, etc) in my base file and do the various steps to "publish" them, those changed visuals do promote through to our customers portal (which is an "azurewebsites.net" solution). The issue is that the viusals lose the custom colors that the JSON file probvides, and the embedded report pages revert back to the default colors of Power BI. Is there something that the web guys I am working with need to do as well to make these custom colors follow all the way through to the embedded visuals?