Forum Discussion
SP2007 vs SPO 2013 View
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.
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.
Thanks for sharing your solution, that is a common problem with hidden web parts and the Content=1 technique has always been needed to find that issue.
