It is possible to create ParseObject(s) with a predefined ObjectId. This allows for use cases where Parse is not the system of record of the IDs of entities are defined in some external system.
This is done by calling the standard POST /classes/{className} API but specifying the "objectId" as a parameter of the object being submitted NOT by calling the PUT /classes/{className}/{objectId}
The Parse-SDK-dotNET does not allow this. If you specify an ObjectId on an object, it will attempt to use the PUT API and update the object failing to create the object.
The ParseJS SDK uses the presence of the "createdAt" property to know if it was ever retrieved instead of using the ObjectId to determine if PUT or POST should be used.
parse-github-assistant[bot]
commented
1 month ago
As implemented in Parse server: https://github.com/parse-community/parse-server/pull/6177 and in the Parse JS client: https://github.com/parse-community/Parse-SDK-JS/pull/1309
It is possible to create ParseObject(s) with a predefined ObjectId. This allows for use cases where Parse is not the system of record of the IDs of entities are defined in some external system. This is done by calling the standard POST /classes/{className} API but specifying the "objectId" as a parameter of the object being submitted NOT by calling the PUT /classes/{className}/{objectId}
The Parse-SDK-dotNET does not allow this. If you specify an ObjectId on an object, it will attempt to use the PUT API and update the object failing to create the object.
The ParseJS SDK uses the presence of the "createdAt" property to know if it was ever retrieved instead of using the ObjectId to determine if PUT or POST should be used.