We have a development SharePoint online site >> and its lists' forms have been customized using Nintex forms. Now we are on the stage of converting the Nintex forms to Power Apps. and we have 2 approaches to follow:-
- Customizing the SharePoint list forms using Power Apps, as follow:-
- Build a Standalone Canvas App, and use the build-in SharePoint lists' forms as is.
but we have the following issues:-
If we follow the first approach >> then when we finalize the development work on the development site and we need to create the live site >> then we will have to rebuild the customized forms, as currently there is not a way to export and import the customized Power Apps forms.
If we follow the second approach to be able to import and export the power apps from dev to live >> then users can still interact with the SharePoint lists using the SharePoint built-in forms, so any business logic implemented inside Power Apps (like cascading drop-downs, hiding fields, make fields as disabled) can be over passed by users when they create or edit list items using SharePoint built-in forms.
so how we can fix these issues? for example is this scenario achievable:-
To build power apps standalone apps >> so we can Export and Import them between different sites >> then inside the standalone app to define deep linking >> and finally , to define a redirect from SharePoint list to the standalone app. So if the user click on edit link inside SharePoint list view Or click on the edit button or click on New button, as follow:-
to redirect the users to the standalone power app instead of opening the built-in forms? is this approach achievable? if not then which approach of the above 2 approaches we should follow? and why?
Thanks in advance for any help.