suddenly numerous component related (brown) errors like :Cannot use boolean values in this context

[HansHeintz]

Example: I have a self made menu component with an CloseMenu action property.

In my app this property uses this code

UpdateContext({lToonEventGroepMenu:false})

;UpdateContext({ShowItemMenu:false})

Simply two context variables which are set to false.

I get the error "Cannot use boolean values in this context"

Like I stated there are suddenly numerous errors like this (not red but brown) in my app on component event properties.

What happened, what could be wrong?

[mmbr1606]

hey @HansHeintz 

is it possible that you can show us screenshots of your issue(s)

thanks in advance

[HansHeintz]

I guess my old component event properties were f.e. of type text, perhaps because ther was no 'none' back then (or text was default and there seemed no need to change) and meanwhile this was ignored but now triggers warnings.

[HansHeintz]

A word of warning about this issue!! If you'd think to just change the event result type of your component event to none, all event code in your app that for instances of this component will be obliterated silently!!

[HansHeintz]

Only way to get rid of the warnings afaik is

-make new event properties without deleting the old ones

-search for all code that uses the old events within the component and change the references to the new events

-process all warnings in the app by cut (and replace with "") the code for the old event and paste into the code for the new event

(97 warnings in my case pffff)

[PowerGon]

Thanks @HansHeintz for reporting, I'm experiencing the same issue (666 new warnings in my app 😈).

Sorry for the spanish @mmbr1606 but the issue is just the same previously described:

Thanks in advance.

[firdaus]

Same issue for me as well. Got 465 warnings on the app. All are related to boolean variables used in UpdateContext.

This was not the case till yesterday.It is coming from today morning.

[mmbr1606]

in my point of view this looks like a general issue and not a specific one (when multiple people have the same problem)

[HansHeintz]

Personally I would like Powerapps to be far more strict about variable types to prevent misery later on so I can understand the change. But a somewhat softer landing / more subtle handling might be nice.

[GlennBullion]

Just to add my two cents. I'm having the same issues. Variable and controls / components that all worked yesterday are returning : "Cannot use boolean values in this context".

As I'm actively working on the app right now, I figured it was something I did by accident. Starting combing through to see if I set the variable in question as a boolean somewhere else, which would break every other instance of it. But nope, it's set as as a string all throughout the app. Good to know I'm not the only one.

Is this one of those times we just have to wait Power Apps for a fix?