Hot answers tagged

2

This is easy to do in workflows. However, your probably want 3 separate workflows. The one that runs on create would send the original email, then Wait for Status to equal Completed, then send another email. The other two would send alerts on changes in Assigned To and Due Date. Wait for Assigned To to not equal Assigned to, then send email. Wait for Due ...


1

Yes and no. You can't create true parent-child relationships, but you can make do depending on your requirements. If there will always be only one parent matching one or more children, you can write a workflow on the child list that will modify the parent item, then write a workflow on the parent item that runs when the item is changed.


1

If you created the multiple columns at the list level, you will need to add the new content type to the list first, and then add the columns to the third content type. That's why it is a good practice to always create columns and content types at the site level. (Site Settings -> Site Columns or Site Settings -> Site Content Types). That way, any columns ...


1

Using workflow you will not be able to validate which field got changed. Workflow kick starts after update and the previous data will be out of context. You best option is to use an Event Receiver.


1

Use a SharePoint Designer workflow, started when the item is created, to wait for the item to be closed. Wait for Status to equal Closed Set Closed On to Today You shouldn't use a calculated column, nor a workflow with an if statement, as some are suggesting. If the item is opened in edit mode any time after it's closed, and then saved (even if there are ...


1

Create calculated column Closed On with below formula: =IF(Status="Closed",Modified,"") Select Date and Time as data type for calculated column.


1

Instead of empty space use blank. Lookup will not display blank values IF(Date>TODAY(), Course, "")


1

BreakRoleInheritance has two params. Just use false and true for copyroleassignments and clearsubscopes respectively then add the groups you want: $list.BreakRoleInheritance($false,$true) $group = $ctx.Web.EnsureUser($group) $roleDef = $web.RoleDefinitions.GetByName($role) $ctx.Load($group) $ctx.Load($roleDef) $roleBinding = New-Object Microsoft.SharePoint....



Only top voted, non community-wiki answers of a minimum length are eligible