This topic contains 2 replies, has 0 voices, and was last updated by KristinaAlt 8 years ago.

  • Author
    Posts
  • #2713

    KristinaAlt

    I’m building a new entity subtab with a number of custom fields- namely Lists, Currency, and Free-Flow Text, and am having issues getting them properly sized (width) and aligned in the UI. I’ve reviewed Help/SuiteAnswers and this forum for hours to no avail.

    Note, I have applied Field Groups to this subtab, which I know has impacts to the display.

    Issue 1: The List and Currency fields are displaying much wider than they need to be, even when considering the available values in the lists. Anyone know if/how these can be shortened?

    Issue 2: The free-flow text field on the far right of the Freight field group extends across the page in Edit view, but it gets wrapped in View. The fields are all set up as individual columns already, as the solution in SuiteAnswers 38217 seems to refer to.

    I’ve attached a couple images of the current UI display to help demonstrate the issues (the first is of View mode, 2nd is of Edit mode).

    Any assistance the community can provide will be most appreciated!

    Attached Files
    This is a cached copy. Click here to see the original post.

  • #2714

    schollguin@gmail.com

    Kristina, I’m curious if you were ever able to figure out a way to solve your Issue#1? I have lists where the entries are only 3-5 characters long, and yet Nesuite wants to make the DropDown List field enormous. And if I try to put two List columns on the same row even if they both contain entries that are 3-5 characters long, it will wrap and put the second one on the next row even though there is plenty of width available because the field directly above them is 80 characters in length. Frustrating, so I was wondering if you were ever able to figure out any tricks to solve your issue.

    Thanks for any insight you can provide.

  • #2715

    KristinaAlt

    schollguin@gmail.com , unfortunately I was not able to find a solution/direct workaround for either issue. It was solved it for us by abandoning the above design concept and switched to using a couple custom records, then displaying them on the entity in sublists. Good luck!

You must be logged in to reply to this topic.