Views

Re: Sharing elements across views

Jimmy — Mon, 24 Oct 2011 21:05:31 GMT

I presume what you want to do here is be able to make changes to the button's logic without having to re-copy the button into all of the views every time you do that, is that correct?

There isn't a way to have controls that exist in all of the views and automatically reflect any changes you make to them, but this is what I do whenever I have some logic that I might want to carry out under different situations.

Create a secondary XML data source with a bunch of fields to serve as "triggers" for various operations. I import them with blank values and include one more field called Stop.
Add rule logic to each of these "trigger" fields, as follows:
Rule 1:
Condition: (the current field) is blank
Action: Set the Stop field to blank. Stop executing rules.

Rule 2, 3, 4, 5, etc. - The operations the trigger should carry out.

Last rule: Set self to blank.

Then, you just set up your buttons to have the rule action: Set (trigger field) = "go". The trigger field carries out the actions and resets itself to blank when it's done. You only need to modify one set of rules any time you want to change the logic.

Do you think something like that might work for you?

Re: Sharing elements across views

bigeldm — Mon, 24 Oct 2011 20:47:34 GMT

unfortunately we are not using form services.

Re: Sharing elements across views

Rémi MATAYRON — Mon, 24 Oct 2011 19:27:35 GMT

Are you using InfoPath Form Services or an InfoPath client version?

With InfoPath Form Services, you can create an XmlFormView custom in order to put asp button into the page.

It is not an InfoPath control but he will be display in the same page.

Hope this help.

Sharing elements across views

bigeldm — Mon, 24 Oct 2011 18:13:15 GMT

Is it possible to have a button (for example a save button) that perpetuates across all views without having to be repeated on each view? Kind of like a master element that shows on all views?