-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data loss when saving Cases when no prior records exist #47
Comments
This isn't good. Only on Cases? |
And only on an empty list? |
I've only had this happen on Cases, and only on an empty list. If RubyZoho is initialized with an empty list, any cases will be messed up. If it's initialized when there are 1 or more, it works fine.
|
That's just plain weird. Because every class except for User is created dynamically based on the initializer and all of the code is shared. I wonder if this happens on any empty list? That would clearly make it a bug. If it's just Cases then it probably in Zoho's API logic. Have you tried an empty list anywhere else? |
It could be. I'm unable to test it because this is an Enterprise level But, the Cases module behaves differently than most others so I wouldn't be
|
Right. Thanks. I'm not sure how to proceed. Could turn logging on I suppose to see what's happening. Or I guess the work around, which is ugly, is to add a record manually. |
In order to reproduce this, add "Cases" to the module list and make sure there are no cases records in Zoho.
This will create a record, but none of the field data is saved (all blank). Now if you re-run the script with the existing record it will work fine.
It looks like something isn't being initialized, because you have to reload RubyZoho for it to work, i.e. creating 2 records from scratch doesn't save correctly.
The text was updated successfully, but these errors were encountered: