-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - SearchBox for address disappear after selecting other filter from the page #65
Comments
I have the same issue. When i try to select another filter, the <div's> that contains the searchbox suddenly dissapear. On the process we see this: Appears the image with this message when i change any of 6 segmentations filters that i have on my report: This message during aprox 1 second and after that the control and searchbox dissapear: |
i couldn't reproduce the bug, could you a give a more detailed step by step guide how to reproduce it? |
Hi @VassTamas87, you need to publish the report on PBI Services. On Desktop the visualization works fine but once you publish the report on PBI Services occured this. The only data that we used is a latitude and longitude. You need to add a segmentation filter that capable to filter the data (for example, use a dataset with coordinates and name of the cities, and make a segmentation filter based on cities name), when you change the filter, the bug appears. If you need more information please let me know and help you. |
Hi,
Please find attached PBIX file. You need to publish this report on PowerBI workspace. On workspace when you select any option from slicer, search box for address will be disappear.
Thanks,
Prashant
From: VassTamas87 ***@***.***>
Sent: Wednesday, May 3, 2023 1:20 PM
To: starschema/mapboxgl-powerbi ***@***.***>
Cc: Jagani, Prashant ***@***.***>; Author ***@***.***>
Subject: Re: [starschema/mapboxgl-powerbi] [BUG] - SearchBox for address disappear after selecting other filter from the page (Issue #65)
[External]
i couldn't reproduce the bug, could you a give a more detailed step by step guide how to reproduce it.
-
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7NO3GBNZPPWILRDWII64LTXEKOVFANCNFSM6AAAAAAXLPXE7E>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Hi, I just wanted to inquire about the expected timeline for resolving this bug request. I understand you and your team are busy with various requests and priorities, but having an estimate of when this bug might be addressed would be helpful for us because It's affecting our production dashboard. |
@prashantj1 in my case, i change the mapbox viz with ARCGIS map viz. |
i couldn't reproduce the bug. For me it seems that is working as expected. @prashantj1 Could you send the PBIX file again? The email doesn't have any attachments. |
@VassTamas87 Confirming that this issue is still happening with MapBox. Primary reason for using MapBox over other visuals is the address search bar functionality that allows us to search for any address. In order to recreate this issue, you will need to publish the PBI to any workspace and pull up the report on any browser. You will not be able to recreate this issue on PBIX desktop. When you select a slicer while on the browser, the search box disappears. Attached zip file; pbix file format cannot be attached here. If you are unable to recreate this issue, would it be possible to request a screen share session? Any help to expedite resolution would be greatly appreciated. Thanks. |
good news, with the PBIX file you have sent i can see the bug. |
Describe the bug
I'm using Mapbox Satellite street visual in PowerBI report. when I select from a slicer on the page, search address box is disappearing from the Mapbox visual. This issue only happens in the online version (means after publishing the report) . In PowerBI Desktop, this is working perfectly fine.
Expected behavior
When I select any other filter. Search Box for address shouldn't disappear.
Screenshots
The text was updated successfully, but these errors were encountered: