Breaking out forum topic 314 into separate posts for each proposed Op.
Create
The create op is used to post new recs to the Haystack Server. It is the client's responsibility to maintain the remote references. Therefore, the client should post new recs of different types in different requests. In other words, the client should post new site recs prior to posting new equip recs that belong to those sites, and post new equip recs prior to posting new point recs that belong to those equips. This will allow the client to maintain and transform remote references. The client should maintain those remote references by adding the remote server id as an hsid property.
Request: a grid of records containing all recs to be added to the server. The client may pass its own internal id as an hsid so the server contains a reference to the remote record, but this should not be required.
Response: order consistent grid containing all recs that were added to the server with an "id" column being added to represent the server specific id of each rec. An "err" column should also be added so any rows that encountered an error during creation can report such error. It is assumed that rows with a defined "err" entity would not return an "id" entity.
Example:
Here is an example which posts some new recs to the server:
Shawn Jacobson Tue 8 Sep 2015
Breaking out forum topic 314 into separate posts for each proposed Op.
Create
The create op is used to post new recs to the Haystack Server. It is the client's responsibility to maintain the remote references. Therefore, the client should post new recs of different types in different requests. In other words, the client should post new site recs prior to posting new equip recs that belong to those sites, and post new equip recs prior to posting new point recs that belong to those equips. This will allow the client to maintain and transform remote references. The client should maintain those remote references by adding the remote server id as an hsid property.
Request: a grid of records containing all recs to be added to the server. The client may pass its own internal id as an hsid so the server contains a reference to the remote record, but this should not be required.
Response: order consistent grid containing all recs that were added to the server with an "id" column being added to represent the server specific id of each rec. An "err" column should also be added so any rows that encountered an error during creation can report such error. It is assumed that rows with a defined "err" entity would not return an "id" entity.
Example:
Here is an example which posts some new recs to the server:
Questions: