Why is the entity_modified_date field in the site_events API not updated when an event status changes?

Created by Atif Ikramuddin, Modified on Wed, 22 Jul at 7:16 PM by Atif Ikramuddin

  • The behavior is expected. The entity_modified_date field available in the site_events API is not updated when there is an event-level status change (for example, when an event status changes from "Assessing" to "Closed").

  • The purpose of the entity_modified_date field is to capture modifications made specifically to the site-event entity, such as:
    • Changes related to impacted sites 
    • Supplier response updates 
    • Site-level event information changes 
    • Other updates associated with the site-event relationship

  • Event status changes are considered event-level updates and are not reflected through the entity_modified_date field in the site_events API response.

  • To capture all event-level changes, including event status updates, users should refer to the event_last_modified_date field available in the event_sites API endpoint.

  • The event_last_modified_date field should be used when tracking the latest updates to an event, ensuring that changes such as event status transitions are captured accurately.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article