PCF - PowerApps Component Framework - with Implementation | Dynamics 365

[@khwong98]

Excellent works.

[@powerdynamixx]

I'm glad you enjoyed the content. Your support means a lot!

[@rashimalhotra8642]

Hello. I have an entity in my model driven app which has 2 fields which are same. Both the fields have my custom pcf control enabled. Now, if I update value of one field, the updateview method is called only for that field. How to call the updateview for the 2nd field at the same time?

[@powerdynamixx]

Could you make sure both PCF controls use the same shared state? When a field is updated, both controls should read and write to the shared state to stay synchronized. Use the same context parameter for both PCF controls. Context parameters allow PCF controls to communicate and share information. Check for changes in the shared state in the updateView method of your PCF controls. If the shared state has been updated, update the control's display accordingly. This way you can check when one field is updated, the shared state will be modified, and both PCF controls will be notified of the change, triggering their updateView methods and keeping them in sync.

[@rashimalhotra8642]

@@powerdynamixx okay, thank you so much for the response 😊 . But how do we make sure that both pcf controls use the same shared state? How is that configured?

[@powerdynamixx]

@@rashimalhotra8642 To ensure both PCF controls use the same shared state: Define context parameters in the PCF controls. Set the same context parameter for both controls in the form editor. Read and write to the context parameter within the PCF control code to share data and stay synchronized.

[@ngaihoho4095]

Hi, can I install some other modules by npm install when I make a new control. I tried to npm run build the file and a return error said that can't find the module but it was installed

[@powerdynamixx]

It seems there might be a configuration issue with your npm installation. The error message you mentioned "the module couldn't be found" despite being installed. Well it can happen due to various reasons like incorrect path configurations or conflicts between different versions of dependencies. I would suggest to double-check if the modules are truly installed. Navigate to your project directory and look for the node_modules folder. The installed module should reside within this folder. Secondly, try clearing the cache and reinstalling the module. Check the specific versions and dependencies to avoid conflicts. Try removing the node_modules folder and package-lock.json file from your project directory and then re-installing the dependencies by running npm install again. Hope this helps! Let me know if you need further assistance.