PowerApps Error on non accessible property

(1) Share

Report

Posted on by BK-02041330-0

Hi there,

I do have an error that is there in all of my screens in my application:

But there is no .orientation property available in the screen component.

Any idea on how to fix this?

Thanks for your help

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like (1)

Report
Copy link

Link copied!

hi @BK-02041330-0

can you try something.

Go to Settings, display

Change the orientation and or size.

Then change it back to whatever you had before. I would definition Publish first, so that you have a copy of your app before you do this so you can restore it if the steps cause you any issue.

Next, if that doesn't work, turn off the new Analysis Engine, and see if the issue goes away. If so, save a publish. Then turn it back on and see if it fixes it.

if these help please mark as resolved.

thanks!

Was this reply helpful? Yes No
BK-02041330-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thanks for your answer.

I tried all your suggestions, but none has been successful :(

Was this reply helpful? Yes No
ronaldwalcott 3,880 Moderator on at

Like (0)

Report
Copy link

Link copied!

Run App checker and provide any error messages generated.

Was this reply helpful? Yes No
Verified answer

Michael E. Gernaey 53,963 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @BK-02041330-0

Not that I want you to have to do this..

But if you create a new App and copy everything to it, does the error stay?

Let me say. I had this exact same issue happen to me. An internal field that I had no access to, couldn't do squat. I had to literally copy everything to a new app to make it go away.

Was the most annoying thing I ever had happen, except when my shoe fell off into a giant mud... lol 4 ft sink hole. ugg

Was this reply helpful? Yes No
BK-02041330-0 6 on at

Like (1)

Report
Copy link

Link copied!

Thanks Michael,

This is what I did... and the error is no longer there

Was this reply helpful? Yes No