Hey everyone! Lots of chart bug fixes, and some new and interesting features.
What’s New?
- More robust education and warning for non-recommended Circular Relationship creation between a Table and itself and/or its parents or grandparents.
- We’ve enhanced the ability to see all the Fields from a Grid View, keeping the Views from cutting off other Views, see the following video.
- The logged in user is now the Default Value (DV) on User Fields within Forms.
- Now, for Default Views, you’ll see a new naming convention, [Table Name] Default View to help Builders and Users know where data is surfaced from or populating.
- The new naming convention paved the way to allow for duplicated Field Names when creating Groupings from multiple Tables.
- Improved Warnings about Character Limits for Application names.
- We’ve updated the Form Builder Placeholder behavior, Builders can now choose which Form Fields have placeholders and which ones do not.
- The Form and/or Form Section must already be saved for this new feature to work, this is not ideal and is being addressed in our next release.
What’s Fixed?
- Charts:
- Hitting ‘Cancel’ instead of ‘Save’ after updating Chart colors doesn’t revert the selections made.
- Legends will now remain on the selected side when they’re shifted page by page.
- Random missing labels on charts resolved.
- Re-arranging the Fields of a chart stay in place as expected.
- App Admins can now access Flows as expected in Sandboxes.
- Resolved UI of the ‘+’ records in Grid View, now when ‘+’ is clicked, the other Records open in a Modal at that location on the page.
- For a more consistent experience, we’ve unified the Session Timeout and Logout page.
- Expanded group views now no longer overlap each other and appear more readable.
- The placeholders for Form Builder and Form Editor now match for the following Field types: Date, Datetime, Calculated Date, Calculated Datetime.
- With some of these improvements and fixes, we’re also creating extra Knowledge Base articles to help our Builders better understand nuances of the system and behaviors that they’re experiencing.
API v23.25
Comments
0 comments
Article is closed for comments.