Hi,

Unfortunately it is not supported yet, for now it is supported for integer datatype or other numbered datatype. The explanation is, everytime user creates an event in WebScheduler, the event will be saved in database and identity of the new record added will be passed back to server.
The identity will be used for editing and deleting event in WebScheduler, if you use data with string datatype the database can't return identity which can cause an error while editing and deleting event.

Maybe you can explain why you need to use string rather that to use integer datatype? Maybe there is some workaround for it.

Best Regards,

Dicky

Thanks Dicky,

I've already had a workaround solution.

Hi Huy,

I have the same problem, is ti possible for you to explain me your workaroun?

Thanks in advance,

Vince.

Perhaps I could offer a workaround for such scenario. 

Currently WebScheduler will need an ID column with numeric data for reasons that has been explained by my colleague. Since you will need an ID column with string data, you could have 2 column ID one for the numeric data which is need for WebScheduler processing and the other one will hold the string data for your own processing.