Another example
Please be sure of your agent type and version and pick the right documentation accordingly.
This is the documentation of the forest-express-sequelize and forest-express-mongoose Node.js agents that will soon reach end-of-support.
forest-express-sequelize v9 and forest-express-mongoose v9 are replaced by @forestadmin/agent v1.
Please check your agent type and version and read on or switch to the right documentation.
This is still the latest Ruby on Rails documentation of the forest_liana agent, you’re at the right place, please read on.
This is the documentation of the django-forestadmin Django agent that will soon reach end-of-support.
If you’re using a Django agent, notice that django-forestadmin v1 is replaced by forestadmin-agent-django v1.
If you’re using a Flask agent, go to the forestadmin-agent-flask v1 documentation.
Please check your agent type and version and read on or switch to the right documentation.
This is the documentation of the forestadmin/laravel-forestadmin Laravel agent that will soon reach end-of-support.
If you’re using a Laravel agent, notice that forestadmin/laravel-forestadmin v1 is replaced by forestadmin/laravel-forestadmin v3.
If you’re using a Symfony agent, go to the forestadmin/symfony-forestadmin v1 documentation.
Please check your agent type and version and read on or switch to the right documentation.
Another example
For the purpose of this example let's say we have an activity-logs index in Elasticsearch with the following mapping.
{
"mappings": {
"_doc": {
"dynamic": "strict",
"properties": {
"action": {
"type": "keyword"
},
"label": {
"type": "text",
"index_options": "docs",
"norms": false
},
"userId": {
"type": "keyword"
},
"collectionId": {
"type": "keyword"
},
"createdAt": {
"type": "date"
}
}
}
}
}Creating the Smart Collection with related data
First, we declare the activity-logs collection in the forest/ directory.
In this Smart Collection, we want to display for each activity log its action, the label (in a field description), the related user that made the activity, the collectionId on which the activity was made and the date the activity was made by the user.
You can check out the list of available field options if you need them for your own case.
Implementing the GET (all records with a filter on related data)
This is a complex use case: How to handle filters on related data. We want to be able to filter using the user.mail field.
To accommodate you we already provide you a simple service ElasticsearchHelper that handles all the logic to connect with your Elasticsearch data.
Implementing the GET (all records with the search)
Another way to search through related data is to implement your own search logic.

Last updated
Was this helpful?