You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/solution-guidance/portal-performance.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Performance guidance for SharePoint Online portals
3
3
description: Describes the evolution of the SharePoint Online customization model, general performance guidelines for client-side web applications, and the Client-Side Data Access Layer (DAL) Framework.
4
-
ms.date: 42/12/2019
4
+
ms.date: 06/19/2019
5
5
localization_priority: Priority
6
6
---
7
7
@@ -143,7 +143,7 @@ Capture critical information application metrics such as:
143
143
144
144
Establish an objective performance baseline for your client-side web application, and use that baseline to validate/tune your initial design decisions. After the application has been deployed, monitor ongoing performance and use the metrics to identify and resolve any issues that might arise.
145
145
146
-
Consider using [Azure Application Insights](https://azure.microsoft.com/en-us/blog/understand-your-sharepoint-usage-with-application-insights-2/), which provides a JavaScript module that makes it easy to add telemetry to any client-side web application. You can also build your own telemetry back-end service, but do know that we don't recommend storing the telemetry data in SharePoint because it negatively impacts your portal performance.
146
+
Consider using [Azure Application Insights](https://azure.microsoft.com/blog/understand-your-sharepoint-usage-with-application-insights-2/), which provides a JavaScript module that makes it easy to add telemetry to any client-side web application. You can also build your own telemetry back-end service, but do know that we don't recommend storing the telemetry data in SharePoint because it negatively impacts your portal performance.
147
147
148
148
<aname="bk_clientBrowser"> </a>
149
149
@@ -161,7 +161,7 @@ When dealing with a legacy browser constraint:
161
161
- Degrade/disable modern functionality in the new application when a legacy browser is detected at run-time.
162
162
- Consider using the legacy browser only for the constrained LOB application; use a modern browser for everything else, including the new client-side web applications.
163
163
164
-
For the latest Office 365 browser requirements, see [Which browsers work with Office Online](https://support.office.com/en-us/article/which-browsers-work-with-office-online-ad1303e0-a318-47aa-b409-d3a5eb44e452?ui=en-US&rs=en-US&ad=US).
164
+
For the latest Office 365 browser requirements, see [Which browsers work with Office Online](https://support.office.com/article/which-browsers-work-with-office-online-ad1303e0-a318-47aa-b409-d3a5eb44e452).
165
165
166
166
<aname="bk_clientEnvironment"> </a>
167
167
@@ -173,7 +173,7 @@ In the ideal scenario, the client environment is comprised of up-to-date client
173
173
174
174
As such, tailor the initial design of your client-side web application to adhere to the present constraints, with a plan to take advantage of client environment improvements as they are deployed. In such a scenario, you will eventually encounter a mix of client machines, so ensure that your client-side web application can detect client capabilities at run-time and adjust its behavior accordingly.
175
175
176
-
For guidance about network performance planning, see [Network planning and performance tuning for Office 365](https://support.office.com/en-us/article/Network-planning-and-performance-tuning-for-Office-365-e5f1228c-da3c-4654-bf16-d163daee8848).
176
+
For guidance about network performance planning, see [Network planning and performance tuning for Office 365](https://support.office.com/article/Network-planning-and-performance-tuning-for-Office-365-e5f1228c-da3c-4654-bf16-d163daee8848).
177
177
178
178
<aname="bk_dataRequestPatterns"> </a>
179
179
@@ -196,7 +196,7 @@ The proper management of client-side data request traffic is critical to the per
196
196
- For static content, or content that is updated infrequently, like site navigation, consider writing this content to a JSON file and serving it from a CDN.
197
197
- To reduce costs at the middle-tier, clients can also cache the responses to LocalStorage.
198
198
199
-
For additional information, see [Caching](https://docs.microsoft.com/en-us/azure/architecture/best-practices/caching).
199
+
For additional information, see [Caching](https://docs.microsoft.com/azure/architecture/best-practices/caching).
200
200
201
201
#### Call the server (or other back-end data source) only when a cache miss occurs
202
202
@@ -261,7 +261,7 @@ In general, use SharePoint REST APIs for client-side data requests. When perform
261
261
262
262
- The SharePoint client library allows a developer to specify the fields needed for their application and return only this data. This reduces costs at all layers.
263
263
264
-
For code samples demonstrating this technique, please see [Complete basic operations using SharePoint client library code](https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code#retrieve-only-selected-properties-of-a-website)
264
+
For code samples demonstrating this technique, please see [Complete basic operations using SharePoint client library code](https://docs.microsoft.com/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code#retrieve-only-selected-properties-of-a-website)
265
265
266
266
#### Be mindful of aggregate request volumes
267
267
@@ -325,7 +325,7 @@ A Content Delivery Network (CDN) is a geo-dispersed network that allows an end-u
325
325
- Leverage existing CDNs to deliver third-party client-side frameworks (for example, jQuery, Bootstrap, Knockout, AJAX).
326
326
327
327
- Consider using a CDN to deliver your custom resource files:
- SharePoint Portal Style Library (default option when a CDN is not used)
331
331
@@ -483,7 +483,7 @@ The logical architecture of the Data Access Layer (DAL) Framework includes the f
483
483
484
484
## See also
485
485
486
-
-[Introduction to performance tuning for SharePoint Online](https://support.office.com/en-US/article/Introduction-to-performance-tuning-for-SharePoint-Online-81c4be5f-327e-435d-a568-526d68cffef0)
-[Introduction to performance tuning for SharePoint Online](https://support.office.com/article/Introduction-to-performance-tuning-for-SharePoint-Online-81c4be5f-327e-435d-a568-526d68cffef0)
-[Learn how to build a fast, responsive SharePoint portal in SharePoint Online](https://channel9.msdn.com/Events/Ignite/2016/BRK3026) (Channel 9 video)
Copy file name to clipboardExpand all lines: docs/transform/modernize-userinterface-lists-and-libraries-scanner.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Analyze and use the scanner data
3
3
description: Understand and process the scanner results to help your sites to get the most out of the modern list and library experience
4
-
ms.date: 21/06/2018
4
+
ms.date: 06/21/2018
5
5
ms.prod: sharepoint
6
6
localization_priority: Normal
7
7
---
@@ -22,7 +22,7 @@ The filtered data is then presented in a number of charts:
22
22
23
23
## Understand which sites you can "fix" to make them work using the modern list and library user interface
24
24
25
-
Apply the following filter and confirm the "Only blocked due OOB reason(s)" shows only FALSE. Lists are marked as blocked by OOB reason if their list template is not yet built to present itself using the modern user interface. See [List templates available in the modern user interface](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-lists-and-libraries#list-templates-available-in-the-modern-user-interface) to get a complete list of list templates that are supported.
25
+
Apply the following filter and confirm the "Only blocked due OOB reason(s)" shows only FALSE. Lists are marked as blocked by OOB reason if their list template is not yet built to present itself using the modern user interface. See [List templates available in the modern user interface](https://docs.microsoft.com/sharepoint/dev/transform/modernize-userinterface-lists-and-libraries#list-templates-available-in-the-modern-user-interface) to get a complete list of list templates that are supported.
26
26
27
27
Filter | Validation
28
28
---------|----------
@@ -39,7 +39,7 @@ The render type results indicate the **key** reason why a list is not rendering
39
39
List page render type | Remediation steps
40
40
---------|----------
41
41
**MultipeWebPart** | Lists are not showing up in modern because on their default view page there’s more than one web part. By default a list view page has only one XSLTListView web part. To remediate this you need to ensure there’s only the default XSLTListView web part on the list default view page (AllItems.aspx). You can programmatically do this using the LimitedWebPartManager API’s.
42
-
**JSLinkCustomization** | List are not showing up in modern because they’re using JSLink to customize the list rendering. To remediate this you need to remove the JSLink customization at web part level. JSLink at field level is not blocking the list be is ignored in the modern experience. See the [Modernize customizations](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-customizations) article for guidance on how to build modern alternatives. Also note that you can use the additional data like the base template chart to get a view on which list templates use JSLink and use the JSLink graphs to understand whether it's JSLink defined at web part or field level.
43
-
**XslLinkCustomization** | Lists are not showing up in modern because they’re using XslLink to customize the list rendering. To remediate this you need to remove the XslLink customizations. See the [Modernize customizations](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-customizations) article for guidance on how to build modern alternatives.
44
-
**WebSettingsOff** or **SiteSettingsOff** | Lists are not showing up in modern because at web or site level modern list rendering has been disabled. To remediate this you need to disable the site or web level modern list and library blocking feature. See the [Maximize use of modern lists and libraries](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-lists-and-libraries) article to learn more.
45
-
**ListSettingsOff** | Lists are not showing up in modern because modern was disabled at list level. To remediate this you need to set the list experience to Auto or NewExperience. See the [Maximize use of modern lists and libraries](https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-lists-and-libraries) article to learn more.
42
+
**JSLinkCustomization** | List are not showing up in modern because they’re using JSLink to customize the list rendering. To remediate this you need to remove the JSLink customization at web part level. JSLink at field level is not blocking the list be is ignored in the modern experience. See the [Modernize customizations](https://docs.microsoft.com/sharepoint/dev/transform/modernize-customizations) article for guidance on how to build modern alternatives. Also note that you can use the additional data like the base template chart to get a view on which list templates use JSLink and use the JSLink graphs to understand whether it's JSLink defined at web part or field level.
43
+
**XslLinkCustomization** | Lists are not showing up in modern because they’re using XslLink to customize the list rendering. To remediate this you need to remove the XslLink customizations. See the [Modernize customizations](https://docs.microsoft.com/sharepoint/dev/transform/modernize-customizations) article for guidance on how to build modern alternatives.
44
+
**WebSettingsOff** or **SiteSettingsOff** | Lists are not showing up in modern because at web or site level modern list rendering has been disabled. To remediate this you need to disable the site or web level modern list and library blocking feature. See the [Maximize use of modern lists and libraries](https://docs.microsoft.com/sharepoint/dev/transform/modernize-userinterface-lists-and-libraries) article to learn more.
45
+
**ListSettingsOff** | Lists are not showing up in modern because modern was disabled at list level. To remediate this you need to set the list experience to Auto or NewExperience. See the [Maximize use of modern lists and libraries](https://docs.microsoft.com/sharepoint/dev/transform/modernize-userinterface-lists-and-libraries) article to learn more.
0 commit comments