PCF Controls with FluentUI v9 - Avoid DOM id collisions
Recently, while developing a PCF control with the FluentUI React v9 library, I encountered a rather unusual and annoying runtime display bug. Its resolution ended up shedding light on an important concept that had previously escaped my attention and I thought it deserves its own blog post.
🤒The symptoms
The control I was developing is my latest community PCF control, the FluentUI Month Picker.
🔗FluentUI Month Picker | PCF Gallery 🔗 GitHub repo : drivardxrm/FluentUI.MonthPicker.PCF
Published on:
Learn moreWe can help you with PCF Controls with FluentUI v9 - Avoid DOM id collisions
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
PCF Controls Tips & Tricks: How to Bundle and Resolve Static JSON Files
JSON files are one of the most common and convenient ways to store structured data. They’re lightweight, human-readable, and easy to parse in ...
PCF Controls Tips and Tricks : How to skip Linting at Build-Time
Have you ever been unable to properly build a PCF control because of linting errors? Well, lately I have, and it can get really frustrating. E...
PCF Controls Tips & Tricks : How to detect Authoring Mode
When you configure a PCF control on a Dataverse model-driven app, the form designer will try to render the control even though it’s not ...
How to Create Deep Links to D365 F&O Records with Dataverse Virtual Tables
It is a common requirement for SaaS platform that exposes form over data to be able to share a secure link (a.k.a. Deep Link) to access a give...
Model-Driven App Trick : How to Hide a Ribbon Button when the Form is Dirty
I recently encountered a requirement on a model-driven app project to display a custom ribbon button only when the form had no unsaved changes...