Skip to main content

Office 365 and PnP-PowerShell 2013 : Fields

Now the time to learn about the Fields or so called SharePoint “List” and “Content Type” Columns. 

The below mentioned cmdlets lets you create and remove the Fields to content type and directly to the SharePoint List. 




CmdletDescription
Add‑PnPFieldAdds a field to a list or as a site column
Get‑PnPFieldReturns a field from a list or site
Remove‑PnPFieldRemoves a field from a list or a site
Add‑PnPFieldFromXmlAdds a field to a list or as a site column based upon a CAML/XML field definition
Add‑PnPTaxonomyFieldAdds a taxonomy field to a list or as a site column.
If you want to take a better control over to the list columns better way to design and developed via “Add‑PnPFieldFromXml” method. As this method you only need to work on the XML part for this you need to invest your time to check CAML Documentation.




So I am going use “Add‑PnPFieldFromXml” cmdlets to create the utility to create the columns and configuration done via CSV file.
So before going ahead you need to know about the basic understanding about the CAML  Documentation.




Let’s quickly jump in to the example. This Utility is tried and tested please feel free if you face any issue related to this scripts. 

In this example, I am going to create the CSV files called "SiteColumns.CSV" in which I will provide you all the type of the columns example. 

  1. Choice
  2. Text
  3. User
  4. DateTime
  5. Boolean
  6. Number
  7. Note
  8. Currency
  9. LookupMulti



Also Please check the all the columns closely before going ahead to do any modification mostly please keep check the "optional" columns in the csv which is used to enter the optional data into the Field Xml like make the column to enter only datetime data, or make it required. Also the "optional" field is separated by  Pipe "|" symbol to enter the multiple values inside the tags. Also for example if you set the default value to the choice column.



Here is the Source code. Hope you like it and please let me know your issue and feedback about this. 





Comments

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis