-
I would guess no because you will need to set a field based on the button and then promote it so the workflow can create a condition based on it.
Maybe you can edit the out-of-box in SharePoint Designer, but it's so easy to just create a reusable workflow that does the same thing, I'd go that option.
Maybe the best option is to use our ...
-
you don't care about permissions on your library because you won't be using max(ID). you are submitting, querying the item submitted, concatenating your ID with the ID returned, and submitting again, so the user only has to have access to the form she is submitting and the workflow shouldn't take those permissions away until after the ...
-
Thanks John for posting this workaround. Looks like you have a dual install of 2010 and 2013. We don't test dual install scenarios much because we assume 99%+ of users will have one or the other. Glad to hear you figured it out. Please email support if you find any issues you can't resolve. We're here for you.
-
Please ask S.Y.M. Wongaton about her sample. We can't be expected to debug other people's stuff.
-
Hi Rental99,
You'll want to search on the double eval technique and create a rule that concatenates all values together not as they are adding them, but at the end just before they submit it.
Here's a link: http://blogs.msdn.com/b/infopath/archive/2006/04/05/569338.aspx
-
Hi Bill,
Yes, you may want to use the fully qualified /my:<root>/.../my:StateDates[filter]/my:DateColumn where the <root> is the default myFields replacement and ... is the intervening path, and the my:StateDates is the parent repeating group and the [filter] is the State filter, for example [my:State=<foo>] where foo is the ...
-
Hi Gail,
For Picture buttons, just add two pictures and set hide-show based on a formatting rule. See attached sample.
:)
-
I recommend a 3 character filter. That will no doubt filter it down significantly. Alphabet single character probably would too. Not a great solution but glad to hear that you are game.
-
Hi jayshreePatil,
This is probably a SharePoint limitation. If you type in 300 characters and reopen the form, does it show them? I think it should. SharePoint columns have limited support for data types and lengths (since they use SQL to represent the data).
Sorry to not have a solution for ya,
-
Piece of pie.
You can filter the table - right click and filter to display only items that are blank.
You can also hide rows using a formatting rule - click Manage Rules and add a formatting rule with a condition of your choosing and check hide.
Good luck. No code needed - it's all about the banana cream pie. :)