SPTransformator Sneak Peek: Feature focus dependencies

3 min read

Mission Control: Prepare to receive the latest news – a brand new version of SPTransformator is coming soon!

The Eagle has landed… we need look no further than the Apollo 11 space mission to see how dependable relationships are built to achieve ground breaking feats – I know, I might be stretching a bit, but we’re here with our new SPTransfromator blog series feature focus dependencies.

In the third blog post of this series we took a closer look at large lists but now dive into yet another new top feature!

Feature Highlight: Dependencies

SharePoint artifacts can be dependent on each other, and whether we’re talking about content types, or custom field types, we use the term dependencies to identify the behavior between artifacts. So, to understand what we define as dependencies in relation to SPTransformator, we need to talk quickly about artifacts and their relationship within SharePoint.

Whether you are adding a column directly to a list, or using a site column instead, they both have their advantages and disadvantages. For example, creating columns in a list can be a simple process, but they have limitations in the sense that you can only use the column within that list, and you cannot reuse the column in other lists. Using a site column instead can, for instance, help you greatly in enhancing your search results: the column definition is the same everywhere within your site collection, regardless of where you use it. Using a so-called site column at site level will introduce a dependency of the list to that column. If you provision the list using CSOM or REST, and the site column is not present, the list will not work.

SPTransformator identifies dependencies between artifacts and visualizes them for the development team to make decisions based on their SharePoint solutions. For instance, SPTransformator might identify custom field types as a chain of dependencies, and you may want to steer away from them as they are gradually becoming incompatible with SharePoint, and although they are currently accepted by current versions, possible future versions might not support them. Crucially, they are 100% non-compliant with SharePoint Online. From the information that SPTransformator provides, it draws a picture so you can better understand the make-up of your solutions.

As with all features highlighted in this blog series so far, automatic is once again a key word, and SPTransformator is taking away the need to manually identify dependencies within your SharePoint environment by automating processes for you – the manual process takes a lot of time and it is very likely to miss dependencies. In a nutshell, SPTransformator saves you and your company time and money.

SPTransformator is free and provides an initial analysis of SharePoint Full-Trust Farm solutions. Further actions, like automated assessments and code transformation, can be unlocked by purchasing credits. If you would like to sign up and receive SPTransformator latest version on release day, please click the button below and fill in your contact details.


Erwin van Hunen

Erwin is Rencore's Chief Technology Officer. He is a long-time Microsoft MVP, Microsoft Certified Master, and Microsoft Certified Solutions Master. He is a core member of the Microsoft 365 Patterns and Practices team, helping developers worldwide with code samples, scenarios, solutions, and guidance to successfully implement customizations for SharePoint and SharePoint Online. Erwin is speaking regularly at tech conferences around the world.