10.0 UI Spacing on Record View - How to widen the columns?

Hi Club,

I've been hitting a wall on something that I feel is fairly simple yet I can't cross the finish line on that I am hoping you can help me with.

When using a 2 column layout with field names to the side, I am trying to determine how we go about spreading the 2 columns out to use more real-estate of the page.  Using the screenshot included as an example, I would love to have each column take up roughly 50% of the whitespace on the page, which would mean moving the red box to the right.  Then, I'm looking to have the green box expanded to, so that the field name "Default Bill To Location" would show the entire field name.  There's tons of white space that is being lost on our record views that I would love to take advantage of, especially in the case when we have long field names that keep getting truncated when there's no reason to.

Thanks Club-

Craig

  • Hey Craig,

    The issue you are seeing with the extra whitespace is with the CSS in 10.0.x. In 10.1, it has been fixed so that the whitespace is used appropriately, and the spacing adjusts based on the screen size. If you are in our SugarCloud, look into getting upgraded to 10.1. If you are OnSite, a hotfix might be available for the issue.

  • Mike,

    I appreciate you taking the time to respond!  We are on 10.0.1 Enterprise running OnSite.  I went through the Support download to see if there were any hotfixes/updates and didn't see anything. Is there a way to confirm if a hotfix is available, and if so, where I can download it?

    Again, I appreciate your help!

    Craig 

  • Hi Craig,

    Hotfixes are built on a per request basis for a Bug, for OnSite customers. The Bug you are experiencing is Bug #84693 . If you open a Case to Support, requesting a HotFix, my team can get one built out and sent over to you.

    Regards,

    Mike Russell

  • Perfect, I have opened a case to request a Hotfix!

  • This is a great news. I had users react not too positively on the spacing issue on v10. I'm glad this is addressed in the v10.1 release.