Skip to content

Commit 2f5d4ca

Browse files
committed
small fix
1 parent 9f5a983 commit 2f5d4ca

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/transform/modernize-userinterface-lists-and-libraries.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,13 @@ An incompatible customization is the most common reason for lists not rendering
4747
- The use of JSLink
4848
- The use of a user custom action that embeds JavaScript
4949

50-
To fix these blockers, you can either remove the customization (in case it's not business-relevant anymore) or create an alternative solution. For more information, see [Modernize customizations](modernize-customizations.md).
50+
To fix these blockers, you can either remove the customization (in case it's not business-relevant anymore) or create an alternative solution. For more information on building customizations that are compatible with the modern list and library experience see the [Modernize customizations](modernize-customizations.md) article. Since JSLink at web part level does prevent the page from using the modern list and library experience you need to remove this configuration. You can do this manually by bringing the page in edit mode via appending `?ToolPaneView=2&pagemode=edit` to the page URL and then updating the web part properties. To programmatically do this you can use get the web part via the `LimitedWebPartManager` class and then update the respective properties as shown in below snippet. You can combine this snippet with the more complete code shown later on this page to get a full solution.
51+
52+
```csharp
53+
webPart.Properties["JSLink"] = "";
54+
webPart.SaveWebPartChanges();
55+
cc.ExecuteQuery();
56+
```
5157

5258
### Existence of certain field types
5359

0 commit comments

Comments
 (0)