Clients have asked me about visually improving documents to highlight content that contain sensitive information (for example) and then applying this change to columns in lists in all their groups (roughly 100 of them).
There is detailed documentation at docs.microsoft.com about how to create and apply the JSON formatting to a single column; but not so much about how to update existing columns with the API, so what and how should we get this done?
SharePoint Framework (SPFx) is new, lots to learn, explore and build new innovative modern features into SharePoint Modern Interfaces. With SPFX, you will notice you get a lot of extra files for configuration, libraries, temp code and compiled code; a lot of clutter and noise that’s not needed as part of the majority of development, it just gets in the way when I want to focus on the code! Huff….
The above example isn’t a large project but you can see lot more files that is necessary to SEE they are necessary for compilation, debugging etc. But really do we need to see these files?
One of many cool announcements from Microsoft Ignite 2017, was the introduction of SharePoint Modern Themes. The SharePoint team have now launched a way to customise themes, colours and the presentation of Modern Sites.
Typically, theming of sites has been randomly chosen at the time of creation making it very difficult to apply consistent branding across SharePoint sites and Office 365 groups.
In numerous projects I have seen development environments that resemble nothing like production. Only to result in a problematic transition through the ALM process, bugs caused by inconsistency, significant differences in SharePoint updates, configuration and even permissions.
I am not saying that you shouldn’t write your app to “expect a specific configuration” or to avoid best practices around handling configuration issues. However, to reduce issues down the line, as a minimum, environments should be setup with the following: