topic Re: Power BI Report Server Branding Issue in Report Server

Power BI Report Server Branding Issue

tim_hodges — Tue, 30 Jul 2024 08:32:48 GMT

Server Version: 1.20.8926.40580 (May 2024)

Issue:

A while back we investigated changing the branding on the server using the Multicolored example brand zip file seen here.
After creating the new branding package and successfully deploying it we noticed that one element refused to change with the new branding colours ("Primary" and "PrimaryAlt") which shows as #117865 (dark green) instead of #e71f85 (pink)

Reverting the server back to default branding doesn't alter it either, as if the link between the two is broken.

Once reverted back you can see the green remains.

All the elements in the json file were accounted for to make sure this colour wasn't in there.

Here's the JSON:

"name":"Multicolored example brand",
"version":"1.0",
"interface":{
"primary":"#e71f85",
"primaryAlt":"#ffffff",
"primaryAlt2":"#0080c9",
"primaryAlt3":"#009ad4",
"primaryAlt4":"#ffffff",
"primaryContrast":"#000000",

"secondary":"#0c499c",
"secondaryAlt":"#0c499c",
"secondaryAlt2":"#0080c9",
"secondaryAlt3":"#ffffff",
"secondaryContrast":"#ffffff",

"neutralPrimary":"#F2F9FE",
"neutralPrimaryAlt":"#ffffff",
"neutralPrimaryAlt2":"#b1d7ee",
"neutralPrimaryAlt3":"#0c499c",
"neutralPrimaryContrast":"#0c499c",

"neutralSecondary":"#F2F9FE",
"neutralSecondaryAlt":"#ffffff",
"neutralSecondaryAlt2":"#ffffff",
"neutralSecondaryAlt3":"#e71f85",
"neutralSecondaryContrast":"#000000",

"neutralTertiary":"#ffffff",
"neutralTertiaryAlt":"#ffffff",
"neutralTertiaryAlt2":"#ffffff",
"neutralTertiaryAlt3":"#ffffff",
"neutralTertiaryContrast":"#000000",

"danger":"#e60000",
"success":"#3fae29",
"warning":"#ffd000",
"info":"#0c499c",
"dangerContrast":"#ffffff",
"successContrast":"#ffffff",
"warningContrast":"#ffffff",
"infoContrast":"#ffffff",

"kpiGood":"#3fae29",
"kpiBad":"#e60000",
"kpiNeutral":"#ffd000",
"kpiNone":"#0c499c",
"kpiGoodContrast":"#ffffff",
"kpiBadContrast":"#ffffff",
"kpiNeutralContrast":"#ffffff",
"kpiNoneContrast":"#ffffff",

"itemTypeIconColor":"#ffffff",
"reportIconBackground":"#009ad4",
"excelIconBackground":"#009ad4",
"folderIconBackground":"#009ad4",
"datasetIconBackground":"#009ad4",
"otherIconBackground":"#0c499c"
}
}

Another poster had a similar issue which was fixed when they upgraded their version of report server to the January 2023 Release. Since our version is newer (May 2024) that hasn't resolved it.

Any ideas where to go next?

Thanks in advance
Tim

SOLUTION:

Added this additional code to the colors.json file.

"primaryButton": "#bb2124",

"primaryButtonHover": "#d31115",

"primaryButtonPressed": "#3d0000",

"link": "#d31115",

"linkHover": "#671215",

"linkVisited": "#3d0000",

"radioButtonCheckBox": "#bb2124",

"radioButtonCheckBoxHover": "#d31115"

Re: Power BI Report Server Branding Issue

Anonymous — Wed, 17 Jul 2024 01:47:44 GMT

Hi tim_hodges ,

This is picture which applyed the sample zip:

My power bi report server Version:

You can try this:

Brand the web portal - SQL Server Reporting Services (SSRS) | Microsoft Learn

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Power BI Report Server Branding Issue

Anonymous — Tue, 30 Jul 2024 05:09:21 GMT

Hi tim_hodges ,

Have your problem solved, if so, please mark as solution the correct answer.

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Power BI Report Server Branding Issue

tim_hodges — Tue, 30 Jul 2024 08:29:56 GMT

Sorry for the late reply, this worked perfectly. The problem was down to us using the colors.json example code embedded on this page.

The code missed out some key tags including:

primaryButton

primaryButtonHove

primaryButtonPressed

link

linkHover

linkVisited

radioButtonCheckBox

radioButtonCheckBoxHover

The top 3 were responsible for the button I was struggling with.

So instead I used the sample branding packages found at the bottom of the Microsoft page, they contained all the tags required and fixed it. Thanks very much for your help.