Skip to main content

Currently we are investigating if we could upgrade our platform version from 2024.1 to 2024.3 

Listed as a possible breaking change is that using the Next group option in the form would add an empty space above the first visible column of that group, with the recommendation to use the Field in next column option instead: 
https://docs.thinkwisesoftware.com/blog/2024_2#field-in-next-column-support-for-the-universal-gui

For one of the major screens in our application it will result in undesired behaviour like this (blank space above the fields):


However, when we change the option Next group to Field in next column, all fields will be reverted to the full width of the column regardless of the value of Field no. of positions further:


Intended behaviour from version 2024.1:


How can achieve having 2 (or more) fields next to each other per column without the column header in the 2024.3 version of the platform?

Hi Ruben,

I think too many form fields have been set to Field in next column.

Check for fields that have Field no. of positions further set to 0. Those should not be marked as Field in next column.

For instance, Contract and Contract type are on a single position. You can see this by the margin between the two fields. Also note how Voyage type below these fields spans the full width of this form column.

If you set Contract type to Field in next column, the setting that they are on the same position is nullified and the field will take up a full-width position.

@Ruben_Kwant that screen looks familiar to me 😊

I hoped it would work for you by NOT setting Next group or Field in next column at all for these columns and have the GUI divide those over 4 columns based on the Max no. of columns Subject setting and the available space in the GUI. Could you try that and share a screenshot of the result?

When unchecking both Next group and Field in next column for all columns which were originally marked as Next group, the Universal GUI would rearrange the columns correctly again based on No. of columns in form:


This is the intended behaviour like we had it in 2024.1

Thanks to both of you for responding @Anne Buit  @Arie V 

@Ruben_Kwant Great! Not having to configure this on Form field level was the reason I let the team change it again between 2024.2 and 2024.3. I’m glad to hear that it worked out for you as I expected!

Reply


Terms & ConditionsCookie settings