Our pure JavaScript Scheduler component


Post by nsarvesh14 »

Hi Team,
We are looking for one example on how "sync" works
Tried looking into the trial downloaded and the examples mentioned on the website. But no luck worked
Also, can you please confirm
If a user modifies the existing events Will the sync automatically triggers either in EventStore, ResourceStore, or through the CrudManager?

How do we pass the data to the backend?

We are tried multiple options like below

 eventStore : {
        readUrl  : 'https://<>/events.json',
        autoLoad : true
    },

resourceStore : {
    readUrl  : 'https://<>/resources.json',
    autoLoad : true
},

crudManager : {
    autoLoad : true,
    autoSync:true,
    transport : {
    load : {
                url : 'https://localhost:8090/byndata/data.json' 
            }
    },
    sync: {
        url: 'https://localhost:8090/byndata/ioupdate.json',
        method: 'POST'
    }
   },

Post by mats »

Please use CODE tags when posting code.

You should not specify individual stores and crud manager, but use either or. Please read this guide: https://www.bryntum.com/docs/scheduler/#guides/data/crud_manager.md


Post by nsarvesh14 »

Sure. We are using a crud manager.

crudManager : {
    autoLoad : true,
    autoSync:true,
    transport : {
    load : {
                url : 'https://localhost:8090/byndata/data.json' 
            }
    },
    sync: {
        url: 'https://localhost:8090/byndata/ioupdate.json',
        method: 'POST'
    }
   },

It will be great if you have any working examples. We are close to complete the evaluation. This really helps!
Since our new customers are having huge datasets. Instead of calling ajax for every request for every event change, we can leverage this feature. The user experience will be good.


Post by nsarvesh14 »

Please ignore it. Will try out an example and revert back in case of any issues.
But this feature I liked it. Instead of calling backend every time we can leverage this.


Post Reply