Data Record Links
- As mentioned in Financial Data Records, the financial impact of records can be interdependent, hence the financial records and their relations are represented as a graph. With relations in mind, each financial record can be linked to another within the graph via reference.
- For example. a payment workflow will contain an invoice leading to a payment which can lead to a dispute. Each financial record will have a link from one to another.
Query a Link
VW_RL_LINK table consists of unidirectional links represented as rows. Details regarding the linked records are represented in fields with the term
A record can have many linked records. Each link/relation is represented as a row within the table. If many rows have the same
LEAPFIN_ID and different
LINKED_LEAPFIN_IDs , then this will be a one-to-many relation.
|CREATED_AT_DT||The Timestamp of when the link is created|
|DECODED_LEAPFIN_ID_VT||decoded version of LEAPFIN_ID in JSON format. It contains the following values:|
|DECODED_LINKED_LEAPFIN_ID_VT||decoded version of the Linked LEAPFIN_ID in JSON format. The values resemble what is shown above.|
|LEAPFIN_DATA_TYPE||Type of Leapfin object|
|LEAPFIN_ID||unique identifier created by Leapfin.|
|LINKED_LEAPFIN_DATA_TYPE||Type of Linked Leapfin object|
|LINKED_LEAPFIN_ID||Unique identifier of the linked Leapfin Object|
|ORGANIZATION_ID||The unique identifier of the organization|
|UPDATED_AT_DT||The Timestamp of when the Record Link was last updated|
Note: All timestamps do not consider time zone. To learn more, click here
Query Linked Records
Users can use this table to link between records and perform forms of aggregation. For example, in order to understand all of the payments tied to invoices, the
LEAPFIN_DATA_TYPE can be filtered for all
leapfinInvoice records while the
LINKED_LEAPFIN_DATA_TYPE can be filtered for all
Then, you may use either identifier,
LINKED_LEAPFIN_ID to connect to respective tables for those records (
VW_FT_PAYMENT) and complete further analysis.
Please note, if you'd like to investigate all the payments tied to invoices (vice versa to the example above), you would have to filter inversely, ie.
LeapfinInvoice). This is due to the unidirectional representation of links within the table.
Updated 5 months ago