Screen Height issue after saving change

[Anonymous]

After creating a list with around 20 fields; the default Edit form displays correctly, however after making a change to it to add a new field or by making the slightest change to it, the form does not stretch the full Hight of the browser window.

This is the original form without any changes.....

Here is how it looks after just adding one field to it and publishing back to SharePoint....

How can I get the form to stretch back to use the entire height of the window it is displaying in?

You might also notice the width changes... not a concern now, but it would be better if it wouldn't change by making an apparently unrelated change.

I already tried to change the Height on the Screen Size in the App Settings from Large to Custom and increased the size of the Height, but I can get it to stick to its correct/original height before saving/publishing the first edited version of the new form. BTW and also after adjusting the Width and Height all the Cards and Labels lose their corresponding size and location respectively from one another.

I look forward to any suggestion(s)... Thanks in advance!

Regards.

[v-xida-msft]

Hi @Anonymous ,

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned.

Please consider turn off the "Impeoved appp rendering (final validation)" option within Advanced settings of App settings of your app, then re-publish your app, check if the issue is solved.

Also please consider set the Height property of the SharePointForm1 (Edit form) to following:

App.Height

Please also check and see if the following article would help in your scenario:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/create-responsive-layout

Best regards,

[Anonymous]

Hello @v-xida-msft ,

Unfortunately, suggested changes did not work... here is the result of changing the Advanced settings and republishing...

Suggested link about "Create responsive layouts in canvas apps" is dated, the options "Scale to fit", "Lock aspect ratio" and "Lock orientation" are no longer available in the App's Advanced Settings section.

I did try changing the Height of the Screen to use "App.Height" as suggested; it did not achieve the dessired effect.

I can shoot a video if it helps.

I have tried this same process in two different clients and the result is the same, I don't think is local to my environment...

I look forward to comments.

Regards.

Salvador Rodriguez.

[v-xida-msft · Accepted solution]

Hi @Anonymous ,

Which Browser do you use to run your PowerApps custom form? Have you taken a try to run your app using Chrome?

Have you taken a try to customize the App screen size within your custom form app?

Please also consider take a try to custom your form app screen size as below:

then set the Height property of the SharePointForm1 to following:

App.Height

re-publish your app, check if the issue is solved.

Also please consider try your app in other different browsers, then check if the issue still exists. If the issue still exists, please consider remove the custom form from your app, then re-add a new one to fix this issue.

Best regards,

[Anonymous]

Hello @v-xida-msft 

I was testing with Edge, IE and Chrome.

Yes, yesterday I did try customizing the App screen size along with the other proposed changes and it did not work then; now I just tried again and this time changes did resolved the issue to get the form to stretch the hight of the browser window's vertical space.

Form is now taking more vertical space in IE. (This is what I was looking to get...)

This is how the same form looks in Microsoft Edge in Windows 10

Same form in Chrome.

Findings/Results:

Inetnet Explorer 11

• The form extends in IE to ocupy almost all vertical realstate; I need to do some more testing to make it fit all vertical space here.

Microsoft Edge

• Using Microsoft Edge the form displays a second container with its own vertical scrollbar.

Chrome

• The app now takes more vertical realstate.
• Rich Text Editor's ribbon does not displays correctly ( I will open another topic for this one).

Nonetheless and despite the unintended discoveries, the original request appears to be resolved.

I will do a few more tests and will mark this as the solution.

Thank you very much and best regards.

srodriguez