Announcements
I have a component that suddenly started reporting a formula error. The issue is that the error is on the .Y property of the component, which shouldn't be editable on the component itself. Seems like a bug. Anyone know of a way to clear this error?
@JroderickMP
Check the formula in the Y property for this control. This error typically occurs when something the formula refers to got deleted. Its a pretty common error and my hunch is its not a bug with PowerApps.
---Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Right, but the issue is that this error is coming from the component definition itself and not an instance of the component placed on a canvas. I cannot access the Y property of a component when designing a component.
I hope that made sense...
When the little red error appears there are two options when you click on it.
Do you have the "take me to the error" option? If yes, what happens when you click it?
That is what I expected as well, but the using the drop down doesn't take me to the error to fix it. The .Y property should not be editable for the component itself while in the component editor.
Just for the heck of it... can you check all the Y property for all instances where this component is being used in the app? Maybe there is an error somewhere else in the app (though you are right the error message does not say that).
No luck. I think I will have to re-built it 😕
**bleep**. I am all out of ideas.
Before you re-build try to export the component and then reimport it. That's my only other idea.
Good idea - but no luck. I just re-built it from scratch. Thanks for the help regardless!
Sorry that I wasn't able to help 😞
In case anyone else runs into this issue...
There is indeed a bug with components, where a property of the component (it also was Y for me) that is not accessible in the designer somehow ends up with a value in it. I tried manually ripping apart solution file and re=importing back overtop of the corrupted component (not a process for the faint of heart) but couldn't manage to successfully repair the corrupted component. I eventually just restored an earlier version.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 342 Super User 2026 Season 2
M Bilal Khan 283
Mohsin Ali 221
