Bug - SfScheduler causes a null reference exception when accessing CSLA managed properties
Hi,
As the subject suggests there is an issue accessing managed properties in the SfScheduler. I have attached an example with 4 scenarios accessing the same business list object:
- Basic text list
- SfScheduler
- SfGrid
- SfScheduler (Without managed property)
Attachment: SyncfusionBlazorCsla6__SfScheduler_error_9126ed75.zip
Hi Lee,
Sorry for the delay,
Due to the complexity of the issue, we need additional time to validate the reported issue at our source end. So, we will check and update it by Monday, June 5, 2023. Appreciate your patience until then.
Regards,
Swathi Ravi
Hi Lee,
Sorry for the Delay.
We had checked your query at our end. The issue with managed properties were
caused because, we had processed each occurrence appointments using Activator.CreateInsance
from the parent recurrence appointment at our source end. Since in CSLA 6,
Activator.CreateInstance will create this runtime exceptions and the same works
fine in CSLA 5. We prepared a sample for your reference in CSLA 5. To resolve
the issue in CSLA 6, we suggest you to define the Appointment model class without
managed properties.
You can find more details about this exception in below link:
https://github.com/MarimerLLC/csla/blob/main/docs/Upgrading%20to%20CSLA%206.md#factory-data-portal-models
Regards,
Mugilraj G
Attachment: BlazorApp_ea09bbf2.zip
Hi Mugilraj,
Thanks for your detailed response. I have removed the backing fields and that seems to work with the calendar now. Are there any other Syncfusion components that function in a similar way? For example, we never had the problem with the SfGrid when using the same business object.
Thanks, Lee.
- 4 Replies
- 4 Participants
- Marked answer
-
LS Lee Stevens
- May 25, 2023 03:24 PM UTC
- Jul 7, 2023 08:14 AM UTC