Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now

Reply
Anonymous
Not applicable

Creating custom Chiclet Slicer

Hi!

 

I have been using the Chiclet Slicer in my report, but need to comply with certain coloring and formatting conventions. The text color needs to be white, and the text within the chiclets needs to be left-aligned, to name a few. Now I know the chiclet slicers are open-sources, so I cloned the code and went to edit it. Now, I am trying to re-package the files so that I can import them as custom visuals in Power BI online.

My issue is that the 'pbiviz' command is not able to successfully run, despite very little being changed in the code itself. I have followed a number of tutorials that explain making custom visuals, but cannot package this one.

What is the issue I am having?

 

Any help or tips would be appreciated. Thanks!

3 REPLIES 3
dm-p
Super User
Super User

Hi @Anonymous,

Without getting detail of the output for your pbiviz command, it's hard to provide targeted help. Are you running pbiviz package or pbiviz start when you get the error?

Here's my guess as to what you might need to get started correctly:

I presume that you have the latest version of the custom visuals SDK (3.1.x) installed?

If so, from looking at the pbiviz.json in the GitHub repo, the visual is using version 1.13 of the SDK/API. So, instead of installing the latest version of the SDK (which is 2 versions higher than this and there are some breaking changes), you'll need to install the target version the visual was developed on. Instead of using this command to install the SDK:

npm i power-bi-visuals-tools -g

Run this:

npm i power-bi-visuals-tools@1.13 -g

You will then need to re-initialise your certificate as per setup instructions, as the version has changed from the one you had installed.

If you haven't updated the Node.js packages required for the visual then run this afterwards:

npm i

Provided that these two pre-requisites have been fulfillled, you should be able to run pbiviz start or pbiviz package successfully.

If you're still having trouble getting this to run, please come back with your output and I'll try and have a look for you.

Good luck!

Daniel





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!


On how to ask a technical question, if you really want an answer (courtesy of SQLBI)




Anonymous
Not applicable

Hi @DM ,

 

I was able to 'downgrade' by running the script:

npm install -g powerbi-visuals-tools@1.13

 I couldn't get the exact one that you suggested to run, but I rearranged and ran again with apparent success.

After navigating to the visual folder, my attempt to run the

pbiviz package

Was the following:

pbiviz_error.PNG

 

Hi @LC 

Sorry, I forgot to mention to run this after updating the SDK:

 

pbiviz update

 

To ensure that the SDK downloads the correct version of the API code into the .api folder (which is how the older version stores the API locally... the newer version uses the node_modules folder). 

This will potentially require another refresh of the certificate if you want to use pbiviz start afterwards.

You should then be able to run pbiviz package.

One other thing to consider if you're packaging:

  • The Chiclet Slicer is a published visual, so if you try to load it into either Power BI Desktop or the Power BI Service, the version in the marketplace will always be loaded.
  • This is to ensure that for visuals in the marketplace, the current version is always served, so that you don't have to worry about manually updating your reports.
  • You will need to assign a new guid if you're rolling your own visual so that you can test it.
  • Open pbiviz.json, and find the guid field under the visual object key. For reference, here's the corresponding line in the Chiclet Slicer source code.
  • Modify this number to something unique - you can probably add a '1' to it and that should be sufficient.
  • You might also want to change other parts of the file, e.g. the displayName, so that you know the visual is not the original Chiclet Slicer when you see it in the visual palette (particularly if you have the original loaded in there too).

Hopfully this should be the rest of what you need. Apologies for missing that out originally.

Good luck!

Daniel





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!


On how to ask a technical question, if you really want an answer (courtesy of SQLBI)




Helpful resources

Announcements
April Power BI Update Carousel

Power BI Monthly Update - April 2026

Check out the April 2026 Power BI update to learn about new features.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

FabCon and SQLCon Highlights Carousel

FabCon &SQLCon Highlights

Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.