Bullet Chart stopped working

smatsonamcor commented 1 year ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

The Bullet Chart visual started acting unusual starting on 7/20, even on reports that were already in production and have had no recent development updates. The color scheme of the visual changed without any developer interaction. The Category field isn't allowing certain fields to populate any data. We have used this field in reports for years and have not had any issues. This is happening both in the Power BI Service and in Power BI Desktop. It is happening in the service to reports that we have not made changes to for some time.

Power BI

Power BI Desktop, Power BI service

Power BI Version

2.107.683.0 64-bit (July 2022), but also May 2022 and June 2022

Steps To Reproduce

Go to Categories tab. in the Bullet Chart visual, remove the field that's in category and add Size. Nothing happens.

any field I add that include a blank value causes the same problem. If I add "Weight Unit Measure" nothing happens. If I then add Weight Unit Measure to the "Filters on this Visual" and then uncheck the "blank" item, the visual populates. This is the behavior I'm experiencing within our reports that have had blanks in the data for a long time.

Sample report

bulletChartByOKViz-tour.zip

even the sample file provided by okviz is behaving unexpectedly. If I were to attempt to add the field Size to the category, nothing happens. This seems to be similar to what is happening in our environment. In addition to the fact that the colors of the visuals just simply changed in reports that we did not update in any way.

Screenshot

No response

Anything else?

No response

smatsonamcor commented 1 year ago

i'm wondering if this could have anything to do with the field being used in the Category field having blank values. But again, we've used this visual for years with the same data without issue.

danieleperilli commented 1 year ago

Please elaborate more on this "The Category field isn't allowing certain fields to populate any data". About other reports:

Main problem of disappearing bars - see #3
Color changes: if the color is the comparison bar, unfortunately we changed where that field is stored internally to fix other bugs and this caused the sudden change of the color. I'm afraid you have to manually change them again... I'm sorry.

smatsonamcor commented 1 year ago

So, if the Category field has any blank values, then the graph won't refresh with data.

Here is the sample file from OKVIZ for this visual. Add the field "Weight Unit Measure" as the category. Nothing happens. Then filter out the blank value and the graph will update.

Scott Matson

www.amcor.comhttp://www.amcor.com/ @.***

