We have many lists and libraries inside our sharepoint online site collections, which have been customized, by doing these main actions:-
1. Adding custom scripts to the new and edit list forms using the "Script Editor" web part.
2. Hiding certain fields inside the New list form using powershell scripts.
fieldTitle = "SiteCreated"
$customfield = $Context.Site.RootWeb.Fields.GetByInternalNameOrTitle($fieldTitle)
$customfield.SetShowInEditForm($true)
$customfield.SetShowInNewForm($false)
$customfield.UpdateAndPushChanges($true)
now those customization were preserved even if we use the modern UI, as sharepoint will always render any new or edit list forms using the classic mode if we have customized the list forms using custom scripts. so in some scenarios where we only customize
the Edit list form, we can render the display form, new form and list views using modern UI while render the edit form using classic mode which is perfect. also the powershell script will affect the classic/modern UI out of the box which is perfect.
but recently i downloaded the sharepoint mobile app inside my iPhone, and i found those 3 sever issues, when i accessed the customized lists/libraries:-
1. the custom script and the power-shell scripts will not have any effect, where the new/edit forms will ignore the custom scripts and the power-shell scripts to hide certain field inside the New list form.
2. I have a managed metadata field >> and this field will be shown as read-only inside SP mobile app.
3. i have disabled attaching files inside the custom list settings>> but when add/edit items inside SP mobile app users can attach files to the items!!!
so can anyone advice how i can fix these issues? i do not mind prevent users from accessing these customized lists/libraries using mobile apps? as currently the behavioure of the sharepoint mobile app is not acceptable, as it will breach our business logic
(if it has not already breach it)...