cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
keathley
Advocate III
Advocate III

Toggle Visibility BUG In Improved App Rendering (final validation) Mode

I have an app that has been working correctly, however recently toggle visibility has stopped working (not sure which update caused this; I will try to do some more research to narrow that down.)  I do know that the issue exists in 3.18091.15 (possibly earlier versions as well).

 

The app has a field / toggle that when true shows other fields / toggles.  Such that if "Other Permits" is true / yes, then a list of other toggles for the various permits is shown.  By default Other Permits is false / no and the other fields are hidden (as shown below).

IMG_9611e.png

Upon toggling the field to yes the other fields are shown (as shown below).

IMG_9612e.png

 

Upon toggling the field to no, and then yes again the other fields are shown, but their toggles are not (mostly, one toggle does appear) (as shown below).

IMG_9613e.png

Setting Improved App Rendering off resolves the issue.  Setting it back on again reintroduces the issue.

 

For reference, the visible field on one of these toggles simply references the Other Permits toggle's value.

OtherPermitRequiredSwitch.Value

This issue is witnessed on an iOS device.  It does not occur in a web browser.

 

Any help would be greatly appricated.

 

Joey

40 REPLIES 40

@mr-dang Okay I have finally narrowed this down, and I am certain it is a bug at this point.  I have also reproduced the issue in a new app.  I will comment on this again at the end of the post to explain my statement (the bug may be in app creation and not render).  Appologies up front for the lenght of the post.  I believe it would help to document step by step how to recreate the issue.

 

1) Create a new SharePoint list (5 columns, each a yes/no with default of no; I forgot to turn off allow attachments, so I will deal with it in a later step). 

SharePointList.png

2) Create a PowerApp from the SharePoint -> PowerApps -> Create an App menu item

CreateAppMenuItem.png

3) On the Edit screen, remove / delete the Attachments card.

Attachments.png

 

4) Find the name of the first toggle (here we will see it is DataCardValue8)

FirstToggle.png

 

5) Set the visible property of each of the t2-t5 datacards to the following:

DataCardValue8.Value

Each of t2, t3, t4 and t5 are now hidden:

VisibleSet.png

 

6) Hold ALT and toggle t1 to "on"; making t2-t5 visible again

t1on.png

 

7) Select the t2 data card, and review the "Height" property on both the formula bar and the properties panel.  Note that they have 50 and 122 respectively. I believe this is the root of the problem.

SizeDiscrepancy.png

 

😎 Select the t2 label (not the data card) and note that its width is 

Parent.Width - 60

NoteWidth.png

 

9) Note that my next couple of screenshots were done out of order (you will note that the label has already moved to the right even though it should not be yet by step order).  Follow the step not the image! 

Select t2's toggle button, and in the Properties panel on the right, change the Position X value from 30 to 100.

setxontoggle.png

 

10) Select the t2 label, and in the Properties panel on the right, change the Position X value from 30 to 100.

changeX.png

Note that the border for the t2 label now extends beyond the canvas.

 

11) Using your mouse drag the width of the t2 label back inside the canvas.  I do not know if it matters or not, but I also slightly changed it's height and then tried to put it back to the original height.

dragwidth.png

Note that its Width property is now your new width.  For me it is:

375

Side note that if you change the width formula instead of dragging, it does not seem to cause the issue.  I was able in one test to change the formula from 

Parent.Width - 60

to

Parent.Width - 60 - 100

and not reproduce the issue.

 

12) Save and publish the app.  Open the app on an iOS device (2 times; open close, open again allowing the app to update to the latest version if you have previously opened it).

 

13) Use the + icon to navigate to the edit screen

IMG_9686.PNG

 

14) Select the t1 toggle and turn it on.  Note that everything looks as it should at this point.

IMG_9685.PNG

15) Select the t1 toggle and turn it off

IMG_9686.PNG

 

16) Select the t1 toggle and turn it on again.  At this point my screenshot may be off.  I believe I missed a shot where it would have been missing the t2 toggle.  However, note from this one that t3, t4, and t5 are missing.  For your view all may be missing.  Realizing I missed a screenshot, I repeated steps for t3 to correct it.  You will see later shots showing this.

IMG_9688.PNG

 

17) Edit the app again, change the Height property of the t2 and t3 data cards to

122


fixheight.pngfixt3height.png

 

18) Save and publish again.  Close and reopen the app on an iOS device 2 times.  Repeat steps to toggle t1 on, off and on again.  Note that both t2 and t3 are fixed now.  Repeat steps to fix t4 and t5 if you like.

IMG_9689.PNG

 

Commentary:  I believe the root of the problem is that the default Height of the toggle data card is in a conflicted state.  The formula bar says 50, the properties window says 122.  If you then change the X value of the toggle (which has references to its parent's Y and Height properties) and then afterwards change the X value of the label, followed by dragging the label's width around a bit, you will introduce the issue.  From there the issue occurrs on all of the other toggles that have the same visible formula.  I suspect using the drag width feature is changing another property that I did not notice / pick up on.  At this point the height of 50 (which is clearly to small) becomes and issue, causing the other toggles to be hidden.

 

Okay, so is this a bug?  Clearly I can fix the issue by addressing the height of the data cards (setting them to a value that is not less than the needed height).  However, I believe it is a bug for 2 reasons:

 

1) Previous render mode handled, showing the full card.  One could argue that the previous render mode had the bug and should have been cutting the card off 🐵

 

2) The default height clearly should match the actual height of the rendered card.  I did not pick heights of 50 and 122, these came from app creation (the bug is likely that the default height should probably have matched the property window).  It's not clear to me how these can be disconnected to begin with...

 

