We are just trying to use the groupings and locking row feature in the scheduler, but for some reason, the display is not as we expected. The locking rows feels like cloning the whole content of the grid and not rendered correctly. Can someone help me with this. Thank you!
Sample code of the implementation:
<Bryntum
...
groupFeature={{
field: `virtualUserType`,
ascending: false,
}}
lockRowsFeature={{
fieldName: 'fixed'
}}
...
/>
Hi there,
I have tried to replicate the issue but was not able to do so. I have checked it on https://bryntum.com/products/scheduler/examples/lock-rows/. Attaching a clip to show the behaviour. Can you please check it and let us know if I missed something?
Also which version of bryntum you are using?
Regards,
Ghous
Hi Ghulam,
We have already seen the given example and applied it to our project, but it is still not working. Can you possibly write a sample code using the React version of the scheduler that implements groupings and locks rows together? Thank you!
As for a reference this is how we import all of the Bryntum scheduler packages for our react project.
export {
BryntumScheduler,
BryntumGrid,
BryntumSplitter,
BryntumCombo,
BryntumTimeField,
BryntumDateField,
BryntumDateTimeField,
BryntumTextField,
BryntumResourceCombo,
BryntumNumberField,
BryntumTextAreaField
} from '@bryntum/scheduler-react';
If I understand correctly, you are not using our api's to load data. If yes, then I am not sure which method you are using to load data into store. But the recommended way of doing that is using loadInlineData method https://bryntum.com/products/scheduler/docs/api/Scheduler/model/mixin/ProjectModelMixin#function-loadInlineData. Can you please try with this? If this does not work, can you share a small sample project with us? You can use the above example and add your bits of code into it.
Hi Ghulam,
Can't really share the exact code of the implimintation but this is how we add data to the store
<BryntumScheduler ref={scheduler} />
const addToSchedulerStore = ({ storeName, data }: IAddToStore) => {
if (scheduler?.current !== undefined) {
const { schedulerInstance } = scheduler.current;
return schedulerInstance.resourceStore.add(data);
}
};As you can see we access the scheduler instance and add data to the resourceStore using the add function.
Hi there,
I believe you will have to remove the records from the store as well, if there are any. But I have tried testing the feature with loading data using loadingInlineData and it works without any issues. We recommend using this method instead of add on the individual stores. Please check the clip and test app:
https://drive.google.com/drive/folders/1g23vFtcV-NsZ6TQgj89WhU_B81-lF-iM?usp=sharing
Hi Ghulam,
I think it will only work if the data are already completed. But on our case we loaded thousands of data and we process it by batch. That is why on our code, we used the .add method because it will just add the upcoming data from the old data in the scheduler. But on your example where having an issue implementing it. Thank yoU!
const addToSchedulerStore = ({ storeName, data }: IAddToStore) => {
if (scheduler?.current !== undefined) {
const { schedulerInstance } = scheduler.current;
return schedulerInstance.resourceStore.add(data);
}
};