Making changes to existing events triggers fetch of current week.

[Diego Rubio]

Hello,

I have noticed that after we make changes to an existing event the crudUrl is called as expected but then url from DataManager gets called too, even if crudUrl returns the new updated events.

let dataManager: DataManager = new DataManager({

          url: `${this.environment.api}contractor/v1/${this.user.id}/get-schedule-control`,

          crudUrl: `${this.environment.api}contractor/v1/${this.user.id}/update-schedule`,

          headers: [{ Authorization: 'Bearer ' + this.user.access_token }],

          adaptor: new UrlAdaptor

      });

How we can avoid the extra call to our API?

Thank you!.

[Balasubramanian Sattanathan]

Hi Diego Rubio, 

 

Greetings from Syncfusion Support. 

 

We have validated your reported scenario at our end. We let you know that, at the time of initial rendering of events the Url will trigger for fetching the events from the DB. If we perform CRUD actions (like create/edit/delete events) the CrudUrl will trigger for create/update the data(i.e., events) in the table of the DB and then the Url will trigger for fetching the updated events from DB to the client end. Kindly refer the below UG for further reference. 

UG : https://ej2.syncfusion.com/angular/documentation/schedule/data-binding/#scheduler-crud-actions   

Please get back to us, if you have any concerns. 

Regards, 

Balasubramanian S 

[Diego Rubio]

Hello Balasubramanian S,

If crudUrl is already getting the updated events why is the need to fetch URL again after crud operations, we want to avoid that.

Thanks.

[Balasubramanian Sattanathan]

Hi Diego Rubio, 

 

Thanks for the update. 

 

We regret to let you know that, there is no possibility to avoid the URL calls when we update the events. According to the Schedule architecture, Url will be triggered whenever the data is updated to the DB through CrudUrl.  

 

Please let us know if you have any concerns 

 

Regards, 

Balasubramanian S