web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Passing in PCF paramet...
Power Apps
Answered

Passing in PCF parameters at RUNTIME in PowerApps

(0) ShareShare
ReportReport
Posted on by 48

Hello all - 

 

Currently the properties defined in the menifest can be setup and configured at DESIGN time in the form designer.

 

It is also possible to passing the input paramters at RUNTIME in the harness debug app. 

 

However, is it possible to passing in parameters at RUNTIME in Powerapps/Dynamics, via form script? Basically inject values into the "context" for controls of type "customcontrol:****"

 

if so, how? If not, will that be a feature coming?

 

Thanks!

 

 

 

I have the same question (0)
  • Verified answer
    Min Rao Profile Picture
    187 on at

    I have following idea but have not tried yet . hope we can discuss in this post. ( whether this would work or not and if it works whether it is a recommend or not,  also anything need to be careful.) 

     

     -  Bound component to string text field A on the form. 

     -  Set field A 's submit mode 'never' onload of the form.

     -  Interact form and component using this field A by following approach

         - Component to Form :  Pass json string from getOutputs from component to form. field A's onchange should be trigger and you can get this json string.

         - Form to Component :  Setvalue of the field A should trigger component's updateview, you can get waht you want  by context.paramters.xxx.raw.

     

     

  • liun Profile Picture
    48 on at

    @MinRao 

    Thanks!

    This can be a reasonable workaround before "Unbounded Control" is available:

    https://powerusers.microsoft.com/t5/PowerApps-component-framework/Unbounded-Controls/m-p/316409#M553

     

    My use case is displaying various data on the form that do not need to be saved in DB, but the calculation is more complex than calculated field can handle and has to be done by javascript code. 

     

    The only thing seems unexpected is that in the form to component, updateView is not always triggered, if setValue is been called multiple times within a small timewindow https://powerusers.microsoft.com/t5/PowerApps-component-framework/updateView-is-not-called-on-every-attribute-change/m-p/351323#M782. But it can be resolved by accumulating values in the JSON object. 

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 431

#2
WarrenBelz Profile Picture

WarrenBelz 360 Most Valuable Professional

#3
Kalathiya Profile Picture

Kalathiya 280 Super User 2026 Season 1

Last 30 days Overall leaderboard