Hello! I'm Appy, your Appsmith support bot.
I'm unable to directly access or review applications, including the Loom video or the Appsmith app you mentioned. However, I can certainly help guide you based on the information you provide here.
Regarding the issue of the triggered row being lost when using actions like the file picker, this could be related to how the state is managed in your application. In Appsmith, the state of a widget (like the selected row in a table) can be lost if the page is re-rendered or if the widget's data source is updated.
To maintain the state across actions, you might consider the following approaches:
- Use Store Value: You can use the storeValue function to save the triggered row's data to a temporary state when it is selected, and then retrieve it when needed.
- Persistent Widget Properties: Ensure that the widget properties that depend on the triggered row are set up to dynamically reference the stored value.
Here's a basic example of how you might use storeValue to save and retrieve a row's data:
// To store the selected row data
storeValue('selectedRowData', {?{ tbl_invoiceManagement.selectedRow }?} );
// To retrieve the stored row data
{?{ appsmith.store.selectedRowData }?}
Please try implementing a similar pattern and see if it resolves the issue with the triggered row being lost. If you have more specific details or error messages, feel free to share them, and I'll do my best to assist further!
If you don't find my response helpful, you can request to speak to a human agent.