Search Changes Release (deployed 9/4/2020)

What’s New?

• List Search values, delimiter, and field selection persist for the current user session within a given app. For users that leverage List Search for a series of values such as Sample barcodes or SKUs, that set of values, as well as any delimiter and the target field, are now retained in the List Search tool for the current user session and app, or until cleared by the user using a new [Clear] button. Now drop a single set of List Search values into the panel, set the parameters once and apply that search multiple times with no additional data entry required.
• Simple and Advanced Search retain a value where possible when a field is selected. If a user enters a value in the simple Search box or an Advanced Search property and then chooses a field, the system will retain the value entered if it is compatible with the type of field selected. For example, entering "12345" and then selecting a Text field type will retain the value "12345" for searching.
  
• Chart filters now include related fields for "many" relationships. Previously, chart filters only supported relationships on the "one" side. It's a known fact that more filtering options = more fun!
• Additional options when querying a User field. “Is Blank” and “Is Not Blank” operators have been added.

What Did We Fix?

• Certain searches causing a SF-S1008 error. Those SF-S1008s are just no fun, we much prefer SF-A1000s, or the occasional SF-F1000 for variety. 
• A validation error preventing some dynamic fields from being added to a view. If the dynamic field contained rules with multiple conditions and was from another application, the View was not being welcoming. It has been subjected to a sensitivity course and behavior has improved markedly.
• Fixed a "ghost" error regarding duplicate values when updating a record with multiple unique fields. There were no actual duplicate values, but the system was convinced there were. Just to be sure, we also removed "The Sixth Sense" from the company video library as a precaution.

What Did We Change?

• List Search no longer offers an "All Fields" option. The user must now select a target field for a List Search, such as "Barcode" when utilizing barcode values. This field selection is now persisted for additional List Searches, as well as any delimiter entered by the user.
• Simple Search no longer has a default field selection if an "All Fields" simple search is currently applied. This requires the user to select a specific field to search if "All Fields" is currently applied, preventing the system from searching on whatever field is listed first in the field picker.