There are a couple of common ways to search a datastore, directly in the datastore console and using bridges.
When each datastore is configured, it can be given a default search, so a search is automatically done and those results are displayed when the datastore is opened in the console. However, this is not required and, even if a default search is provided, the advanced search options are always available. This allows users with access to the datastore to be able to do searches by any field for
- Starts with
- Equal To (can specify more than one value)
- Greater Than
- Less Than
- Greater Than or Equal To
- Less Than or Equal To
- Is Between
And display the results in ascending or descending order. Note that not all the fields on the records will display in the initial table of results that display. Only the fields specified in the configuration as "Visible In Table" will display here.
You can export the records using the three vertical dots next to the New Record button at the top right of the screen. Once a record is selected from the table, you can see all of the fields in that datastore exactly as they were laid out using the form builder. Also, from this view, you can page between search results.
When you are using the datastore values in a Service or Task, whether you are pulling back one or multiple values, you are doing a search on the datastore. This is generally done using bridges. The beauty of this is that it allows any complexity to be on the one-time configuration side, and all of the user has to do is set up and use the bridged resource just like any other bridged resource.
And, as with any other bridge, all of the defined queries are available to the user. All the user has to do to leverage them is to pass the requested parameters:
And then the user can use that bridged resource on any change event or dynamic list. This allows the form builders to be able to search the datastore data without having to understand it, as with any other bridged item.
Updated about 1 year ago