Conditional Default Values

re: Conditional Default Values

Jim Gagliardo — Fri, 11 May 2012 13:55:12 GMT

Thanks for this post. Not much documentation out there for this.

re: Conditional Default Values

Scott Heim — Fri, 02 Dec 2011 13:52:26 GMT

Hi Corrie,

I should be able to assist but I would like to get a bit more information. So you have 3 fields on your View: FieldA, FieldB, FieldC. If "FieldA" contains data, you want to display that data in "FieldC"? Then if "FieldA" is blank you want to display "FieldB"? I just want to be sure I follow what you are trying to accomplish.

Scott

re: Conditional Default Values

Corrie Sigler — Thu, 01 Dec 2011 15:02:12 GMT

I am trying to do something similar but can't figure it out.

If Field A contains data display in Field C otherwise display Field B. Can you give me an example to resolve please.

Many thanks!

re: Conditional Default Values

Nicholas Lovell — Wed, 29 Jun 2011 17:30:06 GMT

Actually, (ElseResult | TrueResult) == (TrueResult | ElseResult). Check out the caveat noted above:

... The node set will always be returned in document order. It does not matter what the order is in the parenthesis, as (field1 | field2) == (field2 | field1). Since you cannot change the node set ordering, you may have to modify your BoolCondition to be NOT-ed. For more information on document order, you can visit the w3.org page on XPaths.

re: Conditional Default Values

Mojtaba Aliakbari — Wed, 29 Jun 2011 09:57:20 GMT

The expression

if (BoolCondition) {

TrueResult

} else {

ElseResult

}

becomes

(ElseResult | TrueResult ) [(BoolCondition) + 1]

not

(TrueResult | ElseResult ) [(BoolCondition) + 1]

re: Conditional Default Values

Scott Heim — Mon, 20 Jun 2011 12:00:34 GMT

Hi Joe,

This example will only work when there is one test and the result is true or false...in your example, there are multiple tests. So the best way to accomplish what you need is to use a Rule on field1 (with 3 conditions) that sets the value of field2 based on the conditions you have in the Rule.

Here is what I have as a sample:

- Main Data Source:

myFields

field1

field2

- 3 Rules on field1 as follows:

Rule 1:

Condition: field1 < 29

Action: Set a field's value: field2 = "A"

Rule 2:

Condition: field1 > 29 and field1 < 39

Action: Set a field's value: field2 = "B"

Rule 3:

Condition: field1 > 39 and field1 < 49

Action: Set a field's value: field2 = "C"

Scott

re: Conditional Default Values

Joe — Mon, 20 Jun 2011 08:53:55 GMT

How do I go about an situation like the following

I want to create a conditional expression which will give a result with the following conditions

If field1 < 29 = A

If field1 >29 and <39 = B

If field1 >39 and <49 = C

re: Conditional Default Values

Jeff Mather — Tue, 08 Mar 2011 22:31:28 GMT

Here's a formula for the name of a day of the week, using the above technique, in case anyone could use it:

concat(substring("Sunday", 1, (@DayOfWeek = 1) * string-length("Sunday")), substring("Monday", 1, (@DayOfWeek = 2) * string-length("Monday")), substring("Tuesday", 1, (@DayOfWeek = 3) * string-length("Tuesday")), substring("Wednesday", 1, (@DayOfWeek = 4) * string-length("Wednesday")), substring("Thursday", 1, (@DayOfWeek = 5) * string-length("Thursday")), substring("Friday", 1, (@DayOfWeek = 6) * string-length("Friday")), substring("Saturday", 1, (@DayOfWeek = 7) * string-length("Saturday")))

I wish InfoPath didn't make us jump through such awkward hoops to accomplish simple stuff like this!

re: Conditional Default Values

Mark — Fri, 04 Mar 2011 22:08:27 GMT

The disconnect between InfoPath 2010 and SharePoint seems very large. IF statement functionality is allowed for default values in Sharepoint list fields. Simply opening a form in InfoPath, making a minor layout change and publishing, breaks your default value because InfoPath 2010 does not allow IF statement functionality.

Metadata fields don't even try to work in InfoPath 2010. As a customer, it's very disheartening when you want to make a simple change in Sharepoint and it forces you to open up another tool (in this case InfoPath), and then the tool does not have what the user sees as basic functionality, or the functionality is completely different.

It seems like the Sharepoint and InfoPath teams at Microsoft are working independently of each other, and there's a major disjoint between the products. Which, a user is expecting to be seemless between the products because SP forces InfoPath on the user.

re: Conditional Default Values

KLF — Thu, 08 Jul 2010 19:39:21 GMT

Along the lines of conditional values- I am creating a form to be accessed in a browser and I am trying to set conditional formatting. I want to make a set of check boxes appear if one certain check box is checked (for instance field 1 is a check box- if they check box 1- fields 2 and 3 appear and are also check boxes). I have tried to set a rule and it's not letting me. Please help!