-
Seems like you've found a good step by step tutorial so go for it!
-
Not that I know of. The form library form has a complex, but unlocked schema. The list form will have a flat schema, locked to the list's columns. If your form has even one repeating node, you'll run into a challenge converting into a list form.
-
Here's my sample form so you can open it in design mode.
-
Getting the formula right is a bit tricky. Here's what I've got in my sample:
xdMath:Eval(xdMath:Eval(my:group1/my:group2, 'concat(substring(my:field1, 8, string-length(my:field1)), ";")'), "..")
-
Hi-
Here's a blog post that explains the options if you'd like to map data into a SharePoint List.
http://forums.qdabra.com/2013/05/map-infopath-form-data-to-a-sharepoint-list/
Good luck!
-
I think the problem is simpler and no code is needed.
Simply add a field to your form called my:Status and set its value (via rules) when the user clicks Save or Submit. Promote this field, i.e. make it a promoted property.
Then, in the SharePoint form library, you can use the value of Status to determine whether the workflow starts or not. If ...
-
If the control is bound to a secondary data source node, the node won't persist the data after the form is closed and reopened.
So assuming the control is bound to the main data source, it could only get cleared via (1) user input or (2) a rule (form logic). You could check the Logic Inspector to see if there's an action somewhere on the ...
-
Do the submit actions have a condition on them? Maybe the condition is not satisfied on the first click but it is satisfied in the second button click?
-
I don't think you need a condition. You need to be setting the value of the queryField.
-
Sorry, I don't know what else to tell you. I have fired up a quick, sample form. In one textbox (string) I used your same formula (I get 06). In the other textbox I just type in the month number (06).
It works fine. The button is disabled and enabled as I expect. That is, the comparison works correctly.
[quote ...