Syncing generalLedgerTransaction

[tenacul]

Hi Business NXT team,

We are currently working on retrieving data from the "generalLedgerTransaction" endpoint. While it's functioning well for a full data load, we're facing challenges when trying to implement a synchronization option in our query. We were thinking of working with either the "changedDateTime" or "changedDate" fields.

In other systems, we typically see a primary key, often referred to as an "ID," that we can use to identify and delete previous data for records that have been updated. In Business NXT, we've encountered the "voucherJournalNo" and "voucherNo" fields, but these fields frequently contain multiple records with the same number. Initially, we considered deleting all records associated with a particular "voucherJournalNo." However, we've observed that the "changedDate" and "changedDateTime" values can vary for different records sharing the same "voucherJournalNo" or "voucherNo." Is there another reliable method to identify which records/lines we need to delete or something else that you can recommend us, so that we are able to keep an up to date table from the generalLedgerTransaction?

I hope our request is clear.

Thanks in advance for your time.

[Marius Bancila · Accepted solution]

The GeneralLedgerTransaction table does have a key; however, it's a multi column key made of the voucherJournalNo and auditNo columns.

In general, you can check the primary key columns for any table in GraphiQL (https://docs.business.visma.net/graphiql/😞

- open GraphiQL

- write a simple query like this:

- hover the cursor over the table (or any schema entity) that you want to explore:

- click on the links (here, the connection) and explore it in the Schema Explorer (on the right)

Primary keys are marked with [PK] and are always displayed first.