search

microsoft / powercat-creator-kit

This toolkit helps create well-designed Power App experiences on the web & mobile. It contains a component library; PCF controls and other utilities that increase developer productivity.
MIT License
322 stars 55 forks source link

[BUG]: People Picker control On Change event does not fire in Runtime #479

Open PRusakPL opened 4 months ago

PRusakPL commented 4 months ago

Describe the bug For control People Picker (https://learn.microsoft.com/en-us/power-platform/guidance/creator-kit/peoplepicker) out of the sudden On Change event stopped triggering in runtime mode for published apps What is weird - this event works when debugging the app and staying in make.powerapps.com (play mode)

To Reproduce Steps to reproduce the behavior:

  1. Use People Picker control in your Canvas App
  2. Use On Change event in the control to react on changes happening inside
  3. Code in On Change event should execute when change happens (put any code - even simple Notify("Change of the people picker value"); )
  4. Your code will not fire - control become almost useless without this event being triggered properly

Expected behavior On Change event should be triggered in runtime. I am not sure what is blocking this event.

Screenshots When using app in debugging mode in make.powerapps.com On Change event works and label is populated with JSON value of array with selected user(s): image

When using app in runtime - label generated in On Change event is not populated (I also checked other code: Logging / notifications - not firing too) image ⬆️ No JSON above - code in OnChange was not fired :-/

Additional context I am using recent release of Creator Kit solution (Solution version: 1.0.20240529.1) image

I used recent Edge browser and Google Chrome browser - both have issues with triggering On Change event

denise-msft commented 2 months ago

@PRusakPL our team was not able to reproduce the issue. In our repro, the OnChange behavior was triggering as expected.

Could you please let us know if you're still seeing the issue on the latest studio version (please share the version if possible).