Page 1 of 1
Question | After upgrade to 24.2.n, API Event - Appointment ran for every apt in DB
Posted: Fri Oct 25, 2024 10:13 am
by rinse-dental
After my upgrade to 24.2.44 (from 24.1.n), it appears my API Event - Appointment fired for every appointment in the DB. Is this to accommodate the new ItemOrderPlanned field? Was there any other updates/changes made to the appointments as part of this upgrade? The volume killed my listener and I'm trying to determine if I need to rerun the jobs.
Re: Question | After upgrade to 24.2.n, API Event - Appointment ran for every apt in DB
Posted: Fri Oct 25, 2024 10:56 am
by SLeon
Good morning,
Yes, that is correct. ApiEvents will fire for
any change to the appointment table (as the logic specifically queries for the DateTStamp). This includes queries in our update scripts, such as the ItemOrderPlanned column we added in the 24.2.1 conversion script. This was the only query ran on that table for 24.2.1-24.2.44.
Here is a link to our
source code so you can verify this, and also see if anything else occurred for 24.1.n+. This source code is kept in sync with our released versions, so you can always eye these before major version updates, to see what you might need to prepare for.
Re: Question | After upgrade to 24.2.n, API Event - Appointment ran for every apt in DB
Posted: Fri Oct 25, 2024 11:38 am
by rinse-dental
Amazing. Thank you!