Browser Forms

Re: Timing Issue for Form Load rules

larslynch — Thu, 17 Oct 2013 13:28:52 GMT

I had the same issue and following Hilary's clue, I was able to use change rules to make it happen for a dropdown lookup list (not available as a connection target from the Query webpart).

1. Create a visible field on the form for your incoming parameter (textbox, calculated value, etc).

2. Create an action rule that fires when the value of this field changes to do whatever you need to get done (set dropdown or other field).

3. Create a formatting rule that always hides this field.

My blog post: http://larslynch.blogspot.com.es/2013/10/passing-url-parameter-to-infopath-and.html

Re: Timing Issue for Form Load rules

Hilary Stoupa — Wed, 02 May 2012 15:57:23 GMT

Yeah, I'd bet you are right - rules run before code, and while I won't claim to understand the mechanism InfoPath is using to get that query filter value, I'd assume it just isn't present when your form load rules run.

As to a work around - that may be tough... But perhaps you could set your rule on the field you are setting to yes? That is, the parameter changes the field, and then you logic executes?

Timing Issue for Form Load rules

cyb9421 — Wed, 02 May 2012 14:20:45 GMT

I have a browser form on Infopath 2010 and Sharepoint 2010. I am attempting to pass a parameter to the form using a page with the Infopath webpart and the QueryString filter. I am getting the parameter fine, but if I attempt to perform a rule on the value in the Form Load event, the parameter does not appear to be there yet. That is, If the parameter is "Yes: and in the Form Load section I do a rule (If parameter="yes), the rule fails, yet if I include the parameter on the form, I see that the value is there. It is not extra characters or anything to do with the matching of the values. This has to be a timing issue, where the value does is not there when the Form Load rules are run, but is subsequently there.

Any ideas?

Chip