Write many records

From server version >7304

To write many record, you must have right to the data and use the maindata url to update them using a HTTP PUT command and create a new record using a HTTP POST command. The format of the url is; /maindata/tablename/recno/?dataeaseqyery&othersetting= etc.

/listdata/ tells the server to give you one record of the selected table.
/tablename/ tells what table to fetch the data.
[/recnostart/] tells the record to start updating based on the query.
[/recnoend/] tells the record to and updating

The query format is the same as for any other query in server. The first part between ? and the first & is a query as your write it in DataEase. This mean you can write a Name="A*" to get all records with a text field starting on A. You can also use all other operators like AND, OR, BETWEEN, >, >=, <, <=, =, not = etc. So if you want a record where Name starts on A and regdate is between to dates your write "Name="A*" AND regdate between 10/10/20 to 12/10/20". If you want to get the results in acending or decending order based on a field, you add this as "&regdate=in order".

Ex. /listdata/Address/0/10/?Name="A*" AND regdate between 10/10/20 to 12/10/20&regdate=in order

This query will return records matching Name="A*" and reg date between the 10/10/20 and 12/10/20 in acending order on regdate. 

The payload you send to the server should have the format application/json and be structured like this:

{ 	
  'listdata' : [
    {
      'Name' : 'Bjorn',
      'Country' : 'Norway',
      'Street' : 'Smal smauet',
      'Postno' : '1234',
      'PostAddr' 'Lillesand'
    },
    {
      'Name' : 'Ulrik',
      'Country' : 'Norway',
      'Street' : 'Veien 2',
      'Postno' : '9876',
      'PostAddr' 'Storesand'
    },
  ]
}

The return value from the PUT or POST is the same as from list data. It will return all updated records as you sent, so you can not rely on this number when doing a subsequent query unless you are the only user of the system. The data is reread from the multiview to reflect any triggered derivations on the original table.