Appointment Field Changes via API Trigger Integrity Warning – v24.3.50.0

[APIwarrior]

Hi all,

We’re running OpenDental v24.3.50.0, and I’m programmatically updating appointment fields (under ApptFields) using the API. However, when doing so, the change does not reflect in the appointment bubble UI, and I’m instead seeing the following Database Integrity Warning in OpenDental:

“This appointment was modified outside of OpenDental. There is most likely nothing to worry about. This modification was probably made by a third party program that you authorized. We are transitioning all third party programs to the API, but you may continue to see these notifications until that transition is complete.”

I just want to confirm:
1. Is updating ApptFields via the API fully supported in v24.3.50.0?
2. Is this integrity warning expected behavior even when using the official API?
3. Is there any known issue with changes not immediately updating the UI (e.g., requiring a manual refresh)?
4. Is there a better-supported method for updating custom appointment labels/tags (like “Verified”) that appear in the appointment bubble?

Appreciate any insights from the OD team or others who’ve run into this.

Thanks!

[SLeon]

Good morning,

The Database Integrity warning you saw says "this appointment", not "this appointment field". ApptFields are not considered in the "appointment" database integrity logic. Regardless of the message indicating a different table altogether, the API is designed to not produce these warnings within Open Dental.

Another engineer from the team will reply to your specific questions.

[justine]

Hi all,

We’re running OpenDental v24.3.50.0, and I’m programmatically updating appointment fields (under ApptFields) using the API. However, when doing so, the change does not reflect in the appointment bubble UI, and I’m instead seeing the following Database Integrity Warning in OpenDental:

“This appointment was modified outside of OpenDental. There is most likely nothing to worry about. This modification was probably made by a third party program that you authorized. We are transitioning all third party programs to the API, but you may continue to see these notifications until that transition is complete.”

I just want to confirm:
1. Is updating ApptFields via the API fully supported in v24.3.50.0?
2. Is this integrity warning expected behavior even when using the official API?
3. Is there any known issue with changes not immediately updating the UI (e.g., requiring a manual refresh)?
4. Is there a better-supported method for updating custom appointment labels/tags (like “Verified”) that appear in the appointment bubble?

Appreciate any insights from the OD team or others who’ve run into this.

Thanks!

Hello APIwarrior,

1. ApptFields was added in v21.1
2. No.
3. This should not be an issue. However, I will have an engineer verify this.
4. No.

Thanks!

[APIwarrior]

Thanks for the responses so far!

Just following up — I’ve confirmed the following:
• I’m successfully updating the Insurance ApptField via the API with the value "Ins Verified".
• In Definitions > Appointment Field Defs, I have an entry for Insurance with “Show in Bubble” checked.
• The spelling and casing match exactly: FieldName = "Insurance", FieldValue = "Ins Verified".
• I’ve restarted OpenDental and manually refreshed the UI.

Despite this, the “Verified” tag still does not appear in the appointment bubble UI. Is there any other configuration I might be missing to get the tag to display properly?

Would appreciate any further guidance!

Thanks again.