Adding to resourceStore and resourceTimeRangeStore doesnt update reference

[jsakalos]

When a record is added to resourceStore with the same id as an already existing record, the existing record is replaced by the new one which breaks its relation to resourceTimeRangeStore record.

Steps to reproduce:

1. https://bryntum.com/examples/scheduler/resourcetimeranges/
2. in console:

scheduler.resourceStore.add( { id : 'r1', name : 'Mock' });

3. drag the first event

The existing resource time range disappears. The situation should be handled, either by removing resource time range record or updating behind the scenes.

Forum post

Hey!

Im running a useEffect hook where im dynamically updating resourceData (1 to many fields) using the resourceStore.addAsync() function it removes that resources resourceTimeRange.

Ive tried a few workArounds, and the only one that seems to work is the very bruteforcy way of doing a setAsync(); func on the Resource itself, which seems wrong to me.

I have recreated this issue in https://bryntum.com/examples/scheduler/resourcetimeranges/

where Ive changed the "add resource" btn onclick to this:

onAction : () => {
                scheduler.resourceStore.add( { id : 'r1', name : 'Mock' });
scheduler.resourceStore.add( { id : 'r2', name : 'Mock' });
            }
            

It looks fine when u click it (the name changes of the resource) but when u interact with the scheduler (either moving timeRanges to lunch or just simply moving an event) the resources timeRanges disapear.

-----OurImplementation-----
the project is set up like this:

    project: {
      eventStore: new EventStore(),
      resourceStore: new ResourceStore(),
      resourceTimeRangeStore: new ResourceTimeRangeStore(),
    },

the "this should work" tries

  useEffect(() => {
    if (updatedWorkShift) {
      const addToResourceStore = async () => {
        await props.planningSchedulerRef.current.resourceStore.addAsync(updatedWorkShift);
      };
      
  addToResourceStore();
}
  }, [updatedWorkShift]);

  useEffect(() => {
    if (updatedWorkShift) {
      const addToResourceStore = async () => {
        props.planningSchedulerRef.current.resourceStore.add(updatedWorkShift);
        await props.planningSchedulerRef.current.project.commitAsync();
      };
      
  addToResourceStore();
}
  }, [updatedWorkShift]);

  useEffect(() => {
    if (updatedWorkShift) {
      const addToResourceStore = async () => {
        props.planningSchedulerRef.current.resourceStore.add(updatedWorkShift);
        const updatedTimeRanges = updatedWorkShift.map((workShift) => ({
          resourceId: workShift.id,
          startDate: dateUtils.addHours(workShift.workShiftStart, -2),
          endDate: dateUtils.addHours(workShift.workShiftEnd, 2),
        }));
        props.planningSchedulerRef.current.resourceTimeRangeStore.add(
          updatedTimeRanges,
        );
        await props.planningSchedulerRef.current.project.commitAsync();
      };
      
  addToResourceStore();
}
  }, [updatedWorkShift]);

  useEffect(() => {
    if (updatedWorkShift) {
      const addToResourceStore = async () => {
        props.planningSchedulerRef.current.resourceStore.add(updatedWorkShift);
        const updatedTimeRanges = updatedWorkShift.map((workShift) => ({
          resourceId: workShift.id,
          startDate: dateUtils.addHours(workShift.workShiftStart, -2),
          endDate: dateUtils.addHours(workShift.workShiftEnd, 2),
        }));
        await props.planningSchedulerRef.current.project.commitAsync();
        
    props.planningSchedulerRef.current.resourceTimeRangeStore.add(
      updatedTimeRanges,
    );
    await props.planningSchedulerRef.current.project.commitAsync();
  };
  
  addToResourceStore();
}
  }, [updatedWorkShift]);

[acpanackal]

Is this bug fixed?

I was trying with 'loadDataAsync' and 'addAsync' to update ResourceStore.

When I use 'loadDataAsync' there is a flicker after polling
When I use 'addAsync' flicker is gone but ResourceTimeranges disappear on polling. any idea?

[matsbryntse]

Not yet fixed but we'll try to get this sorted out shortly!

[acpanackal]

Wow so happy to see that it's ready for review. Would really appreciate it if it's online and available. Because the scenario is very irritating for our customers.

We do have a Premium Account but I messaged here since I think my Issue is well explained here.

Thanks :)