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.
Had a colleague ask me the other day if there was a limit on the People Picker control in SharePoint. Reason being is that she had a Person field setup to accept multiple users and had a group that was constantly getting the error “Item cannot be more than 256 characters” when trying to enter the users. After a bit more digging, found out they were using a list of about 20 people or so and then just pasting them into the people picker box. They had everything correct with semicolon separators and everything, but kept getting that error.
These days it is really easy to create lists and libraries to store data and documents. It is also very easy to build metadata to support the information you are trying to store. However, as I have stated before it is also very easy to set things up incorrectly. This next post in my Power User Best Practices is going to cover what you should and shouldn’t do with a SharePoint List and Library.