Sharing elements across views - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

Sharing elements across views

Last post 10-24-2011 02:05 PM by Jimmy. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 10-24-2011 11:13 AM

    Sharing elements across views

    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?

  • 10-24-2011 12:27 PM In reply to

    Re: Sharing elements across views

    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.

    RĂ©mi MATAYRON / MVP InfoPath
    Visit my blog : Infopath Blog
  • 10-24-2011 01:47 PM In reply to

    Re: Sharing elements across views

    unfortunately we are not using form services.

  • 10-24-2011 02:05 PM In reply to

    Re: Sharing elements across views

    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.

    1. 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.
    2. 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?

    Jimmy Rishe / Software Developer / Microsoft MVP
    Qdabra Software
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.