Customizing SharePoint forms using Power Apps Vs Building standalone apps? Can I have a hybrid appro

%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3155642%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3ECustomizing%20SharePoint%20forms%20using%20Power%20Apps%20Vs%20Building%20standalone%20apps%3F%20Can%20I%20have%20a%20hybrid%20appro%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3155642%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CP%3EWe%20have%20a%20development%20SharePoint%20online%20site%20%26gt%3B%26gt%3B%20and%20its%20lists'%20forms%20have%20been%20customized%20using%20Nintex%20forms.%20Now%20we%20are%20on%20the%20stage%20of%20converting%20the%20Nintex%20forms%20to%20Power%20Apps.%20and%20we%20have%202%20approaches%20to%20follow%3A-%26lt%3B%5C%2FP%26gt%3B%3COL%3E%3CLI%3E%3CP%3ECustomizing%20the%20SharePoint%20list%20forms%20using%20Power%20Apps.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2FLI%26gt%3B%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EBuild%20a%20Standalone%20Canvas%20App%2C%20and%20use%20the%20build-in%20SharePoint%20lists'%20forms%20as%20is.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2FLI%26gt%3B%26lt%3B%5C%2FOL%26gt%3B%3C%2FP%3E%3CP%3Ebut%20we%20have%20the%20following%20issues%3A-%26lt%3B%5C%2FP%26gt%3B%3COL%3E%3CLI%3E%3CP%3EIf%20we%20follow%20the%20first%20approach%20%26gt%3B%26gt%3B%20then%20when%20we%20finalize%20the%20development%20work%20on%20the%20development%20site%20and%20we%20need%20to%20create%20the%20live%20site%20%26gt%3B%26gt%3B%20then%20we%20will%20have%20to%20rebuild%20the%20customized%20forms%2C%20as%20currently%20there%20is%20not%20a%20way%20to%20export%20and%20import%20the%20customized%20Power%20Apps%20forms.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2FLI%26gt%3B%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EIf%20we%20follow%20the%20second%20approach%20to%20be%20able%20to%20import%20and%20export%20the%20power%20apps%20from%20dev%20to%20live%20%26gt%3B%26gt%3B%20then%20users%20can%20still%20interact%20with%20the%20SharePoint%20lists%20using%20the%20SharePoint%20built-in%20forms%2C%20so%20any%20business%20logic%20implemented%20inside%20Power%20Apps%20(like%20cascading%20drop-downs%2C%20hiding%20fields%2C%20make%20fields%20as%20disabled)%20can%20be%20over%20passed%20by%20users%20when%20they%20create%20or%20edit%20list%20items%20using%20SharePoint%20built-in%20forms.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2FLI%26gt%3B%26lt%3B%5C%2FOL%26gt%3B%3C%2FP%3E%3CP%3Eso%20how%20we%20can%20fix%20these%20issues%3F%20for%20example%20is%20this%20scenario%20achievable%3A-%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3ETo%20build%20a%20power%20app%20standalone%20%26gt%3B%26gt%3B%20so%20we%20can%20Export%20and%20Import%20them%20between%20different%20sites%20%26gt%3B%26gt%3B%20then%20inside%20the%20standalone%20app%20to%20define%20deep%20linking%20%26gt%3B%26gt%3B%20and%20finally%20%2C%20to%20define%20a%20redirect%20from%20SharePoint%20list%20to%20the%20standalone%20app.%20So%20if%20the%20user%20click%20on%20edit%20link%20inside%20SharePoint%20list%20view%20Or%20click%20on%20the%20edit%20button%20%2C%20as%20follow%3A-%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CDIV%20class%3D%22%5C%26quot%3B%5C%26quot%3B%22%3E%26nbsp%3B%26lt%3B%5C%2FDIV%26gt%3B%3CP%3E%3CSPAN%20class%3D%22%5C%26quot%3Blia-inline-image-display-wrapper%22%20lia-image-align-inline%3D%22%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fgxcuf89792%2F%5C%26quot%3Bhttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F347371i2E0A60AFD0099BB9%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%5C%26quot%3B%22%20role%3D%22%5C%26quot%3Bbutton%5C%26quot%3B%22%20title%3D%22edit2.png%22%20alt%3D%22%5C%26quot%3Bedit2.png%5C%26quot%3B%22%20%2F%3E%26lt%3B%5C%2Fspan%26gt%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3Eto%20redirect%20the%20users%20to%20the%20standalone%20power%20app%20instead%20of%20opening%20the%20built-in%20forms%3F%20is%20this%20approach%20achievable%3F%20if%20not%20then%20which%20approach%20of%20the%20above%202%20approaches%20we%20should%20follow%3F%20and%20why%3F%26lt%3B%5C%2FP%26gt%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20help.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2Flingo-body%26gt%3B%3CLINGO-LABS%20id%3D%22%5C%26quot%3Blingo-labs-3155642%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CLINGO-LABEL%3EPermissions%26lt%3B%5C%2Flingo-label%26gt%3B%3CLINGO-LABEL%3ESharePoint%20Online%26lt%3B%5C%2Flingo-label%26gt%3B%26lt%3B%5C%2Flingo-labs%26gt%3B%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3C%2FP%3E%3C%2FDIV%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E
Valued Contributor

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:-

  1. Customizing the SharePoint list forms using Power Apps.

