Workday Schema Tables

Workday stores data in structures which do not follow the rules of data typing and structure that apply to traditional relational tables and columns. Because traditional ODBC toolsets might not support these data structures, the data needs to be mapped to a relational form. To achieve this, the Simba Workday ODBC Connector uses schema tables to map the Workday data to an ODBC-compatible format.

The schema tables are listed alphabetically by table name. For each table, the following information is provided:

  • The name of the table.
  • Whether the table is a virtual table, and if so, the table that it is contained in.
  • Whether the table contains any virtual tables, and if so, which ones.
  • Any of the columns in the table that are foldable, that is, whether operations on those columns can be delegated to the server instead of the client.
Note: Key points on "How to read metadata in a virtual table?"

  • Virtual Tables usage:Some columns in the tables might contain multiple data instances for same Entity. For example: Person is one entity and a person can have multiple Addresses. In this case the addresses column might contain multiple addresses of same person.

    In this guide, the metadata of such columns is kept separately in a table (called Virtual Table). This helps to easily identify such columns which contain multiple data instances related to same entity. Please note that these columns (shown under virtual table) are part of the Original/Parent table only, and can be queried in a similar way as other columns are queried.

    For example: If tablename is "person" and "addresses" is the column with multiple data instances (i.e. multiple addresses), then it's metadata is stored in reference guide is:

    Table: Person

    <Columns_metadata_of_Person_table>

    Virtual Table: PersonAddresses

    <Columns_metadata_of_person_addresses>

    The following query can be used to get the city and postal code from person's addresses.

    Select PersonAddressesCity, PersonAddressesPostalCode from person

  • The virtual tables in reference guide refer to the metadata of columns and help us to easily know the columns to be used to get multiple data instances of same entity.
  • The virtual tables maintained in the reference guide are not truly present. Additionally, all virtual tables' columns belong to the main table, often known as the virtual table's parent table.