You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
beforeSave renders Relation column on object invalid on response.success() #1714
Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities. For database migration help, please file a bug report.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Apparently the problem occurs when a beforeSave cloud function returns response.success() instead of response.success(request.object). When using the former on an object that contains a PFRelation, that PFRelation get's screwed up on the client side (becomes PFRelationOperation).
Unfortunately just using response.success(request.object) is not the solution. Using this will keep the PFRelation field intact but it will not save any data defined in the cloud function beforeSave method.
Here MyObject will not save (or create) the 'colorstring' column.
Here MyObject will save (or create) the 'colorstring' column and it will show up on the dashboard. But will render any PFRelation column on MyObject useless.
Activity
flovilmart commentedon Jul 13, 2016
Will be fixed by #1946,
Closing as duplicate of #1606