Universal Windows Platform (UWP)
A Microsoft platform for building and publishing apps for Windows desktop devices.
2,903 questions
Best Practice for using AppointmentStore.StoreChanged in UWP app
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 70%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJF%3C/text%3E%3C/svg%3E)
Joseph Finney
1
Reputation point MVP
I develop a Calendar app for Windows 10 and I have been looking into using the AppointmentStore.StoreChanged API. During my testing I found when an Appointment is added to the AppointmentStore the Changed event fires 4 times. First for AppointmentCreated event then three more times for "AppointmentModified"
Why might this be happening? Is there a way to improve my usage of AppointmentStore to get a single AppointmentCreated when adding a single Appointment to a calendar?
I have created an AppointmentService to keep a single instance of the AppointmentStore in my app, but I still get multiple events when adding a single Appointment.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 46%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
AryaDing-MSFT 2,916 Reputation points2021-05-11T06:47:13.003+00:00 @Joseph Finney Drive from the official document about AppointmentStoreChangeType, AppointmentModified occurs when an appointment was modified, which indicates that the appointment has changed when adding an new Appointment. Therefore, could you please check your operations that related to modifing appointment?
-
Joseph Finney 1 Reputation point MVP
2021-05-11T15:42:48.637+00:00 The new appointment is built up then passed to the AppointmentStore.ShowEditNewAppointmentAsync(Appointment) method. This window launches a window allowing the user to review or edit any property of the appointment before it is added to the calendar. When accept is clicked on the window, that is when the StoreChanged events fire.
Because all of the properties are set by the ShowEditNewAppointment window I cannot add more properties to the new Appointment instance. The StoreChanged event seems to fire 4 times, (once new and three for edited) no matter what properties are selected in the edit appointment window.
-
AryaDing-MSFT 2,916 Reputation points
2021-05-14T09:17:28.79+00:00 @Joseph Finney I have tested it, but when I click the accept button on the window, the AppointmentStore_StoreChanged event is only triggered once. So could you please provide us a minimal reproducible example by OneDrive or GitHub?
-
Joseph Finney 1 Reputation point MVP
2021-08-02T14:59:28.827+00:00 Hello, I'm revisiting this because I have worked on building a minimal reproducible example. Here is the GitHub page.
https://github.com/TheJoeFin/AppointmentStoreReproBug
If you have any feedback on my implementation of the API I'd be happy to make changes or improvements.
-
Joseph Finney 1 Reputation point MVP
2021-11-16T14:58:15.14+00:00 Hello again, reaching out again because I have unhappy customers who are requesting refunds because this API is broken. I need an update!
Sign in to comment