I've been out of the technical weeds for many years, but I have a few ideas I am trying to implement within dynamics. After hitting roadblock upon roadblock using the out of the box dynamics features. I decided to try PCF. And to be honest it's driving me nuts.
I think my frustrations are partly being rusty, partly trying to run before I can walk but mostly dynamics itself.
Environment Details:
Region: UAE (United Arab Emirates)
Environment Type: Sandbox
Integration: Finance & Operations linked environment
Version: Current Dynamics 365 (created May 2025)
What Works:
PCF control builds successfully (npm run build)
Solution packages without errors (dotnet build --configuration Release)
Can see the interface I am building OUTSIDE of dynamics
Solution imports successfully into Dynamics
Control appears in Solutions → Components as "Custom Control"
No import errors or warnings
What Doesn't Work:
Control never appears in Canvas Apps → Insert → Get More Components
Control doesn't show in Model-driven app form field controls
Control not available in Custom Pages component library
Silent failure - no error messages anywhere
Configuration Verified:
"Power Apps component framework for canvas apps" enabled in admin center
User has System Administrator privileges
Manifest includes bound property (usage="bound")
External service usage properly declared
Standard control type (not dataset)
Manifest Structure:
Bound property (first)
Input properties
Output properties
External service declarations
Standard feature usage (WebAPI, Utility)
Question: Is this a known limitation with UAE region, F&O integrated environments, or sandbox environments? Or are there additional configuration steps needed for PCF controls to appear as usable components after successful import?
Additionally, when I go to Canvas Apps → Insert, I don't see any 'Get More Components' or 'Add Components' option at all - not just missing my PCF control, but no component insertion capability whatsoever.
What am I missing here???
