For complex topics that regular users would not be interested in. For power users and database administrators.
-
rinse-dental
- Posts: 103
- Joined: Wed Apr 06, 2022 12:04 pm
Post
by rinse-dental » Sat Aug 31, 2024 6:51 pm
I'm an avid user of the Open Dental APIs and have had success frequently updating our server to the latest beta version. Two weeks ago I updated to version 24.2.n (I can't recall the subversion) and everything imploded... stack trace errors galore and any APIs ShortQueries hitting the Planned Apts table died which killed our patient web/apps. It was late and I was in a panic, so I just restored to a recent backup and didn't grab any notes on the stack trace errors.
Before I take another stab at an upgrade I know I need to rewrite my PlannedApt short queries. Is there anything else I should be thinking about?
(sorry for the general question and no detail - I recognize it's a bit of a stab in the dark. I'm hoping there a few simple known resolutions outside of 'try again and call support')
-
SLeon
- Posts: 553
- Joined: Mon Mar 01, 2021 10:00 am
Post
by SLeon » Tue Sep 03, 2024 8:31 am
Good morning,
The PlannedAppt table was dropped in 24.2. It was replaced with the ItemOrderPlanned field in the Appointment table. You can see this change in our schema
here.
Previously, there wasn't a way to obtain Planned Appointment data via the API outside of Queries PUT ShortQuery. Now you can use Appointments GET (multiple) with an AptStatus of "Planned". However, I recognize you will likely prefer to edit your query instead. This should be straightforward, and the NextAptNum paradigm you may or may not have been leveraging before is unchanged.
Happy to elaborate if needed.
-
rinse-dental
- Posts: 103
- Joined: Wed Apr 06, 2022 12:04 pm
Post
by rinse-dental » Fri Sep 13, 2024 6:54 pm
Appreciate the response. Realizing this is too generic a question, I'll ask anyway... is there any reason for (or have there been any reports of) the Open Dental client dying after the upgrade? We use planned visits heavily so I'm concerned all those stack trace errors I was receiving was related to Planned Appointments.
-
rinse-dental
- Posts: 103
- Joined: Wed Apr 06, 2022 12:04 pm
Post
by rinse-dental » Fri Oct 25, 2024 10:02 am
Update for anyone facing the same issue. In short, after upgrading our server to v. 24.2.44, when we attempted to open the client, the clients would crash during load and before offering the option to upgrade. The work around was to manually upgrade via the setup.exe file found in the AtoZ folder.
The error was a sql stack trace.
