-
Sure - use substring-after(CreatedBy, "i:-0#.f| membership |"), selecting the "CreatedBy" field using the field picker. :)
-
I think the best way to do this would be to instead get the specific XML for Form A that the user wants based on the Name and Year selected in Form B, then to copy that XML data into Form B, using code (or you could try qRules). But you may be able to kludge something together w/out - do you have a promoted field for each column in your repeating ...
-
Thanks - you as well, and nope, you were NOT imagining things and neither was your user. :)
-
Hi! In InfoPath 2003, a lot of us thought today() and now() were broken, because they did exactly what you are wanting them to do now. Somewhere along the way that behavior was changed. I'd remove the default value and add a rule instead, in the FormLoad rules (data tab in the ribbon) to always set the field to today(). That ought to get it ...
-
When I went digging through a form manifest to get the XML for my initial reply - I found an orphan right off. My sample was one. :)
-
I think this can happen if you remove a data connection without first removing all the rules - I've never tried to reproduce it tho..... I've also wondered if it might happen sometimes when we remove a field w/out removing the rules first, but again, I haven't invested any time trying to track it down. :)
-
When you end up with a orphaned rule like that, often a manifest edit is your only choice, unfortunately. Glad that fixed it. :)
-
Wonderful, glad you got it! Another place I see this happening is with dates - a lot of time we think what we see in the control is the actual value being stored. But it is just the formatted value. So while your date picker shows 12/8/2015, for example, your form may have a value of 2015-12-08T00:00:00. Which is confusing! :)
-
So - in the manifest, the rule set will have an identifier. Usually, once I find that, I search for that.
So - if the rule with the old reference is: <xsf:ruleSet name="ruleSet_5">, do a search for ruleset_5. If the only occurrence is in the xsf:ruleSet node, you can just delete that node from the manifest, and, in fact, ...
-
You've added a text box bound to the same field and "it doesn't seem to work"? All I'm wondering is if you'd be able to see the actual value stored, which may include the ID and the text description.