Tabs workaround no longer working in latest iPhone App

[eddyg]

The Tab / Tabs wokaround using DataCard visible properties has stopped working on the iPhone Powerapps App.

It continues to work in the browser without an issue and works on Windows Mobile. Haven't tested on Android.

When you first land on the screen, the fields under the Tab show correctly as they should. If you select another Tab and then move back to the original Tab, the fields no longer show correctly and you can't see the data or interact with the data field.

Screenshots attached show when you first enter a Tab (looks correct) and then when you move away and return (unworkable).

Nothing changed in the App and this was all working before. As a test, I built an App from scratch, standard App from SharePoint list and went to the EditForm screen and added the Tab workaround. This confirmed right away that the workaround has stopped fuctioning in the iPhone App.

Please can someone confirm that this is the case?

[v-monli-msft]

Hi @eddyg,

The workaround you mentioned, was it created by following steps in this blog?

https://powerapps.microsoft.com/en-us/blog/part-2-of-tabbed-user-interface-mobile-version/

If so, I will try to create the same one and try to reproduce your issue.

Regards,

Mona

[eddyg]

Hi Mona,

No, not like that. That is "moving" between screens.

The tabs I'm referring to will display different fields from the same record. If you have an Edit Form to edit a SharePoint item and if you have many fields that need editing, it means that you will have one screen that you have to scroll down quite a bit to fill out all fields.

The Tab approach means that you can have a set of fields in each tab and you can eliminate scrolling altogether. Here is an example:

Here is a blog done by @WonderLaura  showing you the process. She has done this in a SharePoint Powerapps Form but the principle is the same.

If you create this as an app in PowerApps, you will see that it works fine in the browser. As soon as you run it on the iPhone Powerapps App, it does not work. I suspect there is something wrong with the iPhone App as of the latest release ver 3.18063.36.

I have used this in the past and it has working without issues on the iPhone App.

If you can test from your side and tell me if you have the same issue on the iPhone App, that would be awesome. If yours works, please tell me what version you are running on the iPhone.

Regards,

Eddy

[eddyg]

Using the Visible Property to hide and show a DataCard in an EditForm will display incorrectly on an iPhone.

This works fine in a browser.

This is a known bug and confirmed by Microsoft.

Current workaround is:

Go to App Settings, Advanced Settings and turn off "Improve app rendering (final validation)"

Another workaround is:

Manually set the Height Property for the DataCard either using a formula or hardcoded.

I set it to the following formula and it worked for me - ErrorMessage.Y+ErrorMessage.Height

[Anonymous]

Hi All, I've also found this issue whilst creating tabs within both detailforms and Editforms(Visible property of entry dependant on context of tab) I tried the solutions mentioned below including using the improved app rendering setting, and by eddyG but with no luck. The formula doesn't work with my DB, and manually setting the height property made no difference. Its an odd behaviour, that at points i also experienced in the web browse (attached), where it would seem all parameters that are on screen when the page are originally loaded are OK, but then when the tabs are clicked back and forth (visible changes true/false) the entries are never displayed again correctly. The best way i can describe it is; When the screen initially loads the values they appear to open and drop down from the top of the screen, but on the OS platform this on partially happens when the entry goes from visible false -> True. I've remade my app with the Tabs hidden, but it would be nice to categorise the data n the screen #lessscrolling

[eddyg · Accepted solution]

Hi jackferryman, This thread is old and there is a thread with far more detail around this topic. If you look at the bottom of page 3 you will find my detailed workaround on how I got this to work correctly. Having said that, apparently a fix was scheduled to come out in mid Jan 2019. Lets see if that happens or not. In the meanwhile if you would like to use my workaround, here is the link to that discussion: https://powerusers.microsoft.com/t5/General-Discussion/Toggle-Visibility-BUG-In-Improved-App-Renderi...

[eddyg]

This is now fixed since the 21st of Jan 2019. New rendering engine has been updated and rendering issues have been solved.

This seems to be working fine now with Global or Local variables. Can also use a single variable such as UpdateContext({tab: 1}) and use tab = 1 or tab = 2 as the Visible property on a field. In other words, you don't have to have 1 variable per visibility state.