Forum Discussion
Azure Maps reference layer conditional formatting polygon
Hello,
Really liking the new dynamic Azure Maps reference layer which relates to data.
Hoped this would make it possible to use the conditional formatting option.
However this isn't working, as you can see below.
When i use the regular polygon option (not a reference layer) it works fine.
Does anyone know if I am missing something, if it is a bug, or just an upcoming feature?
Thx!
Hi Anonymous ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and consider giving a KUDOS. Feel free to reach out if you need further assistance.Regards,
Dinesh
Hi
Are you using the URL as the file source? If so, we've fixed the issue, would you try it again? The fix had been deployed to production couple weeks ago.
6 Replies
Anonymous
I believe you need to include the fill color property within the gecoding file (geojson)
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
Did I answer your question? Mark my post as a solution! If I helped you, click on the Thumbs Up to give Kudos.
Proud to be a Super User!
Hi Anonymous ,
Thanks for reaching out to the Microsoft fabric community forum.
In addition to tharunkumarRTK response, Please find the below document.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and RegardsHi Anonymous ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and consider giving a KUDOS. Feel free to reach out if you need further assistance.Regards,
Dinesh
Hi
Are you using the URL as the file source? If so, we've fixed the issue, would you try it again? The fix had been deployed to production couple weeks ago.
