mikebedwards.com
SharePoint Solutions: May 2015
http://www.mikebedwards.com/2015_05_01_archive.html
Monday, 4 May 2015. New Item workflow fires before metadata. A common problem with document library workflows is the fact that often workflows set to fire 'on create' will fire too early. Consider this scenario - a workflow set to fire on a new item, checks a metadata value and takes some actions. In the lifecycle of the document - the user uploads a document, and is taken to the metadata screen. When the user completes the metadata, this changes the modified date, and the workflow continues:. A Blog I k...
mikebedwards.com
SharePoint Solutions: Powershell to reset publishing site collection
http://www.mikebedwards.com/2015/06/powershell-to-reset-publishing-site.html
Friday, 20 March 2015. Powershell to reset publishing site collection. When developing provisioning scripts, it's sometimes necessary to quickly provision a new site collection. Over. and. Over. This powershell script is for on-premise sharepoint 2013. It will delete a site collection, recreate it based on the publishing template, and also install any pre-requisite solutions that you may need (perhaps for content types). Add-PSSnapin "Microsoft.SharePoint.PowerShell". Site = "http:/ siteURL/sites/site".
mikebedwards.com
SharePoint Solutions: June 2015
http://www.mikebedwards.com/2015_06_01_archive.html
Saturday, 20 June 2015. SharePoint site property bag. The SharePoint site property bag is useful persistent storage. When creating JSOM scripts to provision site columns, content types etc, it can be useful to set and check a site property, to prevent provisioning code being executed more than once. Var clientContext= new SP.ClientContext.get current();. Var web = ctx.get site().get rootWeb();. Var props = web.get allProperties();. Propsset item("CustomMetaDataProvisioned", "True");. Thursday, 4 June 2015.
mikebedwards.com
SharePoint Solutions: January 2015
http://www.mikebedwards.com/2015_01_01_archive.html
Monday, 12 January 2015. Provisioning Metadata for Office 365. In a recent data management project, our provisioning options were limited. In this situation, provisioning metadata using power-shell was not an option as our permission levels were limited to Site Collection Administrator levels. No Power-shell. But, what happens if the feature is deactivated? With no event handlers on O365 to handle the 'clean up' process, what happens to list instances that use your content types? App model. Create an...
mikebedwards.com
SharePoint Solutions: SharePoint site property bag
http://www.mikebedwards.com/2015/07/sharepoint-site-property-bag.html
Saturday, 20 June 2015. SharePoint site property bag. The SharePoint site property bag is useful persistent storage. When creating JSOM scripts to provision site columns, content types etc, it can be useful to set and check a site property, to prevent provisioning code being executed more than once. Var clientContext= new SP.ClientContext.get current();. Var web = ctx.get site().get rootWeb();. Var props = web.get allProperties();. Propsset item("CustomMetaDataProvisioned", "True");. Bug with Custom Acti...
mikebedwards.com
SharePoint Solutions: March 2015
http://www.mikebedwards.com/2015_03_01_archive.html
Friday, 20 March 2015. Powershell to reset publishing site collection. When developing provisioning scripts, it's sometimes necessary to quickly provision a new site collection. Over. and. Over. This powershell script is for on-premise sharepoint 2013. It will delete a site collection, recreate it based on the publishing template, and also install any pre-requisite solutions that you may need (perhaps for content types). Add-PSSnapin "Microsoft.SharePoint.PowerShell". Site = "http:/ siteURL/sites/site".
mikebedwards.com
SharePoint Solutions: New Item workflow fires before metadata
http://www.mikebedwards.com/2015/06/new-item-workflow-fires-before-metadata.html
Monday, 4 May 2015. New Item workflow fires before metadata. A common problem with document library workflows is the fact that often workflows set to fire 'on create' will fire too early. Consider this scenario - a workflow set to fire on a new item, checks a metadata value and takes some actions. In the lifecycle of the document - the user uploads a document, and is taken to the metadata screen. When the user completes the metadata, this changes the modified date, and the workflow continues:. A Blog I k...
mikebedwards.com
SharePoint Solutions: July 2015
http://www.mikebedwards.com/2015_07_01_archive.html
Friday, 17 July 2015. A recent requirement was to create a custom form, with 'auto complete' functionality to encourage consistency in inputting data. A choice or lookup wasn't enough - the user required the flexibility to add new items. The OOTB 'allow auto fill' option for choices was also considered, but was not right either - the client wanted a specific input box with a drop down menu:. The solution was to combine the JQuery UI auto-complete feature with JSOM code and a list to store the values.
mikebedwards.com
SharePoint Solutions: Bug with Custom Action and Rights Mask?
http://www.mikebedwards.com/2015/06/bug-with-custom-action-and-rights-mask.html
Thursday, 4 June 2015. Bug with Custom Action and Rights Mask? In my current project I am using simple custom actions as a shortcut to starting a workflow. These custom actions are created with SharePoint Designer 2013 on a document library on office 365. Attribute of a custom action is supposed to show/hide that action, depending on the user's permission level. Detail of the available Rights Masks are here:. In this example, the custom actions are List Item Menu. Has anyone else observed this behavior?