Components executing events automatically when editing within formula bar

[cipster]

Hi all,

I have quite a few components with a custom OnSelect event behaviour. Since yesterday every time I try to edit the Component.CustomOnSelect property in an app it just triggers whatever I have there if I click anywhere within brackets. For example, if I have something like Navigate(ScreenName); when I click on the formula bar it just navigates to the screen. This makes it incredibly difficult to edit the code, I have to insert a random character so it produces an error then do it blindly as suggestion stop working in the formula bar. I've tried everything, I created brand new components, same issue across all environments, using different accounts, different computers, different authoring versions. The odd thing is that if I monitor the app the execution from the formula bar doesn't get recorded, even though it's actioned.

Does anyone else experience this? Has anything changed in the past few days that I might not be aware off?

Also, it's been a while since enhanced properties were released and are still experimental. It's been, I think, 4 years since components have been released. When do we get some peace of mind and they get out of experimental. We use components extensively across the university and it will be a disaster if they get withdrawn.

[cipster]

Anyone? 

There are now two more users confirming the same bug.
Re: Components triggering when editing code - Power Platform Community (microsoft.com)

[nataliap]

Exactly same issue here, it has ruined my developed apps which are used by clients

[cipster]

Hi @nataliap 

Just had a chat with Microsoft support, maybe better said a contractor for them. We all confirmed the issue occurs from version 3.24031.25 onwards. We created a component on the call and it triggered from the formula bar. Reverting to version 3.24024.18 fixed the issue for me. Unfortunately they cannot do anything further as they do not support experimental issues however they said to raise the issue in the Ideas section of the community, have no clue what that is. I suspect that Microsoft will look into this as some point but the feel I got from the call is that experimental features are not priority for them, even though components have been around for ... ya know ... 4 years or more.

[numeroeins]

Yeah, I noticed the same problem. Now go and try to create a custom component and you will see that the property types Data, Event, Function, and Action were replaced with Input and Output. The latter two options were once nested under the "Property definition" dropdown. Furthermore, when you have a look at existing components, you will see that any property using Data, Event, Function, and Action cannot be edited like the others. 

BEFORE

AFTER

[joaoandre83]

Certainly, I can help refine the English version for clarity and coherence:

Yes, many people are encountering the same issue. I witnessed this problem firsthand at a live event, and a friend of mine ended up sending numerous emails unintentionally, which is quite troublesome. I'm surprised there aren't more complaints about it.

In all my applications, I've implemented a condition If(__dev__,...) that defaults to true. I switch it to false during development, and place all the subsequent code after this condition, to prevent it from being triggered while I'm working on the development.

But it's becoming a significant issue now, as all the environments I work in are experiencing the same problem.

[ShantanuP · Accepted solution]

Thank you for reporting the issue. The issue has been fixed in version 3.24041.0

[numeroeins]

Thank you for the information.

[jfritz]

This is still an issue in version 3.24034.17 for PowerApps for Teams. Just had my delete component run and delete data (dummy) while writing the code on an Component Event.