-
Your datepicker in your form is probably formatting the date as 2010-09-23T08:03:55. Your SharePoint data source may not have the T.
-
Hi:
I'm not sure if this is a typo -- but I see in your example "JSmith" with a capital "S" -- Your conditions will be case sensitive, so keep that in mind.
You can use rules with dialog box expressions to help you see why a condition isn't being met. For example, in a rule prior to the rule for switching views, you ...
-
Right click the link to the attached file and save the file locally, then you can right click again to open in design mode and preview.
I'm not entirely sure what your desired outcome is, but I modified the conditions on two of your rules for the field bound to your multi select so that basically one ruleset runs if Value1 is not ever ...
-
You can use preceding-sibling for this -- you can find a sample form here. Just save the sample locally and right click, select design from the menu and open in design mode. Then you can preview from there.
-
Can you attach your template to a reply (under the Options tab when you reply) or maybe some additional info about the conditions you've tried?
My guess is that since your rules are based off a repeating field, you'll may need to use preceding or following-sibling in the conditions to take into account all instances of the field bound to ...
-
It is one of those tricky bits -- when you start using IP, it seems like a condition is what you want. Usually, though? What you really want is a filter. Glad we can help you stay sane!
-
Hi --
You need a filtered XPath, not a rule condition.
Try this -- remove the condition on your rule set. The, for the first action, where you set PositionShortText, in the formula editor where you select the field from your SharePoint list (@Position_Short_Text), when you click "Insert Field or Group" you should have the option, when ...
-
Oooh, good catch, Potemkine -- then there would be previous versions to roll back to.
-
Can you attach a sample XML file from the previous form and your XSN?
If you change a field name, even a little, and the form is set to upgrade existing XML, the data previously stored in the field will be lost. Do you have any backups you could restore from?
-
You can write code to copy the data from your secondary data source into your main data source. If you were able to add and remove items from a repeating table bound to a secondary data source, the next time the form loaded the data from the data source, everything would be just as it originally was -- since the secondary data source was ...