Hopefully that is enough detail for you to trace down the root cause.  Again, this issue only exists on the Improved App Rendering mode.  

 

Let me know if you need anything more,

Joey

 

 

mr-dang
Community Champion
Community Champion

Thanks for the very detailed steps and screenshots, @keathley. I've linked this to the same ticket BUG 3070219 and notified the team. I'll get back with any updates.

Microsoft Employee
@8bitclassroom
mr-dang
Community Champion
Community Champion

@keathley

Our team was not able to replicate this on iOS from your steps. It would help to know the exact model of your iOS device and its version.

 

Here's some more specifics:

Regarding the discrepancy in height values (50 vs 122), this is a bug in the properties panel. The value shown in the Advanced panel and formula bar is the desired value (50). The value shown in the properties panel is the actual value (122), which takes into account the autoheight of the Label. They should be the same (50) in all panels, even though the actual height is bigger.

 

For data cards that contain autoheight elements, the Height property is actually for minimum height.

 

Microsoft Employee
@8bitclassroom

@mr-dang This was witnessed on an iPhone 6 plus (model MKTY2LL/A) running 11.x, as well as 12.0.1 (updated today to try to resolve another issue).

 

Regarding the autoheight comment you made, I worked around the issue in my app by setting the height to each of the affected toggle's data cards to 112.  The issue is not present when I do this.

 

I would just note that when reproducing it in a new app myself, I had one try on the first toggle that did not produce the issue.  When I tried again on the 2nd toggle it did.  I questioned the order of my steps.  I ended up with feeling that you need to "move" the toggle before you move the label.  I tried documenting this in my steps, but if you followed the images instead of the text content you may have fallen into what I did on the first round.  And of course that could have had nothing to do with it lol.

 

thanks,

Joey

I wonder if it is a problem with the toggle control or the form. Have you tried with checkboxes instead of toggles? Both have the same functionality.

I reported this problem earlier this year in June and had no joy. I posted 2 posts and both where kind of ignored.

Post 1

Post 2

This is a general problem when working with "hidden" fields. It's really easy to replicate this bug. I've done it three times today using different SharePoint Lists and different iPhones. When I tested on a Windows Phone, the bug does not occur.

This is the process I went through to replicate this bug:

  1. Create a SharePoint List
  2. Create a few fields. They can be plain single line text fields.
  3. Go to PowerApps and create an App from the SharePoint List you created above and wait for it to generate the App.
  4. Go to the EditScreen and select the EditForm
  5. Reduce the size of the EditForm from the top of the screen so that you can add some buttonsEditScreen.PNG
  6. Create three buttons at the top called General, Status, Files. This is just an example. Any names will do.
  7. Enter the formula Set(tabSelect,"General") on each button's OnSelect property. Change the formula so that it correspondes with the button's name for the buttons, Status and Files.
  8. Expand the EditForm to show all the data cards.
  9. Set the Visible property of a few of the DataCards to If(tabSelect="General",true,false)
  10. Set the Visible property of a few of the DataCards to If(tabSelect="Status",true,false)
  11. Set the Visible property of a few of the DataCards to If(tabSelect="Files",true,false)
  12. Set the EditScreen's OnVisible property to Set(tabSelect,"General")

That's it! Nothing else needs to be done. Save and Publish. Check the App by running it in a browser. As you click on each button, the corresponding "hidden" fields will be made visible while others are made hidden. In it's basic format, this is how you would create the illusion of tabs in an standard EditForm.

Then run the App on an iPhone. The first time you go in, the fields show fine on the "General Tab". Press the Status or Files buttons and the data portion of the fields no longer show.

Here are some screenshots of the App on the iPhone. First screenshot is when you first go to the EditScreen. Second screenshot is once you press either the Status or Files button and then press the General button again.

 

When the EditScreen is first opened.When the EditScreen is first opened.Field Data no longer showingField Data no longer showing

As mentioned, if you go to the App Settings, Advanced Settings and turn off "Improve app rendering (final validation)" and save and publish the app. The problem goes away on an iPhone and the app works as expected.
I'm almost certain this is a bug.

Tested on

iPhone 8

iPhone PowerApps Version - 3.18103.21

iPhone iOS - 12.0.1 (16A404)

 

For backward compatibility, I also tested on

iPhone 6

iPhone PowerApps Version - 2.0.720

iPhone iOS - 10.3.3 (14G60)

Just got off the phone with Microsoft. They have confirmed that it's a bug and it's currently being reviewed.

The workaround that they have put in place is to use the setting under the App - App Settings, Advanced Settings, turn off "Improve app rendering (final validation)".

Thanks @eddyg for contributing to this!  Apprecite the follow up that it is being worked as a bug.

 

thanks,

Joey

Thanks @eddyg for the detailed steps. I am able to reproduce the bug now.

 

The cause is that the Form is not calculating the height of autoheight controls correctly. It uses the DataCard.Height property. When creating an app from a Sharepoint list, DataCard.Height is set to 50 by default, which is too short to show the entire contents of the card. Normally, DataCard.Height will be ignored if there are autoheight controls inside the card, but improved app rendering does not do this when card visiblity is changed.

 

The workaround at the moment is to set a larger value to DataCard.Height or a formula like DataCard.Height = DataCardValue.Height + DataCardKey.Height.

Thanks @tahoon.

 

Using this formula for the DataCard.Height seemed to have worked better for me:

ErrorMessage.Y+ErrorMessage.Height

 

At least I know I'm not going crazy :-).

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (4,375)