Answered

Modeldriven-Form Form Control - No Auto Height adjustment

(1) Share

Report

Posted on by MS-21101203-0

Hi,

i am currently trying to insert a related table-form (N:1 Relationship) into a Modeldriven Form with help of the "Form Control" into a Modeldriven-Form (Components --> Input --> Form).

This is working so far, but the form-control height is not adjusting to the height of the parent section.

I use a single column tab with a single column section and inside this section i use the form-control which shows a form of a related table entry.

is this a known issue?

All options to set a fixed height are gone, in modern designer and also in classic designer.

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

Valantis 6,735 on at

Like
a
(2)

Report
Copy link

Link copied!
Hi @MS-21101203-0,

from what i have sound Yes this is expected. The Form component control doesn’t expose a supported “height/rows/auto-resize” setting in the designer, so you can’t force it to stretch via a property.

If your tab is meant to show only this one control, the supported way to make it fill the available space is to set the tab’s content type to singleComponent (so the first component uses the full tab height/width) using the client API: tab.setContentType("singleComponent").

If you don’t want to change the tab behavior, the other supported options are:

Use Quick View if you only need read-only related data, or

Open the related record’s main form in a dialog via Xrm.Navigation.navigateTo(...) (you can set height/width there).

if you like check also here for more info:
https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/form-component-control
https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/design-productive-forms
https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference/xrm-controls/tab/setcontenttype
https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference/xrm-navigation/navigateto

Was this reply helpful? Yes No
Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @MS-21101203-0,

I have answered a question this morning, can you please check if this helps?

Was this reply helpful? Yes No
MS-21101203-0 14 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Valantis,

are you reffering with your first suggestion to this option:

If yes, this is already set. Or is tab.setContentType("singleComponent") giving another behaivor then this option?

Quickview is not an option, since i want to show a subgrid (with a pcf on top) of another related table of the related table entry and want to edit these rows.

it seems like that the form-control is just not using the available space, even if the option "Expand first component to full tab" is set and other components are using this space correctly

Was this reply helpful? Yes No
Verified answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @MS-21101203-0,

you might need to edit then the css file. check the following articel might help you.

https://www.r2power.de/blog/responsive-canvas-app-in-model-driven-form

Was this reply helpful? Yes No
MS-21101203-0 14 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Valantis,

thanks for replying. I investigated this issue a little bit further and also tried to edit via css file.

What i figured out so far: The Form-Control Component itself uses the correct height. But since it only renders the first tab of a MDA Form (no Tab Selection is rendered), without the logic of the parent-tab (e.g. the option to Expand the first component to full tab), the section does not get this parameter and is rendering by its default height.

If the section has more controls, these are shown correctly in its height. But in my case the section would only have one subgrid (with a PCF overlayed) , there is no option to set the height of the subgrid or the section.

Was this reply helpful? Yes No