List Search Updates & Performance Release (deployed 3/28/2021)

What’s New?

• List Search now supports up to 3 target fields. Previously List Search was limited to a single target field. Now up to three fields can be searched against the value(s) entered in the List Search window.
• List Search now supports Any or All. With the additional functionality to support more than one target field in List Search, the user can now select whether Any or All of the target fields must contain the search string.
• Optimization record retrieval (charts, views, calendars, etc). Makes stuff faster!
• Infrastructure upgrades to improve database performance. This was already deployed earlier in the week (3/22/2021 at approximately 12:30PM EDT) based on performance issues.

What Did We Change?

• Only one List Search can be active in a View. Due to the changes made to the List Search function, only one List Search is now applied to a given View. Selecting the List Search button while there is an existing List Search applied displays the value(s) for the current List Search. Executing a new List Search for a View replaces the results of the prior one.
• Saving a List Search to a View saves the target field(s) and settings. Any existing search string value(s) in the List Search are not technically saved to the View, but the value(s) are retained within the user's browser session and the delimiter is set to newline
• Creation of one to one table relationships is no longer supported. This is only applicable to a small number of System Admin roles and should not affect any existing functionality.
• Removed support for using file fields in dynamic field conditions/filters. This field type (used for attachments) is not applicable to the dynamic field functionality.

What Did We Fix?

• User isn't able to log in to two different browser sessions simultaneously. Now you can!
• Yes/No field bug when configuring an Action. Previously the user could not set whether a Yes/No field had a static value in the Action.
• “Today” function not properly being evaluated in dynamic field condition. Fixed!
• Some Charts were starting at the lowest displayed value instead of zero. Fixed!
  
• Related records fields not reporting time in user's time zone. When viewing time data in a related record field (data is from a related table), the user's time zone was not being reflected in all cases.
• Support for Asia/Calcutta Timezone. This specific time zone was not being passed correctly and causing a "Timezone provided is not valid" error for users with that time zone setting.
• Double quotation mark character causing truncation when editing fields. The presence of a double quotation mark character { " } in a field would cause truncation of additional characters when editing the field.