Resource ID not correct handled

[Arwin]

Hi,

I'm a problem with the resourceview in Vue and I think it is a bug. I created a Javascript example: https://stackblitz.com/edit/saaovh?file=index.js

You see i added 1 appointment with ConferenceId: 12. Now the appointment is shown at resource Id 12, but also resource Id 2? Same with 13, 3 or 14, 4 etc. Hopefully you can provide a fix.

[Karthigeyan Krishnamurthi]

Hi Arwin, 

 

Greetings from Syncfusion. 

 

We could reproduce the reported issue and logged the below bug report. The fix will be included in our JS2 weekly release on April 30, 2019. 

https://www.syncfusion.com/feedback/5817/event-not-rendered-properly-with-allowgroupedit-when-the-resource-id-is-two-digit 

 

Regards, 

Karthi 

 

 

[Arwin]

Hi Karthi,

I just updated de ej2-vue-schedule to version 17.1.43, but it didn't fix anything. Do we have to wait another week? If so, is there a quick fix that we can implement so we can release the new calendar?

[Vinitha Devi Murugan]

Hi Arwin, 

 

Sorry for the inconvenience.  

  

We are working on it with high priority and the fix will be included in our JS2 weekly release on May 07, 2019. In the meantime, we suggest you to use the single digit resource id instead of two digit. 

  

We highly appreciate your patience until then.  

  

Regards,  

M. Vinitha devi. 

[Arwin]

Hi M. Vinitha devi.

I just updated the package to 17.1.44 but still the same problem. I thought that you are working on it with a "high prio"?

"In the meantime, we suggest you to use the single digit resource id instead of two digit." That is not a solution for us (with more than 10 resources), so we are just waiting..

Hopefully you can provide a quick fix.

[Karthigeyan Krishnamurthi]

Hi Arwin,  

  

Sorry for the inconvenience. 

 

We have fixed the issue but the fix is not included in May 7, 2019 weekly release. We will include the fix in May 14, 2019 and would appreciate your patience until then. 

 

Regards,  

Karthi 

[Arwin]

Hi Karthi,

I am very disappointed that you promise to solve it twice and that it has not been resolved again. I pulled version 17.1.47 from May 14 but the problem still exists.

How can this happen if you say the problem has already been solved?

[Vinitha Devi Murugan]

Hi Arwin, 

 

We regret for the inconvenience caused. The reported issue has been fixed and included in our weekly patch release (v17.1.48) and same can be checked in the following sample. 

 

https://stackblitz.com/edit/angular-skefuk-4qwynd?file=app.component.ts 

 

Regards, 

M.Vinitha devi. 

[Arwin]

Still the same problem....

https://codesandbox.io/s/7su5q

With "allowGroupEdit: true".

[Karthigeyan Krishnamurthi]

Hi Arwin, 

 

Thanks for the update. 

 

When allowGroupEdit is enabled, the resource id field should be in array. We have modified your sample which is working correctly. 

https://codesandbox.io/s/vue-template-9tc1s 

 

let data = [ 

  { 

    Subject: "Paris", 

    StartTime: new Date(2018, 5, 5, 10, 0), 

    EndTime: new Date(2018, 5, 5, 12, 30), 

    ConferenceId: [14] 

  } 

]; 

 

Note: CRUD will not work unless Id field is added to above event. 

 

Regards, 

Karthi 

[Arwin]

Strange behaviour but it works now. Thanks!

[Karthigeyan Krishnamurthi]

Hi Arwin,

We are happy that our solution resolved your issue.

When allowGroupEdit is enabled, we can assign same event to multiple resource by just giving the resource id values with in array. For this reason only resource field is defined as array type in the event collection.

Regards,

Karthi