|
|
Search
You searched for the word(s):
< 1 second(s)
-
Vadim, I don't know if you will see new replies to old threads, but I have something to add. I created a test workflow that limits its query to 300 or fewer items on each iteration. It filters so that 1 <= ID < 301, tne next time, 301 <= ID < 601, etc. I had hoped that this would be a workaround, but it ...
-
I am encountering the same issue in NW 2007, build 11200(?). Is there an update for 2007 that fixes this?
-
Never mind, I'm being stupid. 8-o
-
I mentioned this in a previous post, but think I should repost with a pertinent subject line.
I have created a simple test workflow. It has workflow variables called LastCalDate and NextCalDate, both of type Date and Time. I have set LastCalDate to 5/1/2012. Then there is a Calculate a Date action which is set to operate ...
-
Never mind that. I deleted the Calculate a Date action and added it back. This time it worked, even though I don't think I did anything different.
HOWEVER, I had it send me NextCalDate in the Notification step, and it is showing 5/1/2013, a full year ahead of LastCalDate. I double checked, and Calculate ...
-
I have a simple workflow that I built just for testing date calculations. I set a workflow variable called LastCalDate to 8/1/2012, then for the second action used Calculate a Date, and entered 6 in the Months field, store in NextCalDate. Then I have Set a Condition, Compare any data source where NextCalDate is less than (date when ...
-
This thread brings up a question I have had that is indirectly related. I have created some scheduled workflows similar to what you describe, which act on all list items, or a subset of them. Yet, unless I am missing something, these workflows must be started from one item in the list, even though it may not be particularly pertinent ...
|
|
|