-
Hi. Happy dreams, right? Well, to the best of my knowledge there's nothing that will convert rules to code (though that would make an interesting tool, right?)
To the best of my knowledge (as far as I can recall) you must either use rules OR code to sumbit... both won't work. Please verify this from another source though before going through that ...
-
Sounds like you are well on your way! Hope you were able to get it working!
Greg Collins [InfoPath MVP]
InfoPath Dev
-
You will need to write code to query the library for that particular title. If it exists, and the current form is not the same as the previously saved form, then query the user.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
I believe that if you write your own submit code you can bypass this. The only place where this is not the case is for email submit. You will always get an email submit dialog for security (think SPAM) reasons.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
Whether using rules or code, you should be able to first determine whether the notes node exists. If it does, then you copy it.
Use conditional formatting on the field in the view. If it is blank, hide it.
Greg Collins [InfoPath MVP]
InfoPath Dev
-
If I understand what you are asking, you want to have the user check a box in View A, and when they do, an extra row is added to a table in View B. When they clear the check box, the row is deleted.
If that is accurate, then you should be using the OnAfterChange event handler for the check box. If the value is TRUE then you would use code to ...
-
Did you create the data source using InfoPath or did you start from a pre-existing schema?
If the latter, that is probably the issue. You will need to update your schema to allow signatures. The easiest way to do this is to create a new blank form and add the signatures you want, and then copy that portion of the schema over to your exisitng ...
-
If the secondary data source does not have the ''N/A'' or ''Other'' in it then you will need to do something like populate the drop-down list via code.
If you have multiples of that in your XML, then the best choice would be to modify your XML so it only appears once. If that is not possible, then filtering would be the next best choice.
As for ...
-
Here's a sample of what you can do:
domMyXml = thisXDocument.CreateDOM() as IXMLDOMDocument2;
domMyXml.async = false;
domMyXml.load(''MyXml.xml'');
domMyXml.setProperty(''SelectionNamespaces'', ''[NAMESPACES USED IN MYXML.XML FILE GO HERE]'');
Then you just use it as you would any other XML DOM (such as thisXDocument.DOM).
Hope this ...
-
That works too! Glad to hear you got it working.
Greg Collins [InfoPath MVP]
InfoPath Dev