SP_Field - New Resource Proposal

[kilasuit]

Description

Way to provision Site Columns in sites or webs

Proposed properties

Name
SchemaXml

Special considerations or limitations

[kilasuit]

Note: Use of SchemaXml and not all other properties that Field objects could take is to reduce the overhead in development and is often used cross on-premises & online with CSOM so should allow developers (or admins) to easily use this where they deem it fit to do so

[ykuijs]

Usually SharePointDsc focusses on infrastructure components, not content. This because editing content can result in a conflict with user edits (e.g. a user edits the title of a site and your desired state is no longer compliant). This resource is a grey area. I like your idea to also allow managing the Content Type Hub, which is something end users are unable to edit. That is why I think this resource is a valuable one.

[shurick81]

SharePointDsc should focus on providing "SharePoint platform", not some customized platform. By the way, there is another way of controlling lists and fields with declarative code: PnP provisioning templates.

[kilasuit]

To address comments - I totally get that in the majority of cases this seems like a counter intuitive resource to have that could perhaps be better served using other tooling - however there are use cases that I have seen used where this functionality would be incredibly useful and would negate needing to have additional tooling in place, as such I intend to in future raise a PR that implements this.

@ykuijs - If you can assign this to me I will work on implementing this in the next month or so.