It looks like, within SharePoint, the div `#SharePointForm1container > .appmagic-borderfill-container` that holds the PowerApps new-item form has its styles set incorrectly. `overflow` is set to `hidden` when I need it set to `auto`.
This is happening when I create a new PowerApps custom form within SharePoint from scratch.
Solved! Go to Solution.
Did you mean the blank area on the bottom of the Form on SharePoint list?
The first screenshot shows what I see when I create a PowerApps "new item" form for SharePoint. The form is much longer, but I'm unable to scroll down past the first screen.
The second screenshot shows the CSS changes I have to make myself, using my browser's developers tools, to enable scrolling. Once I do this, the PowerApps "new item" form scroll exactly like they used to.
I added a scrollable screen and copied my form to it. Much better but it still won't scroll all the way to the bottom. Tried extending the height property of the form, but it doesn't help. How can I make it scroll so all fields are visible?
Is there a solution to this? I've seen a few topics on this issue but no real solution...unless I missed it somehow. It's Feb. 2020 and I can't get a customized SharePoint list form to scroll / display all the fields. I increased the height of the form, but it will not scroll and so the user can't access all the fields. It cuts off the form and leaves blank white space, for some reason. Do I really have to recreate the whole thing on a new scrollable screen? Couldn't this just be a configuration in the form properties? This kind of negates the notion that Powerapps is super easy to spin up.
On another note - I have another custom form experiment that will not open in Edit mode despite the fact that I have the SharePointIntegration, the form settings, all data card settings, all default settings -- EVERYTHING -- is set to Edit mode. I'm finding this not viable as a forms solution in SharePoint.
I have the same problem. Not sure if there is a solution found to this problem. Fixing on chrome will solve it for local browser, but looking for a solution for all chrome browsers. Has someone found a solution to this, for me this problem is still pending and not resolved