We have a version of AccountEdge Pro that works on Catalina and Big Sur (and Apple M1 chips) without requiring a virtual machine. Learn More.

Please visit our COVID-19 Resources page for useful payroll and reference information. If you are teleworking, check out Working Remotely with AccountEdge.

  • Section: Importing/Exporting
  • Last updated: June 28, 2019, 2:48 p.m.

Record ID in AppleScript

Many of the AppleScript commands in AccountEdge require the Record ID of a transaction. For example, the command 'show me sale' requires the unique Record ID of a particular sale.

The commands 'import one sale' and 'import one purchase' were designed so that another program could trigger an AppleScript to have AccountEdge create a transaction in a particular file. When the transaction is created the Record ID is returned as a result.

So if the scripter stores that result in the other program as the transaction's unique Record ID, it can later use that as the variable in other commands (for example, the 'show me sale' command to display a particular sale in AccountEdge).

If the transaction is not created via AppleScript, it is not possible to find the Record ID at a later time.

Additionally, it may clarify some confusion to note that the Record ID on an exported transaction (usually the last field on an exported transaction) is actually the Record ID of the card on the transaction. So it is not possible to export sales or purchases to find the Record ID of a given transaction.

The same logic applies to the Record ID of items. The Record ID of an individual item can be determined at the time of creation if it is created via the 'import one item' AppleScript command. It is returned as the result of the command. It is not possible to determine the Record ID at a later time.