resourceHeaderTemplate get re-render on state change

resourceHeaderTemplate get re-render on state change. Because of this every time it blinks and shows the data.

How to avoid rerending custom template.

Regards,

Sonam Diwate

Hi Sonam, 

 

Thank you for contacting Syncfusion support. 

 

In the below sample we have changed the state value on button click which will load the events in empty resource Scheduler without any blink. 

https://stackblitz.com/edit/react-9ab3ep-6xbsku?file=index.js 

 

If we misunderstood your requirement, kindly share your code example / sample(if possible) to proceed further and check whether your requirement is like below forum. 

https://www.syncfusion.com/forums/143048/blink-on-events-replace-with-grouping 

 

Regards, 

Karthi 

Could you please provide same example with data from server.

As we have a structure which calls a action from reducer and update state using getDerivedStateFromProps .

Regards,

Sonam Diwate

Hi Sonam, 

 

Thanks for your update. 

 

We have modified our previous sample to fetch the data from remote service and Schedule is working correctly. We request you to reproduce the issue in our sample and revert else share your code example / sample (if possible) to proceed further. 

https://stackblitz.com/edit/react-mh9znd?file=index.js 

 

Regards, 

Karthi 

 

and i have added simple state change event, but when we change the state "resourceHeaderTemplate" function get re render again and template data will not shown on the screen.

Could you help me to fix this issue and guide me what wrong I am doing.

Please click on change source button at top left of page to reproduce this issue.

Hi Sonam, 

We have checked your provided code example and could reproduce the reported problem at our end, which was suspected to be due to the “resourceHeaderTemplate” property is not properly handled during the set state changes. Currently, we are validating the scenario further related to this particular template property and therefore, in the mean-time, we suggest you to try our following highlighted code changes (by declaring a variable/property for the selectedDate and group properties and assign those variables to the respective APIs of the ScheduleComponent instead of directly assigning the value) which could also be referred from the below StackBlitz sample.  Also, further information regarding this issue validation will be shared from our side on March 29, 2019. 

Example: https://stackblitz.com/edit/react-xudhgx?file=index.js 

Kindly be patience, until we get back to you with the issue validation information.  

Regards, 

Hareesh B