# Deprecated Items

The following items are deprecated and at some point in a subsequent release will be removed:

The Import Metadata from Audio File statement
  Use Transfer Metadata as an alternative.
The Linked to Apple App Test statement
  Use the Compare Numeric statement testing property Is Linked as an alternative.
The Lossy Encode As statement
  Use Re-encode as an alternative.
The Modified Test statement
  Use the Compare Numeric statement testing property Is Modified as an alternative.
The Test Property statement
  Use Compare Numeric and Compare Text instead.
UD Text Column Mappings
  These are an older means of displaying UDTIs as columns. Custom Fields provide a much better audio format independent means of accessing UDTIs which can be displayed as columns.
The Inline Fields mode in the Exists statement
  Use the Fields in Named Variable mode instead.
The Extract Preference Set Statement's Action Runtime Settings with Prefix function
  The usefulness of this function is dubious. It was introduced at a time when the runtime settings were always grouped together. Being able to partition the settings into separate replacement sets eliminates the need to prefix the settings.
The Prompt for Text List R/O and Prompt for Text List Overwrite named variables
  Use of these named variables has been replaced by format codes in the Prompt for Text Formatting named variable.
The Enumerate Fields, Roles and Extensions Statement's Supported Image Filename Extensions function
  The function now only most common subset of the supported image types.
The popupEditable object key used by Prompt from Container statements
  Replaced by isPopupValue set to 2.
Selecting Yate in a Clear User Defined Items by Source statement
  The use of the Yate item in this statement is deprecated. Selecting Yate will not remove Yate Album ID and Yate Track ID if they have been defined as custom fields. You should use the Yata Database IDs statement to remove them which always works.
Prompt from Container statement's selectedRow Key
  Prior to Yate v6.11, the selectedRow key was incorrectly written to the Columns object as opposed to the container object. For now Yate will write the key to both locations in order not to break any existing actions ... but at some point will stop doing so. You should always read the key from the container object.
Prompt for Text List Selection named variable
  The named variable is treated as an alias of Prompt Menu Item Reference. All occurrences will use Prompt Menu Item Reference at runtime.