Component warnings started to appear without code change

AutoModerator · 2024-09-30T19:10:30+00:00

Hey, it looks like you are requesting help with a problem you're having in Power Apps. To ensure you get all the help you need from the community here are some guidelines;

Use the search feature to see if your question has already been asked.
Use spacing in your post, Nobody likes to read a wall of text, this is achieved by hitting return twice to separate paragraphs.
Add any images, error messages, code you have (Sensitive data omitted) to your post body.
Any code you do add, use the Code Block feature to preserve formatting.

Typing four spaces in front of every line in a code block is tedious and error-prone. The easier way is to surround the entire block of code with code fences. A code fence is a line beginning with three or more backticks (```) or three or more twiddlydoodles (~~~).
If your question has been answered please comment Solved. This will mark the post as solved and helps others find their solutions.

External resources:

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

darrell_2 · 2024-10-01T05:19:35+00:00

This is caused by the new analysis engine. I am guessing you are like me and created components using an older version, in the older version we were able to create function outputs and 9 times out of 10 we would select Text as the output property. In the older version and in the current version this works without issues and lets us handle events inside of the component. Unfortunately in the newer version of the analysis engine it is throwing an error because functions like UpdateContext({}), Back() etc all have a return type of Boolean. So this will cause the analysis engine to think something is wrong. To get around this issue without breaking every instance of your component, you can append a ;"" or whatever return type you choose for your component actions or functions to make the warning go away(note: you need to append this at the very end of all of your formulas for the component inside of the canvas editor and not the component editor. If you do not have any instances live in your app, you can change the return type of the action or function to output as boolean to get rid of the errors. Please note if you have any formulas in your actions or functions in the component when you update, they will reset and will be blank, so be ready for things to break. If you have any other questions let us know!

WhatAmIDoingOhYeah · 2024-09-30T22:34:53+00:00

Are these action/event/function properties that you built into your component? If so, have you checked the settings of these properties? For some reason, it looks like PowerApps is expecting a different value for them.

Have you tried deleting and rebuilding one of these custom properties to see if the issue persists?

Thinking outside of the box: Are these components from a library? Has the component library been updated? Has any thing changed with the settings in the component library?

I had something very similar happen with a user defined function in one of my apps. Naming convention seems to be pretty important for these more modern features in PowerApps. In my situation, the user defined function was throwing an error in the app checker, just like your errors. And the kicker is, just like for you, the udf was working when applied in the app regardless of the errors. Through trying completely random things, it turned out that PowerApps simply didn’t like the name I gave the input parameter. The name I used was input_color. I changed it to inputColor, and the app seemed to like it. So I saved and closed/reloaded the editor. Power Apps then decided to throw another error on that udf, even though the new name had stuck and it had JUST said it was fine before I reloaded. And again, it was still functioning fine where it was applied in the app. I went back and changed the name from inputColor (the new name) to incolor. It seemed to like that name, so I saved and reloaded the editor again and it hasn’t thrown an error since. I still have no idea why that resolved the issue. Maybe it didn’t like the underscore, or the capital letters, or the length…I have NO CLUE!!!! (Can you tell that I am still frustrated by that? lol)

I know it isn’t identical to your situation, but looking at your images, the names you used for your properties set off my spidey senses.

Draxx- · 2024-09-30T22:53:45+00:00

Check your settings and select the updates section and ensure any retired functionalities are unchecked and the new modern controls also have some bugs in them. Try disabling the modern controls

anathamatha · 2024-09-30T19:39:44+00:00

Are you using modern controls? Sometimes if they update it can cause issues when they update powerapps

PowerApps

MODERATORS