From: Daniele Perilli @.> Sent: Wednesday, July 20, 2022 4:13 PM To: okviz/bullet-chart-issues @.> Cc: Scott Matson @.>; Author @.> Subject: EXTERNAL: Re: [okviz/bullet-chart-issues] Bullet Chart stopped working (Issue #6)

Caution: EXTERNAL Email

Please elaborate more on this "The Category field isn't allowing certain fields to populate any data". About other reports:

Main problem of disappearing bars - see #3https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fokviz%2Fbullet-chart-issues%2Fissues%2F3&data=05%7C01%7Cscott.matson%40amcor.com%7C7126d3e24221431473de08da6a94a25d%7Cfe9c207fda30422682b5bff6ef031c8c%7C0%7C0%7C637939483854224400%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6ORqWTdHEJZHwf8pwQpIG7BWvNlA6CFLHLHYWCZc0js%3D&reserved=0
Color changes: if the color is the comparison bar, unfortunately we changed where that field is stored internally to fix other bugs and this caused the sudden change of the color. I'm afraid you have to manually change them again... I'm sorry.

- Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fokviz%2Fbullet-chart-issues%2Fissues%2F6%23issuecomment-1190763003&data=05%7C01%7Cscott.matson%40amcor.com%7C7126d3e24221431473de08da6a94a25d%7Cfe9c207fda30422682b5bff6ef031c8c%7C0%7C0%7C637939483854224400%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9OpG5NJXeiYLcnom5JhhLodTOqW8eXIXqnmIRGIs0XM%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA2E5MUBNU5YKIL3HKZFCITLVVBTV5ANCNFSM54FCKYAA&data=05%7C01%7Cscott.matson%40amcor.com%7C7126d3e24221431473de08da6a94a25d%7Cfe9c207fda30422682b5bff6ef031c8c%7C0%7C0%7C637939483854224400%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uN%2Fmb1UB0Kzbwg3EvXHmNjXObEeQD9mfC0zximFuWiE%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

danieleperilli commented 1 year ago

Thanks for your feedback, we found the issue and the next version will contain a fix.

smatsonamcor commented 1 year ago

I appreciate the update. Do you know when that next update will be?

Scott Matson

ebeery11 commented 1 year ago

The issue I am seeing is that in horizontal orientation, toggling the data labels to "On" immediately prevents more than one measure / category from appearing.

See below for an example from the OkViz sample.

Bullet Chart Bug - OkViz Sample.zip

aktharH commented 1 year ago

The bullet chart seemed to have collapsed and stopped working suddenly for me today 21.07.2022 on both desktop and power bi service . version i am using is 2.2.9.2. Will i need to download a new version with the fix ? when will the new version be made available ?

riccard0russ0 commented 1 year ago

@ebeery11, @aktharH fixed in Version 2.2.9.4 - that will be released on July 27th.

jimhill-jt commented 1 year ago

I am running into the same issue with existing reports that suddenly went blank. When I remove the blank values, the data reappears. How will we know that the fix has been published so we can download the update?

jimhill-jt commented 1 year ago

One additional thing that I noticed. After removing blank category values the data bars once again were displayed; however, if I then tried to turn on Data Lables only the first column would display. All other became invisible. Please make sure that the Data Lables works when you fix the blank values issue. Thanks!

07TJ commented 1 year ago

The issue I am seeing is that in horizontal orientation, toggling the data labels to "On" immediately prevents more than one measure / category from appearing.

See below for an example from the OkViz sample.

Bullet Chart Bug - OkViz Sample.zip

This solved my issue. Only one of the category was populating in my visual, when I put Data Label as OFF it started flowing for other categories as well. But another issue is that both Category Label and Data Label cannot be enabled together!!

reubedude commented 1 year ago

Hello, we are experiencing similar issues in the last 48 hours. A number of OkViz bullet charts that are in production in Power BI reports have turned blank, with no underlying development having been made to the model or to the reports. The issue is replicated in Power BI desktop and Power BI service.

I note above there is a fix to form part of the next release 2.2.9.5. Is there a timeline for this release?

Thanks a lot!

danieleperilli commented 1 year ago

@reubedude It is scheduled for July 27th

reubedude commented 1 year ago

@danieleperilli thank you

mshparber commented 1 year ago

Same here:

The Data Labels are not working
The visual shows only one item in a category
If I use several nested fields - the labels are concatenated even if I turn off the "concatenate" option.

Guys, such things should not happen in production versions. If you make changes - please do them in the new release only. Many of my existing Dashboards stopped working and the clients are not happy. I am checking other visuals now, although the OKVIZ Bullet Chart used to be my favorite.

Please fix it ASAP. Thank you

danieleperilli commented 1 year ago

@mshparber I see that you sent a similar email to my email address, I will only reply here. I apologize if this has caused major issues for you and your customers. A fixed version will be deployed to everyone on July 27, but you need to understand that we sent this version on July 12 as a priority fix, while the previous version (the buggy one) was already in the deployment cycle. Certified visuals take up to 3 weeks to be released, we have no control over this.

We strive to write good code, but we are human beings, and bugs do occur. We will continue to update our visuals, not just new ones as you suggest, sorry. We hope to avoid these problems in the future, of course.

danieleperilli commented 1 year ago

@mshparber Regarding the issue you mentioned about the concatenation, please create a new issue on this repo with more details and a sample file, because no one reported it yet, so it will probably still there in v2.2.9.4, we need to check it.

stugr commented 1 year ago

@danieleperilli are you able to provide release notes for the version that will be deployed on July 27th? With so many bugs being introduced I'd like to check them off and submit additional issues for anything that hasn't already been addressed.

Additionally, have you considered releasing an older working version on your website that people can use in the meantime? Like you do for card with states, as referenced here: https://okviz.com/blog/how-to-downgrade-a-visual-imported-from-the-appsource-marketplace/

danieleperilli commented 1 year ago

@stugr v2.2.9.4 fixes the problem with Data labels + categories, and the Display unit of axis values. If you find other bugs, please report the through new issues on this repo.

About private versions: we stopped releasing private version since they are not certified, also the licensing system provided by Microsoft wouldn't work.

santrilla commented 1 year ago

This has inspired us to stop using OKViz custom visualisations and swap back to the (much less attractive but much more stable) standard Power BI charts. A shame, because we used this bullet chart on pretty much all of our multi-page 40+ production reports across our 100+ daily users, but we can't build a reporting platform around a visual that will just flat-out stop working with no warning.

I appreciate that mistakes happen and that the publication process is slow, but it doesn't inspire great confidence in the certification process if something like this will make it through even after those three weeks.

marcosqlbi commented 1 year ago

@santrilla You can imagine our feeling after we predicted the risk of the single version of the visual available in the AppSource and then being affected by the very problem we described the moment we tried to adopt the new licensing API from Microsoft. OKVIZ provided free visuals for many years, and the existing features will continue to be free. Getting revenues from advanced features would have started to cover part of the multiple-year investment. This is not a good start. We will continue to provide feedback to Microsoft. Unfortunately, we are not able to control the versioning for certified visuals. I would like Microsoft to implement features to enable that at least for Power BI administrators that should control the version of the visuals deployed in their tenant. Until then, you should consider that all the visuals have the same publishing pipeline and potentially the same risk.

relax528 commented 1 year ago

Will this latest release address the visual not being exportable (copy visual as image, and export report to a PDF, PPT) even though it's listed as certified? Or is this a different issue all together? Let me know and I can open a new issue if necessary. Thanks!

danieleperilli commented 1 year ago

@relax528 This is weird, we don't have control on this thing. Which version are you using?

mshparber commented 1 year ago

@marcosqlbi thanks for the reply. OKVIZ bullet chart used to be my favorite visual ( I am a fan of Stephen Few's DataViz techniques)
I implemented it in many of my clients' dashboards. With the latest release (2.2.9.2), everything broke. Hours of time spent to look for alternatives (at the end I used the Error Bars feature of the native Bar Chart) Microsoft should allow rollback to previous version. This is so important or else it is hard to rely on a visual. They should hear this message. Thank you for addressing this issue, looking forward for a fixed version

mdLinkII commented 1 year ago

kinda silly workaround...but fyi: was building new report and noticed horizontal bulletchart working at one point then ceased. went back thru process checking along the way. changing field data type and format was cause. data type = decimal and format = general seemed to solve quite a few issues mentioned above (at least for me).

_as to not disrupt format of these bulletchart fields used elsewhere in report, workaround was creating new column that simply pointed to field needed (eg. "BCTarget = MyTable[Goal]") then changing its format.

relax528 commented 1 year ago

@danieleperilli

We had a report that was used in a dashboard and subscription that was working just fine. Then last week (not sure which day for sure), the tiles in the dashboard wouldn't paint, they were just blank and shown below. We thought there was something with the subscription. But then noticed the report itself wasn't painting the visuals either. The version of the bulletchart in this report is 2.2.9.2 and the about page shows the visual is certified. Then one of the developers tried to "fix" it and loaded the visual from a file, which turned out to be version 2.2.8 and was not certified. That version however did paint correctly so hoping this release tomorrow will fix out issue.

Thanks

danieleperilli commented 1 year ago

@relax528 It is not possible to "fix" the visual on your side and keep the certification, because a visual is certified only if it comes from AppSource (and meets certain requirements). I too hope that the new version will fix your issue, but you can send your report so that we can check on our end if you want to.

stugr commented 1 year ago

AppSource is now showing a 2.2.9.5 version with a date updated of 27/07/2022 but upon loading this into power bi desktop all the bugs still remain and the version in the about section is listed as 2.2.9.2

marcosqlbi commented 1 year ago

@stugr In theory the 2.2.9.4 should be deployed today, this is what we have been told by Microsoft. When you import the visual you still get this message at the moment:

*Our latest version 2.2.9.4 is currently being deployed and will be fully available within 10 days.

I hope it will be deployed later today. Unfortunately, we have zero control over that.

ajt11223344 commented 1 year ago

Appears the issue still exists in the new release - is there a timeframe for remediation?

danieleperilli commented 1 year ago

@ajt11223344 Please wait to end of the day, we don't have control over the deployment process.

ajt11223344 commented 1 year ago

@ajt11223344 Please wait to end of the day, we don't have control over the deployment process.

@danieleperilli I've checked this morning and the fix still hasn't gone through? What's delaying the fix?

stugr commented 1 year ago

@marcosqlbi @danieleperilli now upon import the message returned says 2.2.9.5 instead of 2.2.9.4 however the visual is still 2.2.9.2 (I have deliberately waited until the date is now the 28th in Redmond)

Along with fixing display unit of axis values, will the new version also fix the display unit of tooltips as it's settings are also being ignored?

marcosqlbi commented 1 year ago

We are waiting for an answer from Microsoft. They told us that yesterday was the date for 2.2.9.4 delivery.

marcosqlbi commented 1 year ago

Unfortunately, we have bad news from Microsoft. They pushed the delivery date to August 3, and told us the previous date was wrong. However, we have an email they sent us with that date, and we have an ongoing discussion about this issue.

As we are unable to change anything on AppStore, we kindly ask you to open a ticket with Microsoft support in order to make them aware of the magnitude of the problem, so that someone can realize the impact of this delay and try to fix the issue as soon as possible.

To open a ticket and you are a tenant administrator, you can use the following link: https://admin.powerplatform.microsoft.com/newsupportticket/powerbipro

If you are not a tenant administrator, you can start from this link and follow the instructions: https://powerbi.microsoft.com/en-us/support/pro/

NickyvVr commented 1 year ago

For anyone also opening a support ticket, you can file it under Create and Author Data > Using Custom Visual on the above links Marco mentioned :-)

marcosqlbi commented 1 year ago

Thanks @NickyvVr !

ajsully commented 1 year ago

Medtronic has opened a ticket with Microsoft with TrackingID#2207220040007262 - in case anyone needs that number as we build a case with Microsoft that many people need this.

cathoms commented 1 year ago

I tried submitting a ticket but didn't see a way to submit it. I've never used the system before...

Nevermind, I figured it out. Support request #2207280040006807

PowerBIwjkolesar commented 1 year ago

Medtronic has opened a ticket with Microsoft with TrackingID#2207220040007262 - in case anyone needs that number as we build a case with Microsoft that many people need this.

Brookfield Properties has submitted ticket #2207280040005226.

Mpicca commented 1 year ago

This has been an extremely frustrating break that has me re-considering the use of any 3rd party visualization. I've had to spend days fixing many reports and dashboard that I've created for clients that use these visuals. At the end of the day I cannot tell a client that a break like this is some random persons fault whos at the other end of the world, they look to me to build something that is reliable. I really hope that this forces how you guys push changes to Production visuals.

I appreciate the free visuals for years, and love how you guys attributed to building up the BI community, but mistakes like this effectively weakens my position with clients who don't understand the technicals too well. The impact is too large across the board to make a mistake like this.

marcosqlbi commented 1 year ago

@Mpicca I completely understand your frustration. The irony is that we are victims of our own predictions. While we do our best to release the highest quality, we make mistakes. But let me give you some additional details.

We published this article two years ago: https://okviz.com/blog/updating-power-bi-custom-visuals/ Because Microsoft was launching a new licensing system on July 2022, we were convinced to be part of the early adopters, and we extended Bullet Chart with additional features. In theory, the free version would get free updates and other improvements with the back of a sustainable economic model: We had a long list of pending issues and zero resources available to fund them - please keep in mind that Bullet Chart and many other OKVIZ visuals can be used for free, we are only adding premium features now that requires a license. Long story short, the new code was impossible to test for a larger audience because it was using a new API not available to the public until the public preview. Bullet Chart has thousands of companies using it worldwide, and despite our tests, something went wrong. We believe that requiring a single version to be deployed to all the customers through AppSource creates an issue. We are not in control of the deployment time, we could ask Microsoft to roll back to the previous version, but it seems that this requires four days to be fully deployed. Thus, whoever uses new features or was affected by other bugs would see the visual working correctly for a few days and suddenly be broken again. It's a lose-lose situation. Managing change is hard; we are committed to providing full transparency (which is why I'm replying to your comment). We have successfully deployed quick updates for Smart Filter Pro as a private visual (not certified) for several years now. We can fulfill the obligations to the customers if we are in complete control of the deployment process. The certification process for custom visuals is mainly a security and compliance review, but it does not provide real quality control. We knew that; we warned customers about that, and we failed to follow our suggestions. However, we are providing feedback to Microsoft because we firmly believe that a healthy custom visual ecosystem can bring more options to report authors. I still hope that improvement is possible. The alternative is to keep the standard visuals and not rely on any custom visuals because - as you noticed - you cannot stop automatic updates.

I understand your choice of not using custom visuals anymore. I just wanted to provide more background information to other readers who might think that the risk is vendor-related (OKVIZ) rather than intrinsically high (because of the deployment process) when you use any third-party custom visual deployed through AppSource. Two years ago, I wrote that private non-certified custom visuals are "safer" to keep a reporting system running: unfortunately, my description is still accurate today.

mshparber commented 1 year ago

Case opened: Case 2207310050000102

07TJ commented 1 year ago

Case Opened : Tracking ID:2207280030001828

I had received the following response from the microsoft support engineer.

"I have now had an update from the custom visuals team. They have confirmed they have already approved the publication of the fixed version but can’t speed up the release process as this is outside their control. They expect the first wave of updates to be available on the 3rd August followed by a second set on 10th August. I would suggest we carry out some tests on the 4th August to see if the first set of changes resolve your issue and if not follow up on the 11th August.

As mentioned previously a second approach would be to try and get hold of the source files. I have asked the custom visuals team if these are available, but they may well be confidential, and it is likely you would need to approach OKViz directly to get access to these. I will update you further as soon as I get more information from the custom visuals team as to whether they can share the source files.

I’m very sorry to have to have to share the news that we cannot expedite the roll out of these changes. I have made clear the urgency of your request, but these type of roll outs are on very strict schedules."

@marcosqlbi, @okviz team can you tell the feasibility of providing source file, as it is extremely critical

vertikasr commented 1 year ago

TrackingID#2207220040007262.

Thank you @07TJ for the update.

@okviz , it would be really helpful if you can provide the source files.

marcosqlbi commented 1 year ago

@07TJ @vertikasr Getting access to the source file would not solve the problem - the source code is merely something you should still compile and deploy into a pbiviz local version of the visual. What you may want is a pbiviz file with a local version of the component that is not the one you get from AppSource. However, this would require you to manually update every report where you have the Bullet Chart visual, and once you do that you would not receive any future updates. Assuming this is all good, now there is the tricky part. The new (fixed) version of the visual wouldn't work, because it's tied to the new licensing engine and it doesn't work with deployment through a pbiviz file. If you really want a pbiviz file that (could) work, you should rollback to a previous version of the visual, not certified by Microsoft, that doesn't use the new licensing API. Considering that the issue described in this thread is included in version 2.2.9.4 that should be deployed by August 3 (the version deployed on August 10 has other fixes), I would suggest you wait two days, rather than getting a version that could break your report in a different way (we never tested what happens going back to a previous version in an existing report).

stugr commented 1 year ago

I opened ticket #2207280030001390 with microsoft last week as well. I am pressing for further info on the timezone used for release dates and at what time on this date they do the release. Their product team is in Israel

Will update once I get further info. Currently from live chat:

generally it is the US time my experience should be 4th August for Australia time I will check with the engineer this afternoon to get the exact time

The support person has also escalated my feedback around the dates and version shown in AppSource being incorrect, as well as the message you receive about version when importing the visual

Edit: Update from Microsoft around timing:

Just checked with our product team, they mentioned the ETA is end of Aug 3 UTC+2 time zone. that means in Thursday morning 8 AM UTC+10, it should be available for you to use the version with issue fix

marons13 commented 1 year ago

Hi All,

I think a found a solution and the root cause of the issue. I noticed that bullet charts with values < 2,000 rendered perfectly fine and bullet charts > 2,000 weren't rendering. My fix was to divide the values I had by a value that would make it <2,000. This will mess up the values of the tooltips but you can do a page tooltip.

Additionally, I think the fix would on the OKVIZ side would be changing the upper bound somehow of the graph because I think that's the issue

danieleperilli commented 1 year ago

@marons13 Sorry, the solution you provided doesn’t fix the issue of this post (that we already fixed in v2.2.9.4). If you are referring to another bug, please open a new issue.

danieleperilli commented 1 year ago

The v2.2.9.4 should be available for everyone right now. If you find other bugs, please create a specific issue on this repo.

We are already aware of some that will be fixed in the future versions, check the roadmap here: https://docs.okviz.com/bullet-chart/changelog

okviz / bullet-chart-issues