-
The rules are never firing because the conditions are incorrect.
Notice this screenshot: the rule is setting the value of the attribute to the same value of the condition. So, the rule will never meet its own condition.
The condition needs to be opposite of the rule.
-
Those two address the first section, and might help you resolve the other sections as well.
Let us know if you have any further questions. Thanks!
-
The rule should look like this. Notice how the field to be set is bound to an attribute on the form.
-
The second issue I see is that the is_Visible field that's getting set appears to be incorrect in the rule.
-
Hi,
There are a few issues.
Here's the first one: you seem to be setting the field to both 1 and 0 in consecutive steps.
Clicking should only set the is_Visible to either 1 or 0. But having these two actions is not going to work.
-
Hi-
It's a little difficult to know what may be going on with the form without seeing it. Would you able to attach it to your next reply (via the Options tab)?
Thanks.
-
Hi,
The problem you've encountered is the following:
- When the form is opened from DAT, DBXL is able to automatically detect which doctype it belongs to, and therefore submits to that doctype.
- The form, opened from a file share, is not connected to a doctype, though it has a DBXL submit data connection.
I believe the solution is to ...
-
Hi,
Are you asking about this?
http://www.infopathdev.com/blogs/mel_balsamo/archive/2009/01/14/hide-show-section-template-part.aspx
Or something else?
-
Query 1:
The ID value is most likely the ProjectID (which is guaranteed to be unique). There's no guarantee that the ProjectName will be unique so SharePoint cannot have a look up relationship based on that. You could add another field in the form to store the ProjectName, and have rules in the form to obtain the ...
-
If the data is in a repeating node, you can use sum(field) to sum all instances of that field.
If the data is not in a repeating node, you can use regular math expressions ( + ).
I guess if you need more specific advice, please attach your XSN or a screenshot of the schema. Attachments can be added to your response via the Options tab.