CopilotStudioEmbed Power Platform Solution v1.0.3
Fixes the control not appearing as an addable Canvas app code component.
What changed
- Changed all PCF manifest properties from
usage="bound"tousage="input". - Added Canvas-friendly
pfx-default-valueentries for maker-configurable properties. - Bumped the PCF control version to
1.0.3and solution version to1.0.3.0. - Retains the v1.0.2 production-size bundle fix and the v1.0.1 manifest apostrophe fix.
Verified package checks
npm run buildsucceeds in production mode.npm run lintsucceeds.pac solution packsucceeds for managed and unmanaged packages.- Packed
ControlManifest.xmlhas onlyusage="input"properties and nousage="bound"properties. - Packed
bundle.jsis 4,114,358 bytes, below the prior import failure threshold. MSPFE2019.CopilotStudioEmbedis present as a solution root component.
If it still does not show in Power Apps Studio
- Confirm the solution imported into the same environment where you are editing the canvas app.
- In Power Platform admin center, enable Power Apps component framework for canvas apps for that environment.
- Reopen Power Apps Studio after importing the solution.
- Use Insert > Get more components > Code, select CopilotStudioEmbed, then choose Import.
- After import, expand Code components in the insert pane and add it to the screen.
Assets
- CopilotStudioEmbedSolution_1_0_3_0.zip — Unmanaged solution
- CopilotStudioEmbedSolution_1_0_3_0_managed.zip — Managed solution
Use this release instead of v1.0.0/v1.0.1/v1.0.2.