scheduleop schema
scheduleop schema
Currently in scheduleop schema there is no datatimestamp,so how can we track while syncing the updations and deletions of that particular schema entries?
Re: scheduleop schema
I don't see a reason why an application would need a 1:1 instantaneous, in sync cache of scheduleop data. Most developers query for relevant data at the time of display/use.
Re: scheduleop schema
Hi,
We are currently building a sync from onpremise to local system inorder to reduce api latency issues ,so we need real time syncing from scheduleop schema ,it doesnt have timestamp,so is there any other ways to know the updations and insertions.
We are currently building a sync from onpremise to local system inorder to reduce api latency issues ,so we need real time syncing from scheduleop schema ,it doesnt have timestamp,so is there any other ways to know the updations and insertions.
Re: scheduleop schema
If you are creating a local application, the Local or Services modes of the API are recommended. These return larger JSON payloads than the Remote mode and, because it never leaves your network, execute in just a few milliseconds. If this is how your office and application are already set up and you're experiencing latency, that likely points to high database traffic, over server load, etc. instead.
Most applications will only query for scheduleops relevant for their use case, as it is a linker table. I recommend API Guide - Finding Appointment Openings if it pertains to your use case or otherwise posting in the API forum, if that is your type of integration.
Most applications will only query for scheduleops relevant for their use case, as it is a linker table. I recommend API Guide - Finding Appointment Openings if it pertains to your use case or otherwise posting in the API forum, if that is your type of integration.