optional field - InfoPath Dev
in

InfoPath Dev

optional field

Last post 06-12-2006 09:43 AM by Greg Collins. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 06-02-2006 09:09 AM

    optional field

    Hi I made an optional field and then I made it not optional and decided to put this part of the form into its own view.

    The form is rather long. The problem is that when ever you click on anything it highlights the entire section and jumps to the top of the form.

    This is very annoying for users.

    Anyone know how I can change this or correct this problem. I would like to remove all of this code out of the section all together as it would fix this problem.

    The only way I know how to get part of the form is copy it to another section but then I loose all my controls. There are many drop down boxes and data validation points that I will have to do over.

    Any ideas.

    I can send the form to someone if it helps.
  • 06-02-2006 11:16 AM In reply to

    Do you have any repeating items inside that section that gets the blue highlight?

    If so, you need to put the repeaters inside a containing section to prevent their commands from bubbling up to other sections. If you right click on the section when it highlights blue, you'll see a list of commands which should help identify the offending repeaters.
  • 06-05-2006 09:02 AM In reply to

    The entire section was an optional section at one time but then I changed it to be included by default.

    There is also a repeating section and some repeating tables in this section.

    I am not sure I understand what you mean by put the repeaters inside a containing section.

    Can you please explain this with more detail.

    Thanks
  • 06-12-2006 09:43 AM In reply to

    It's those repeating sections and tables that are likely causing the trouble.

    Again, if you right-click in the blue section you'll see a context menu appear with commands like "Insert ..." and "Remove ..." Those "..." parts of the menu item will indicate what repeating table/section(s) are the problem.

    Most schemas have a "group" that contains the "repeating group", such as:

    Root
    --Group1
    ----Group2 (repeating)
    ------Field(s)

    If you place your Group2 inside a section bound to Group1 then the Group2 commands will bubble up to Group1 and then stop there... otherwise they'll bubble up to Root--which is where you are getting your problem from.
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.