Stryke Changelog

Version 0.22.0

CSV Data import enhancements

CSV data import is now available from the default Stryke User Interface under the records list views.

Import button

When developing an app, you can control which entities support records import via the canImportRecords field in the entity metadata. canImportRecords can be edited via the API and via the Stryke user interface under the entity edit screen.

Governor limits have been introduced to control the number of records that can be imported in a single request. Currently, standard subscriptions can import up to 100 records in a single request, whether it is from JSON or CSV payloads.

Version 0.21.0

Lists pagination, filtering and sorting enhancements

Lists have been enhanced in the standard Stryke user interface to support server side pagination (this leverages Stryke's GraphQL API). This dramatically improves the performance of the client for apps that have many records.

Version 0.20.0

Version 0.20.0 brings a lot of powerful enhancements and fixes but contains a breaking change that may require you to update some of your GraphQL queries (in API calls or scripts). If you are using queries with lookup fields in the filter criteria please have a look below at how you should update your code.

  • Stryke query enhancements
    • query by fields of related record (id, alias)
    • LIKE and NOT LIKE operators
    • OFFSET parameter
  • Import data from CSV files
  • App logs API

Stryke query enhancements - Breaking change

Stryke v0.20.0 brings quite a few important enhancements to the GraphQL queries that can be performed via the API or through scripts.

Filter by fields in a related record - Braking change

Until v0.20.0 queries could filter by lookup filed only using the ID of the related record.

The example below performs a query to retrieve all receipts related to a given business as supported by Stryke up to version 0.19.0.

// Stryke v0.19.0 and previous
{
  Receipt(
      filter: { business : { eq: "cca1f06a-985b-4f41-a27d-3df64aac1f50" } }      
    ) { 
    id 
    alias 
    amount 
  }
}

Starting with v0.20.0 the above query needs to be changed to:

// Stryke v0.20.0 and above
{
  Receipt(
      filter: { business : { id: { eq : "cca1f06a-985b-4f41-a27d-3df64aac1f50" } } }      
    ) { 
    id 
    alias 
    amount 
  }
}

This syntax change allows to extend the query to have a criteria that refers to fields other than the ID field. For example:

// Stryke v0.20.0 and above
{
  Receipt(
      filter: { business : { alias: { like : "%shop%" } } }      
    ) { 
    id 
    alias 
    amount 
  }
}

The query above retrieves all receipts whose related businesses contain the word "shop" in their alias.

Currently only the id and alias fields can be used in filter criteria. For more details on query filters and how to apply this new approach see the query docs.

LIKE and NOT LIKE operators

The LIKE operator allows to search for partial string values using '%' wildcards.

See docs for details.

OFFSET parameter

The OFFSET parameter allows to offset the result of a query by 'x' number of records. This is especially useful for paginating records together with the limit parameter.

OFFSET and LIMIT parameters are available in both the Query by filter as well as the Query all queries.

CSV Data import

Starting from Stryke v0.20.0 data can be imported from CSV files using the /data/importdataset endpoint.

Data can be imported for a specific entity at a time. This means that a single CSV file being imported can only contain records for a specific entity. The entity for which records are being imported is specified as a request parameter in the request itself.

The CSV file needs to have as headers the fields of the entity being imported. If more fields are included in the CSV they will be ignored. Stryke will only import data for the fields it recognises for the entity being imported.

If a record being imported has a lookup to another record the CSV data needs to include the valid ID of the lookup record.

Example

Importing records of entity "receipt"

amount,receiptDate,type,business
12.5,2020-02-29T11:34:38.000Z,be4c9be7-74c9-4026-a241-51439bf199b4,
2.5,2020-02-29T12:00:03.000Z,,d0be016f-1ad3-43ad-a387-6aa1e74f682b
10,2020-02-28T11:12:38.000Z,ddef0c02-8587-437a-a2dd-0faf669db305,d0be016f-1ad3-43ad-a387-6aa1e74f682b
52,2020-02-28T19:50:38.000Z,ddef0c02-8587-437a-a2dd-0faf669db305,eb0a4a77-d416-44eb-9399-2ad91d842ac1
5,2020-02-28T18:50:38.000Z,,df9b54cc-639d-42e8-a7e2-04a073f3ab23
7.25,2020-02-27T12:54:38.000Z,,df9b54cc-639d-42e8-a7e2-04a073f3ab23
2.5,2020-02-26T15:25:38.000Z,,df9b54cc-639d-42e8-a7e2-04a073f3ab23
45,2020-01-29T14:25:38.000Z,,df9b54cc-639d-42e8-a7e2-04a073f3ab23
125,2020-01-26T22:59:38.000Z,f4184d59-44c5-4618-b3b6-c759132a35fa,6450cd2f-19a2-4b1d-8bf1-5072851e9a62
1.75,2020-01-13T13:03:38.000Z,f4184d59-44c5-4618-b3b6-c759132a35fa,6450cd2f-19a2-4b1d-8bf1-5072851e9a62

Currently, create triggers will not run when importing records via the /data/import or /data/importdataset endpoints.

App logs API

Stryke v0.20.0 provides a new API to retrieve logs from your app instance. These logs allow you to review and debug activity of your app. The logs API is only accessible by Stryke users and it will return logs for each operation performed against one of your apps (CRUD, script execution, etc).

The app logs API can be accessed via:

https://api.stryke.io/v0/[appinstance]/app-log

← The Playground appCreate a new App →