Forum Discussion
SP2007 vs SPO 2013 View
- Feb 01, 2018
Update:
1) All "*.aspx" pages can be found under "https://<<relative site url>>/Forms/<<pagename>>.aspx"
- What I observed is these .aspx pages are used for classic experience. So it's good to keep minimum list view web part (XSLTListViewWebPart) to work properly
- These .aspx pages are created for each corresponding view. So deleting these pages mean we are deleting the View or vice versa.
2) Some of the Web Parts from SP 2007 that are migrated into SPO are in hidden status. These web parts didn't appear even in "Edit Page" mode. The trick is to add "Contents=1" after the "pagename.aspx?" to list all web parts of the page including the hidden one. It provides the option to select the web part and delete it. After removing them, the view returned to Modern Experience.
3) For a given document library/List, don't alter the default view page "AllItems.aspx" or "All Documents" view. Not sure whether it is discouraged to set some other view as Default. The views work perfectly fine in a huge list if "All Documents" is default page. Noticed a new thing in last few weeks that the page displays "Tap here to load more items" if the filter is not returning any files within 5000 limit. I assume it goes back by created/modified date by 5000 items at a time.
What are you using to migrate your content?
Have you considered using a migration tool like Sharegate? It will migrate all of your views and much much more.
- Dec 16, 2017Totally agree here with Eric. To manage the migration os such a huge list you should be using (I think that's the case) a third party migration tool
- Deenadayalan VDec 17, 2017Brass Contributor
Thanks for the response. My question is misunderstood. My question is not about how to migrate. After migration (yes, using a tool) where these SP 2007 web part pages land in SPO? How to access them via code?
- Eric AdlerDec 18, 2017Steel Contributor
Ha, wow, I misread that one. Sorry.
Honestly my understanding has always been that these pages are dynamic based on an XML blob that get's rendered upon request and stored in the content db. That's usually all a view is.
However, you can see them in SPD as .aspx pages. I created a view called whereAreYou and you can see in the attached screen shot (arrow 3). Still pretty sure that is a façade.
I would check in to the SharePoint PnP or the Dev Center for code examples that set views.
You might also want to post this question in the SharePoint Dev area of the community.