Unanswered

PCF on Portals: updateView not called after the value changed

(0) Share

Report

Posted on by Diana Birkelbach

3,072 Most Valuable Professional

I've tried out some of my field PCFs on Portals following the tutorial: https://docs.microsoft.com/en-us/powerapps/maker/portals/component-framework-tutorial?WT.mc_id=BA-MVP-5004107

It worked like a charm.

The only problem that I've found out: after we change a value (and call the notifyOutputChanged) the updateView is not called again (only getOutputs).

Usually the PCFs wait for the framework runtime to validate the input, and are designed to wait for updateView to be called with the new value. At least this worked until now for Model-Driven and CanvasApps PCFs, and was described here: https://docs.microsoft.com/en-us/learn/modules/get-started-component-framework/2-architecture?WT.mc_id=BA-MVP-5004107

Since the updateView is not called, my controls don't show the changed value (but they gets saved),

I suppose the Portals have another framework runtime, so I would like to ask if the portal PCFs are supposed to work this way. That would add some complexity to the controls, since the value is set both inside the PCF and outside through the updateView.

Or maybe not calling the updateView is just a bug for now, and we don't need to change the PCFs.

@HemantG , maybe you can help to clarify this.

Kind regards,

Diana

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Hemant Gaur Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Ack - Following up on this .

Thanks,

Hemant

Was this reply helpful? Yes No
gonara Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @DianaBirkelbach , Thanks for trying PCF on portals out and bringing this to our notice.
Can you please give us more details about how you are changing the value? Is it part of the component itself ? Also, if possible, can you share the component that you are using so that we can test and confirm from our end?
This seems to be a bug on our end and the PCFs need not be changed just for portals. This is what we are trying to achieve.

If you are changing the value of the control using client scripts in Portals, you could do so using the below snippet.

var hiddenFieldSelector = 'input[id$=' + logical name of the attribute + ']';
$(hiddenFieldSelector).val(JSON.stringify(NewValue)).change();

Thanks,
Gokul

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you so much @gonara .😀

An example would be the ColorfulOptionset: https://github.com/ORBISAG/ORBIS.PCF.ColorfulOptionset

Inside my own react component, I don't keep the value in the state: I rely on having my component called through updateView after the value was validated by the framework.

Maybe there is a better way to use the Dropdown Control (it was my first PCF), but I also have another PCF made with own created react component (without FluentUI), and I have there the same problem, since my component only needed the starting value, and onClick I only needed to notify the framework. I thought it was easier, and it worked until portals. In case you would like that code too, I can send it to you in a private message.
I didn't use any scripts in portals to change the value.

Kind regards,

Diana

Was this reply helpful? Yes No
gonara Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Ack. Will check this out. Thank you so much for the inputs.

Was this reply helpful? Yes No
gonara Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Diana,
Thank you again for bringing this to our notice. This indeed was a bug on our side. This is fixed and should be available with the next release. I tested with the ColorfulOptionset that you had shared and is working fine now. Also if possible can you share the solution of the other PCF that you were having troubles with, so that I can test and confirm that it fixes all scenarios?

Thanks,
Gokul

Was this reply helpful? Yes No
Abhishekchopra 16 on at

Like
a
(0)

Report
Copy link

Link copied!

Is it now available ?

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Abhishekchopra ,

Yes, it was fixed short after reporting this.

Was this reply helpful? Yes No
Abhishekchopra 16 on at

Like
a
(0)

Report
Copy link

Link copied!

In my case:
Still when we are creating new pcf component, after using notifyOutputChanged, it is triggering UpdateView only on local but after deploying to portal, it's not triggering UpdateView.

Was this reply helpful? Yes No