I have a site that is saved as a template, and close to 200+ sites have been created out of that template. All worked great until one day when I received this request for a change in one of my workflows in one of the lists of the site.
Also, this change had to be copied to almost 40 out of the 200 sites created.
Of course, I made the changes in the template site, but the challenge was how do I publish my updated workflow to the said sites.
This happened to be a slight extension to the same methodology that was used previously. Continue reading →
Requirement – I have a site that has around 40 country lists which have the same workflow. When there is a change in the workflow, there is a need to update the workflow in all 40 lists; which is practically impossible. Also, it wouldn’t be considered a good practice.
As most of the times, I knew there was a solution using Nintex. And the moment I found it, I fell even more in love with this workflow tool. It keeps surprising me as always!
Solution – Nintex workflow comes with a web method called PublishFromNWFXML that will do this job for us.
Update your workflow at the parent location and export it. Upload the nwf file to a library (here – Shared Documents) and create the below workflow on this library, that will update it to the multiple lists.
In my previous post Reading the recurring events in a SharePoint calendar using Nintex – Part 1, I discussed how the data gets structured in the XML format when a calendar event happens to be recurring. Now let us focus on how to extract the required information from that XML and calculate the next occurrence of the event. This will enable us to send reminder emails to the users before the event.
You ought to have a lot of patience since there is quite a lot of work posted here. Be persistent!
Recurrence in SharePoint’s calendar list is a wonderful feature that allows the creation of events that may be recurring in nature. It could be daily or weekly or monthly or yearly recurrence.
Once a recurring event is created, it is smart enough to update dates in the calendar accordingly.
Now I am not writing this post to tell you the benefits of recurrence in a calendar list. I have my own reasons.
My requirement was to send reminder emails to the users 4 days in advance from the date the event is to happen. Also, an email should go on the same date of event.
I was under the impression that it should be pretty simple. But my conviction was lost when I saw that the start time is the date of 1st occurrence and end time is the date of last occurrence. Which means the dates that come in between are not logged anywhere for me to do the comparison and send out emails. Although the calendar view of the list shows all occurrences properly.
So the foremost concern was to get the recurring information of the event.
A lot of research led me to my findings which I am sharing here, so that you don’t have to invest your time in it.
Many times there is a need to segregate the components of a date column. For instance, the date, month, year or the day of the week.
They are needed to perform multiple calculations and also may be responsible to define some logic. So, here goes my post that gives an insight of how to isolate the date components using Nintex workflows. Continue reading →
Issue – Querying a calendar list for the date time field.
I had never thought that querying a calendar list in SharePoint for events in a particular date (ignore the time ) would be so much trouble. But somehow, I managed to overcome the issue. So here’s some light on it so that you can save your time next time you got to do this…
The SharePoint calendar list has a Start Time column that stores the date with the time stamp when an event has to start. My requirement was to query for all events on a specific date, irrespective of the time.
1.) Query all the list items that are checked out.
2.) Get the checked out user names and store in a collection variable
3.) Email to that user with the name of the items checked out to this user only. One email is going to contain all item names that is checked out to one user only. There might be multiple items checked out by the same user multiple times.
Well, it appears to be quite simple and straight forward given the Nintex actions we have, but despite that it took me some real good time to achieve this. So, I’m going to share my pain area in this task and the solution. Continue reading →