BUG - component Event not being triggered since update

[lizwharty]

Ever since the update that occurred in the last few days, all my buttons inside of components that Patch to SharePoint are no longer working (says it's after a text field). Until this update they were working fine. Can we please get a fix for this? 

[ElCazando]

I was able to restore as I save my apps a lot!

[ElCazando]

I did something similar:
was running an Event on the selection of a date in a custom date picker, I have created a button on the page that sits within the component. I copied all the code from the Event into the button OnSelect. This meant an extra click for the user however still accomplished my desired requirement:

Code in Event on Custom Component:

Custom Component on screen:

Button visible when ShowCalendar = true.

So clicking the button sets ShowCalendar to false hiding the button and the Component:

[anhtruongMSFT · Accepted solution]

Hi everyone, apologies for the inconvenience we have caused. We have listened to your feedback and have decided to revert the change and will look into an alternative solution. Please allow a couple of hours for the change to take effect after this response.

[_follone]

A temporary solution is to add the requested return, in your case it is text so just add an empty quote to the end of the formula, if the property is boolean it will request a bool so add true to the end of the formula

Ex:

[_follone]

Even changing the event data type it doesn't work correctly, I didn't define any parameters, but it still gives an error because the event table return has a different structure than the sample table which is the default value when I defined the event data type for table, I tried leaving the property blank when editing the component and restarting the application but the error persists

[trucbinh]

Hi @anhtruongMSFT ,

Now it runs without errors on my DEV environment, but doesn't run on UAT environment. I would like know if these updates will affect the published apps or only editing apps.

Regards,

Binh.

[anhtruongMSFT]

Hi @trucbinh , the breaking change has been turned off all across stations. And it shouldn't affect existing published apps. If you have made changes since the breaking change was released and published them, please try restoring the app version to an earlier version. 

[cipster]

Thank you! 🙂

[james_hathaway]

@anhtruongMSFT 

This is really poor behaviour from the Power Apps Development Team - but I guess I would expect nothing less!

"I know, let's just Change a load of core functionality, and not tell anyone at all..."

I'm sure if any of us Power Apps Developers did that to our Clients, we could potentially be prosecuted and sued for compensation caused by flawed computer systems - but standard development practices obviously don't apply to Microsoft...

For years now, I have had a real problem with Microsoft's "Update and Release Strategy" - but nobody is listening.

• We do NOT get any warning that the studio is now using an upgraded engine - it just updates our Apps without asking
• We do NOT get a CHOICE - it is simply forced upon us
• We are NOT given ANY fore-warning about what is changing
• We are NOT given any useful information about the changes implemented

I know some of you might say that they compile Release Documentation - but it is so laughably incomplete and poor, IT CANNOT BE TRUSTED AT ALL.

Case in Point - this is the release notes for version 23105:

Absolutely NO mention of the fact that "Component Event Properties are now completely different, and any that you have written will not work AT ALL any more" - Yet we KNOW (from experience, and the evidence given above) that downgrading to version 23104 removes this regression BUG - so clearly this was changed in version 23105.

I always laugh when I see a Release Document that says "No new Features or Bug Fixes"...

Oh really? Then why release a new version, if nothing has changed?

It's obviously a complete LIE, hence the documentation CANNOT BE TRUSTED.

PLEASE sort out your Release Strategy and Documentation - it is an awful experience for us developers, as well as probably ILLEGAL by Consumer Law ("Passing Off" is Illegal in the UK, as is false advertising of features/benefits of a product or service, as is sabotaging or downgrading a product or service that has already been delivered and paid for.

J.

[cipster]

Here here James!!!

I had to pick up the pieces from these updates, I can't keep up with them and I check the PA blogs regularly. This is extremely poor behaviour that leaves us in the dark and of course we get blamed not Microsoft.

I think PowerApps is the most amazing product ever released by Microsoft, it opened so many possibilities and the fact we can create great components is a big plus, but for the love of this universe dear PA Dev team, please listen to the community and communicate your changes better and in advance. It's like we're always chasing these changes and never really catching up. Give us some time to adjust.