• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Hide group name in form

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hide group name in form

    When I hide all the fields in a form helper program, it would be beneficial to be able to hid the group name as well

    If ((Mode = '*AddUpdate') or (Mode = '*Approval'));
    HideField('SELNAME');
    HideField('SELADDR1');
    HideField('SELADDR2');
    HideField('SELCITY');
    HideField('SELSTATE');
    HideField('SELZIP');
    EndIf;?

    image.png?

  • #2
    Thought this was already in place...we will take another look. This was added in version 6.3.20240821...are you at this release or greater?

    Comment


    • #3
      I have more information on this...it may be a bug rather than a feature request. If the number of columns in the widget is not blank, and you hide all the fields that are on the group, it leaves that artifact out there. But if you leave the number of columns to 'optional', and then hide all the fields that are in the group, the entire group disappears. I have been able to reproduce this at will.

      ?image.png?

      for me, the number of columns is required for some of my groups so I can get the vertical layout I want. With fields not hidden:

      image.png

      with fields hidden (notice the Original Order group is not shown, but the Name/Address group is.):

      image.png???
      Attached Files

      Comment


      • #4
        Thanks for the information, and we will attempt to replicate and report back

        Comment


        • #5
          What exact version of Valence are you experiencing this in? We are unable to replicate the issue where the group container does not hide after all fields within it are hidden.

          Comment


          • #6
            Just following up on this one. Thanks

            Comment


            • #7
              Johnny, we are on 6.3.20240724.0.

              I will attempt to test it on 6.3.20241120.2

              Comment


              • #8
                this issue does not seem to occur in 1120.2,

                Comment

                Working...
                X