Start Sharepoint itemupdating event

Sharepoint itemupdating event

Step 2 The Share Point Customization Wizard will come up as shown below.

So, enough of theory, let’s get hands on and build our own Event Receiver feature for Share Point 2010.

The solution is to manually set up the Pages library the same way Microsoft does by adding two event receivers, changing some columns from hidden to visible and adding them to the default view.

Note: This example uses commands from the Office Dev Pn P Power Shell library, ex. I recommend using this library for working this Power Shell and Share Point (both Online and On-Premises).

You can also change the deployment scope here from Web to farm etc. I’ll cover xsl transforms and more customizations in a future article. This class will save our transformed html as a file into a given sharepoint library.

For now we’ll use the quick-and-dirty ‘code transformation’. This class also has a single method Save File To Library that takes the site url, library name, html content and file name as parameters.

Scheduling is easily enabled through the web interface when configuring the “Pages” library, but when deploying solutions using Power Shell, this must be automated as part of the configuration.

Unfortunately, as many other sources also state, this is not directly supported in the Client Side API (CSOM).

If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.