cus.png

  1. Build a Standalone Canvas App, and use the build-in SharePoint lists' forms as is.

but we have the following issues:-

  1. 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.

  2. 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 a power app standalone >> 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 , as follow:-

 

edit2.png

 

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.

4 Replies

@john john it is possible to export a customised form and the steps are described here.

 

We normally use the second approach and don't tell our staff where the datasource and list is as they don't need to know and therefore they don't create or edit items in the list directly, only via the app.

 

Rob
Los Gallardos
Intranet, SharePoint and Power Platform Manager (and classic 1967 Morris Traveller driver)

You can also set the list as hidden, using PowerShell. This way users cannot navigate to the list. As said above, use the list only as data source for users.

@RobElliott  Thanks for the reply, but i have these 3 points:-

 

1) but in our case we do not only use the SharePoint site to manage this list , we have news pages other lists, document libraries etc.. also hiding the list from the users, does not mean that they can investigate the url and access the source list. also we still want to benefit from SharePoint built-in features, so users can filter, search & export the list items... i do not want to reinvent the wheel inside the Power Apps i just want to customize the new,edit & view forms,.. that why i am asking this question.

 

2) Also for the approach to export/import power apps customized list forms.. i think this approach is not supported by Microsoft and is considered as a hack.. so officially MS does not support export/import customized power apps.

 

3) now since i asked this question, i came access this hybrid solution.. to create a standalone app and define deep linking on it , then customized the SharePoint forms using Power Apps, and inside the customized forms >> to just define a redirect to the standalone app... in this case we can export/import the standalone app + users can not use the SharePoint built-in forms.. so what do you think of this? any drawbacks i am unaware of ?

@Robert Schouten 

Thanks for the reply, but i have these 2 points:-

 

1) In our case we do not only use the SharePoint site to manage this list , we have news pages other lists, document libraries etc.. also hiding the list from the users, does not mean that they can investigate the url and access the source list. also we still want to benefit from SharePoint built-in features, so users can filter, search & export the list items... i do not want to reinvent the wheel inside the Power Apps i just want to customize the new,edit & view forms,.. that why i am asking this question.

 

2) now since i asked this question, i came access this hybrid solution.. to create a standalone app and define deep linking on it , then customized the SharePoint forms using Power Apps, and inside the customized forms >> to just define a redirect to the standalone app... in this case we can export/import the standalone app + users can not use the SharePoint built-in forms.. so what do you think of this? any drawbacks i am unaware of ?