Unanswered

Container Columns and Component Columns not working

(0) Share

Report

Posted on by Community Power Pla...

Is anyone else having problems with the model-driven form designer not respecting the columns in the containers. I have a container set to 3 columns, and components set to 1 column. Initially, they displayed with 3 components per row, then as some point it hiccupped and now they all display as 1 column. In this first image you see that the container is set to 3 columns. In the next picture you see the component is set to 1 column. This happens to me regularly.

Screenshot 2023-08-28 141705.png Screenshot 2023-08-28 141722.png

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

MarioRing 541 Super User 2024 Season 1 on at

Like (1)

Report

Yeah, sometimes this editor works very strange in terms of layout management. In that case, I use the legacy "classic mode" editor - it sometimes helps (or it is even worse 😠).

If the form is not so complex, try creating a new one from scratch.

Was this reply helpful? Yes No
Fubar 8,340 Super User 2025 Season 2 on at

Like (2)

Report
Classic is more consistent with showing the correct layouts. Appears to be an issue with the size of the layout in the editor.

The 'flakiness' I have observed
Less likely to occur on single column Tabs
Closing the field selector on the left and then zooming the Browser will sometimes show the correct layout (i.e. the browser zoom, not the plus/minus zoom at the bottom of the editor)
Often when dragging a field from the field selector it does not display when it is dropped (saving and then refreshing the browser shows it in the position it was dropped)
The Editor often does not position the field at the top of the Section (if you open in Classic you see empty space above it and can reposition it correctly only in the Classic)

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Sounds like there isn't a real solution, only work arounds, until Microsoft puts more spit and polish on this. I am going to close the ticket. Thank you to everyone that gave me advice.

Was this reply helpful? Yes No