The event log can be used to track changes in Next for different entities.

However, not every operation will result in an event log entry. Some operations will also result in two event log entries. For example, when a work order is moved from one project to another, two event log entries will be created, one referencing the source project and one referencing the destination project.

Another example is that events for internal costs are not generated when creating/updating/deleting work order rows or time on a work order in Next. Internal costs are cost/revenue rows that are automatically generated by Next when making changes to a work order. This means that internal costs which are automatically created in Next Project because of a work order row or a booked hour change to work order will not be visible in the event log.

Another example is that when Next support restores previously deleted data by request from a customer, events might not be triggered for that restored data

So experimentation and testing is very important before starting to use the event log, and it's up to the integrator and customer to verify that desired scenarios work as expected.

The following strings are possible for the storename parameter (to be used in a filter string on the endpoint):

AdditionalWorkOrder
CostRevenue (In the response from the event log endpoint, this storename is called "VoucherRow", and corresponds to voucher row endpoints in the API)
CustomerOrSupplier
Invoice
Journal
Project
Supplier
SupplierInvoice
Time (corresponds to endpoints "Booked Hours" in the API)
WorkOrder
WorkOrderRow

Relevant endpoints

/eventlog/