Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Apps - Power Apps Pro Dev & ISV
Unanswered

Potential discrepancy between visual width and actual width of field in model driven app form affecting pcf rendering.

(0) ShareShare
ReportReport
Posted on by 98

Hello, I am facing an issue with correctly rendering a custom component on a model driven app field.

The component consists of a text field that only accepts numbers, with a list of items representing the numbers already submitted.

Here is an example screenshot of the component while testing it in the local host:

Capture.PNG

The four lines at the top are for debugging purposes and represent from top to bottom: The current calculated max number of items per row (based on an item's width and the container's width), the width of each item, the width of the entire container and the width of a filled row of items given the previously mentioned numbers.

 

The component is made to dynamically change the number of items per row and all other necessary data to fit whatever width the container has. For example:

Capture2.PNG

 

My problem occurs when pushing and testing it on the model driven app, here is a screenshot:

Capture3.PNG

    As is visible, the items on the far right are cut off, with their full width represented in the black outline. There also is another item on each row that is completely invisible as the entire rectangle is cut off, also represented with the black outline.

 

As you can see, in this case the container's width is close to 775. Now if I test it locally with a container of width 775, I get this:

Capture4.PNG

Which is the expected result, with the items that would've initially been hidden are now shown. This is the same set of numbers, so you can see the 14 and 55 on the far right of the first and second rows that were invisible in the above picture.

Note that in both cases, the Items count per row, items width, container width and total items width are all the same, which leads me to believe there is a discrepancy between the visual width and calculated width provided to the component on a model driven app field.

 

Any help is appreciated.

 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Power Apps - Power Apps Pro Dev & ISV

#1
WarrenBelz Profile Picture

WarrenBelz 85 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 63 Super User 2025 Season 1

#3
mmbr1606 Profile Picture

mmbr1606 55 Super User 2025 Season 1

Overall leaderboard