How to create a table containing the history of changes to a contract

I’m doing a project to manage events. I have some databases and the databases I’m using it for are the client database and the contract database. I created a page where to display a table to show the modification history of this contract. But my changes field shows the changes I make to all contracts and not the one I’m viewing. How can I solve this problem? Here are the screenshots

First in my workflow I am creating the contract.

Then I create a new history inside the Historic database
then steps 3 to 6 are to reset the inputs, hide the pop-up for creating a new contract and go to the page where my history table is.

on my table page the configuration is like this:


if i do it that way it will bring me all the contracts and i want only one. In reality, I would like to have a history of all changes within a contract, however, I have not been able to think of a solution for this.
I appreciate any help!

In Search for Históricos you should use a constraint to return only the specific contract.

You said that after creating a new history you are directed to the page where your history table is. In this case, are you somehow sending information to this page that identifies this contract and that you can use as a constraint for filtering your search?

Not. I don’t send the data to the page. How could I carry out this logic?

Depending on the structure of your app there are a few different ways.

If the page you refer to is really a new page, you can send data as parameters.

Workflow Actions > Navigation > Go to page > [Define page and parameters to send]

On the target page you will need to define the data source to match the same type of data you are sending, in addition to needing to retrieve this data from the URL.

For a better understanding, I advise you to read these articles:
1 - How To Send Data To A Page In Bubble
2 - Bubble URL Parameters

Otherwise, if the page you refer to is a group on the same page that is shown/hidden by some action or Custom State, then you can send data to it through the following steps:

Workflow Actions > Element actions > Display data (for groups) or Display list (for repeating groups) > [Define the element and data to be displayed]

In the case of a group, another alternative would be to send the data you need to a custom state in the group (or anywhere you prefer), and in the group or repeating group, search the database and return what you want using the custom state as one of the constraints.

1 Like

This topic was automatically closed after 70 days. New replies are no longer allowed.