cancel
Showing results for 
Search instead for 
Did you mean: 

PowerApps Custom Form working with classic experience

Currently the PowerApps Custom Form in SharePoint will only work if the modern experience is enabled. If the user clicks the "Return to classic SharePoint" in the browser then the out of the box SharePoint list form is used instead of the PowerApps Custom Form. If a PowerApps Custom Form is being used in a list then the Classic toggle link shouldn't prevent the custom form from being displayed.

Status: Completed

It is now possible to play a PowerApps Custom Form from the classic experience (if the form has been customized prior to the user switching to classic).

 

Adding @emmac who will be working to improve these experiences. She and I were able to run a form from classic which had previously been customized by a maker using the modern experience to confirm this change.

 

Thank you for your patience as we continue to evolve this experience,

Audrie

 

Comments
Power Automate
Status changed to: Declined

Currently the PowerApps integration with SharePoint is only available on the modern experience. Although this has been requested before, the classic experience architecture does not allow for this service. 

 

You may have noted that you now have the "go to classic experience" and "return to modern experience" link on the lower right of the page on SharePoint whenever you need to bouce back and forth between the two.

 

Thank you for your patience as we grow these experiences. Your continued support and feedback are highly appreciated.

 

Audrie

Super User

@Audrie-MSFT,

If the PowerApps can't work in the classic experience then maybe the solution is to have the list honor the List Settings > Advance Settings > List Experience setting. If it is set to “New experience” then the view should use the modern experience no matter what browser toggle link (“Return to Classic SharePoint” or “Exit classic experience”) is set to. Otherwise, creating PowerApps custom forms loses its appeal because all the business logic and functionally that a site owner created in the custom form could easily be bypassed (on accident or on purpose) by switching to the classic experience.

Advocate I

This presents a challenge for linking directly to a NewForm from outside of the associated list. Example, a link to a reimbursement request form on a company home page. Ideally, the link would open the form itself, without the user having to go into the list and click New from the toolbar. If they are in Classic mode, they would get the OOB NewForm, but since they are in the form vs. the list, they would not see the "Exit Classic View" toggle. Somehow the user would need to 1) know the OOB form is not the intented experience, and then 2) navigate to a list so the can exit classic view.

Power Automate

@Jeff_Thorpe@DannaT - Thank you for your inputs. Adding our partner on the SharePoint team to comment on the feasibility of this suggestion for the classic experience.

 

@KeremY: Please review suggestions and add your thoughts. Thank you.

 

We appreciate your continued feedback and suggestions. Thank you,

Audrie

Anonymous
Not applicable

I came across this post and since I also have sites with the classic and sites with the new experience I would like to know if @KeremY already had time to look at this?

As an extra related question could someone please tell me what happens in the following case:
I have a classic site with an Infopath form and I switch to the new experience and create a new form there with PowerApps. When I than switch back to the classic view what form will the users get? The Infopath form or the OOTB form?

 

Thanks,

Clarinus

New Member

I have more of a two fold problem with not being able to use PowerApps in classic view.

 

Changing a list from Classic to New using List Settings -> Advance Settings doesn't work.  I have to use the Link on the Quick Launch?

Capture.PNG

When I did click on the "Exit Classic Experience" I could see all the PowerApps features fine.  But then going back to the home page it was still in the classic and not the new experience.  So now I'm getting whiplash with what the site looks like.  I could go back to the classic experience on the list and create in InfoPath form, but with that being depreciated why would I waste my time.  I need a way that the expeience is universal and to the users needs, whether that's in classic or new, so I need PowerApps to be availble in both, otherwise what's the point of PowerApps if it doesn't work 100% of the time?

Power Automate
Status changed to: Completed

It is now possible to play a PowerApps Custom Form from the classic experience (if the form has been customized prior to the user switching to classic).

 

Adding @emmac who will be working to improve these experiences. She and I were able to run a form from classic which had previously been customized by a maker using the modern experience to confirm this change.

 

Thank you for your patience as we continue to evolve this experience,

Audrie

 

Frequent Visitor

Hi @Audrie-MSFT

 

This doesn't seem to work form me, we have a list form customised in powerapps but everytime we go back to classic view the form will only open as the old OOTB form. How are you opening powerapps from classic?

 

Thanks

Lucy

 

Frequent Visitor

Worked it out - if you have forms set to launch in dialog it still opens the old form, switching that to No allows the new powerapps forms to open instead. 

 

Thanks!

Frequent Visitor

Hi,

 

As per my knowledge, currently we have Calendar list template only in classic experience and there is no option to switch it to new experience. Is there a way to customize the calendar form using PowerApps?

 

Thank you!