Answered

fluentui version when creating virtual pcf control

(0) Share

Report

Posted on by Ctse

I've noticed an issue with the latest versions of the Pac CLI (version 1.50.1+gabb74d2, but also with version 1.49.x) when creating a virtual pcf control with react and fluentui using this command:
pac pcf init -n ReactSample -ns SampleNamespace -t field -fw react -npm

It creates a new pcf control with a newer version of react-components (version 9.68.0 instead of 9.46.2).

ControlManifest.Input.xml:
<platform-library name="Fluent" version="9.68.0" />

package.json:
"dependencies": {
"react": "16.14.0",
"@fluentui/react-components": "9.68.0",
"react-dom": "16.14.0"
},

When trying to push this pcf with the Pac CLI, I got this error:
platform library fluent_9_68_0 with version 9.68.0 is not supported by the platform.

The documentation shows a strange situation with 9.46.2 as allowed version, but 9.68.0 as loaded version:
https://learn.microsoft.com/en-us/power-apps/developer/component-framework/react-controls-platform-libraries#supported-platform-libraries-list

Of course I can change the versions in the ControlManifest.xml and package.json back to version 9.46.2, but the Pac CLI should create the PCF control with the right version and I'm curious, because I would like to use version 9.68.0 of @fluentui/react-components instead of 9.46.2, because of some nice improvements.

My question: Does anyone knows if and when 9.68.0 comes available as platform-library for virtual pcf controls?

Categories:

Power Apps component framework

I have the same question (4)

All responses (2)

Answers (1)

Michael E. Gernaey 52,569 Super User 2025 Season 2 on at

Like (1)

Report

fluentui version when creating virtual pcf control

HI @Ctse

I looked all over, I do not see a release date specified anywhere on any pages (github/releases plans etc)

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

Ctse 43 on at

Like (0)

Report

fluentui version when creating virtual pcf control

I discoverd that with a little tweak FluentUI v9.68.0 is already working in a virtual pcf control.

The trick is that you install @fluentui/react-components v9.68.0, but in the Control Manifest Xml file you set the FluentUI version to v9.46.2

So, with this set in the Control manifest Xml file and in package.json it's working:

ControlManifest.Input.xml:
<platform-library name="Fluent" version="9.46.2" />

package.json:
"dependencies": {
"@fluentui/react-components": "9.68.0",

"react": "16.14.0",

"react-dom": "16.14.0"
},

If you take a closer look in the documentation this makes sense, because it's saying that FluentUI v9.68.0 will be loaded, despite the Control manifest Xml file says FluentUI v9.46.2 is used, but it doesn't make sense that you have to pull this trick. Its also disappointing that the documentation does not explain this more explicit.

https://learn.microsoft.com/en-us/power-apps/developer/component-framework/react-controls-platform-libraries#supported-platform-libraries-list

Was this reply helpful? Yes No