This is an idea designed with Google services. Using Appsheet, I developed an application that allows you to record bank transactions for a current account or card. When creating the two tables, the first has the current account field, the card field, and the last has a “one-to-many” relationship with the second database table. It was decided to use a single database and create subtables to save KB of memory.
The problem arose when the tables communicated with each other. Tab3, “Bank Transactions,” related, list variable, did not provide a correct result to the accounting field. In fact, during the connection, it was Tab3 that had to send the “many fields” message to Tab2, “Banks,” and leave a correct save result.
BOT AUTOMATICALLY CREATED EVENT NOTIFICATION
The bot automatically creates the event, sending a note to the user, generating a new record in the current account field, and saving the value in the Banks field.
The notification occurs when an action is entered in the current account field, tab 2 banks, storing a value to which the transactions in tab 3 will be linked; transaction data, description of the type, important, and the execution counter.
APP CONSULTING BANK CREDIT STATEMENT SCREEN
Button 1 [Go to details] opens the detailed information displayed.
Button 2 [Edit bank] allows you to edit the bank’s main details.
Button 3 <+> Enters a new bank with all the account details.
