I am looking for some architectural guidance on a Tryton implementation.
I have two external API endpoints:
The first endpoint returns a list of car models for a specific brand.
The second endpoint returns detailed information for a specific model selected from that list.
My goal is to display this information inside Tryton without persisting any data to the database. Ideally, the workflow would look like this:
The user types a brand (e.g., “BMW”).
Tryton displays a tree view with the corresponding rows (e.g., X1, M3, Z4).
When the user selects a row, Tryton fetches and displays the detailed view for that specific model.
Which components would best suit this requirement? Is it possible to use a ModelView tree without ModelSQL for this, or should I approach it differently?
Yes, for that reason we have ModelStorage to define a generic storage.
You can create any subclass that extends ModelStorage and implements the needed operations.
With such workflow in mind I will consider having a wizard that guides the users througth each step of your workflow. Proably it will be simpler that implementing a custom storage not based on ModelSQL.
Thanks both for your answers, I’ll take into account each one, so inside a wizard I can create kind of a tree view to list tabular data? I was thinking like a Function field as well for these purpose.