-
Then put the rule on the TriggerValue field.
-
Isn't this the same issue that you mentioned in your other thread?
Re: Setting a
field value inside a hidden section
If so, I suggested a solution there. Did you try it?
-
You can use a custom expression on the rule in this situation. For example:not(//my:TriggerValue[. != -1]) Will be true when all TriggerValue fields are equal to -1, and boolean(//my:TriggerValue[. != -1])Will be true when one or more TriggerValue fields are not equal to -1.
So you could combine the second one withDropdown ...
-
Rules only fire when the field to which they are attached undergoes a change in value. That doesn't seem to be the situation you have here. Might it be possible to come up with some other rule logic (on the fields that determine whether the section is hidden or not) that will set the combo box's field at the appropriate ...
-
That's because they're not DocumentElements; they're processing instructions. To get at a processing instruction, you'll need to do something like this:
XmlDocument xmlDoc = new ...
-
This should be all you need:
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.Load(@"C:\manifest.xsf");
XmlAttribute nameAttr = ...
-
Do you have any experience working with the XmlDocument/XmlNode classes? Can you show us the code you have so far so I can fill you in on the necessary missing steps?
-
Yes, that's pretty much the best that can be done. For the middle step, you can write a .NET tool to:Open up the manifest.xsf and template.xml files using the XmlDocument class.Make the necessary modifications using the XmlDocument object's access methods.Re-save the files using the Save() method.
-
You can make a separate view that is a "read-only" view and have a "Submitted" field in your form that is set to true immediately before submitting. Then have a form-open rule that switches the form to the read-only view if that field is true.
-
Would you mind telling us what the error is?