I recently had a need to read data from an xml configuration file that was stored within a SharePoint library. To make things easier I of course went to Google (or Bing) and checked to see if someone else had yet blogged this. Couldn’t find anything, so in order to help out someone else that may need to do the same at some point, I wrote up a quick little blog. Note: this will only work for on-premises versions of SharePoint. I’ll update with a SharePoint Online version in the future. I’ll also write up how to add and delete contents in a future post as well.
Over a year ago, I wrote about SharePoint’s storage limits and threshold, why they are there and and can they be exceeded. I had started to illustrate how the content databases could be exceeded and to what extent, but I really never got to do some more in depth tests. I had promised to come back one day and perform more tests and to show if pushing SharePoint content databases beyond 200GB is possible in your environment.
Back in October I did an overview of the different ways to wait for a change in a SharePoint Workflow. You also have the option to wait for a certain time, there are two options which are waiting for a set duration or waiting until a set date. Either of which are easy to control or set. I am not focusing on these actions in this post, but just a quick note if you want the date to be dynamic when using wait until a date, then you will have to set the date you want in a workflow variable prior to setting the wait value. Otherwise your date is going to have to be static and that’s probably not going to work for you in 99% of your workflows.
Today, however I want to discuss waiting for a value to change on the list your workflow is attached to.
Bit of a disclaimer: Why am I still talking about SharePoint Designer? Why not Microsoft Flow? Don’t worry, I have some Flow blogs planned. However, Designer is still widely used and will be for some time. I encourage others to use flow where they can, but remember that not everyone has access to that yet. Designer is free and anyone with a SharePoint environment can make use of it. Hence, I still see providing insight and knowledge on this product very important.
I have a bit of a TLDR here as you may be just looking for the answer, and not WHY it is occurring. I strongly urge you to read the whole post to understand why things are the way they are and to make you a better person ;-p, but if you are in a hurry or think I talk\write too much, just click here to find out what you need to do.
There are already a ton of posts out there where a SharePoint 2013 workflow becomes stuck at started or starting. Well I have another one. This problem actually originated in a SharePoint 2013 farm. If you are using SharePoint Online, the cause is actually pretty easy to determine. So for those of you not lucky enough to be working with SharePoint Online, I will go through the symptoms you could come across and a possible resolution.