App Loads but no create or edit screen available after 4 revolutions of the loading icon- 3.18114.16

[Anonymous]

Hi,

I know this topic keeps rearing its head.

I have version 3.18114.16. 

I customised the create and edit screens from the bog standard.

I have 192 columns - of which 166 are radio buttons.

In the live browser all screens load when play is chosen.

Data source is a SharePoint 365 site.

In the mobile app from cell phone, only the Gallery and Display screens work wonderfully.

When I select create new or even try to edit an existing record, I get the loading icon revolving 4 times then it goes back to the Gallery screen - will not pass go.

Gallery

Display

Load Icon

I have cleared the cache and followed other advise - and still canot pass go using the mobile version.

I have even tried splitting the create and edit into two distinct screens (keep it simple less VBA than if I had one screen to it all) and on call neither load - will not pass go - does on the live play in the browser. I know the column count is ok for performance - I do not have more than 500 records - only 3 test ones.

Is it the radio buttons?

And the saddest part - I am trying to replace an InfoPath form.

Any help advise, moral suport welcome. 

Recreate app - this is a recreation.

[Anonymous]

Futher to my delema,

I chose classic mode - and surprise surprise the create screen worked.

Edit screen however still strikes out after 4 revolutions of the start icon.

So there is promise - only classic mode isn't around for much longer.

mmmmmmmmmmmm - a bug me thinks .

[v-xida-msft]

Hi @Anonymous,

I have made a test on my side, and don't have the issue that you mentioned.

I think this issue may be related to the large number of columns you enabled within the Edit form of your app. The large nunber of columns enabled wthin the Edit form or the large number controls you add within your app would consume large CPU resources and memory of your mobile device.

Please consider take a try to enable the "Explicit column selection" option within Advanced settings of App settings of your app, and turn off/disable the "Improved app rendering (final validation)" option, then re-publish your app, check if the issue is solved.

Please also consider reduce the number of columns enabled within Edit form of your app, then check if the issue still exists.

Best regards,

Kris

[Anonymous]

Thank you.

I have set advanced features  per attached photos.

Still same situation cannot render edit screen as it is.

Sooooo  to many radio buttons for the app to render in edit mode.

Each column has a radio button attched to it. To allow for three possible answers - "Yes" , "No", "N/A", or "Safe"," At Risk",  "N/A".

Radio button as I feel easier and simpler - keeps things simple.

So - if edit required need to be able to sinply change things.

Question: can I split the edit screen into two halves - complete first half then direct to second half screen to finish.

Upload corections would work as if two screens were one - merge?

[Anonymous]

So further to my learning curve - 212 columns (160 radio buttons)  - I had to split the edit form into six forms with the following number of controls on each form to get the thing to render.

1 = 54

2 = 33

3 =33

4 = 32

5 = 21

6 = 39

Why the odd numbers of controls on each form baffles me - but the forms will render on the cell phone and transition.

Why 54 controls on the first form and only 33 on the second - dohhhhhh - but it is what it is.  Must be something to do with the radio button count on each form also?

Oh and finally came to the conclusion that the cell phone processor and memory are the limiting factor followed by network speed and of course the cloud.

Dang if I dont have an app on my mobile that will geo locate and allow 200 fields to render on one form, and allow a photo for each question, and allow emailing and converting to pdf to send all in the one app - and here I have a p[owerapp that will not render even 55 controls and has to be 54.

It is what it is...