-
In your validation, try using
translate(date1, '-', '') > translate(date2, '-', '')
That will probably work better.
-
It's probably best to avoid completely starting over, and creating a form based off of a webservice has its own large limitations, as I can see in another thread that you've already discovered.
For whatever reason, InfoPath doesn't allow using the Add Row/Delete row actions on repeating tables bound to a secondary data source, but ...
-
I think you've misunderstood your reasearch. The issue is most likely that the node you're trying to modify has an xsi:nil attribute that has to be removed before you set its value. If you search this forum for xsi:nil, you should find examples of how to to this.
In order to put the date in the right format, you need to ...
-
Most likely you need to put the [1], [2] after rsIssueDescription, not tbIssueDescription.
-
You can spread it across multiple expressions in the condition for a single rule, and join the expressions with the AND dropdown box. All of the expressions would look like the one I showed you, and you would just use different fields in each.
-
The expression is a little verbose, but please give the attached template a try.
-
Code written as script (JScript or VBScript) is stored in the XSN and can't be concealed from users. If you want to keep your form code secret, you will need to use compiled .NET code.
-
When you publish the form, the code will be compiled into a DLL and this will be embedded in the XSN template. As long as you distribute just the XSN, nobody will be able to see your code.
-
Could you attach a screenshot of your main data source?
-
Were you able to determine which line was causing the error?