thank you for your quick reply. I once tried that but when deleting a record from a list (list remove) it took ages to delete and also i have to email the files and that's done in a traditional web app so i cant pass a list variable as an input parameter to email so either way i had to save data in an entity. 

Hi Rudo,

Sorry, I'm not able to understand why it's taking too long to delete the Local list record using ListRemove client action?

Solution 1: Using Local List type variable

1) Use/Map the Local List type variable as the Table Source

2) Add/Remove table record, which is not that difficult to achieve using ListAppend/ListRemove

3) Within the Send Email button client Action flow, before calling the actual server action (exposed from the Traditional Web app) - define a logic to dump/Insert all the Local List variable records to the respective entity for future reference.

Solution 2: Without using Local List type variable

• Just introduce an additional logic before the end node within the Send email server action (defined in the Traditional Web app), --> define an Advance SQL node to clear/delete all the respective entity records and Hence, on every screen load the Aggregate result mapped with the Table widget will be empty.
• I personally won't prefer this approach because unnecessary query execution is occurring during the screen load (Of which the result-set will be empty on every instance)

Note: I would suggest, to use the Local List data type variable approach for this use-case (Solution 1)

Hope this helps you!

Kind regards,

Benjith Sam

Thank you, For option A, i tried that but when i try to delete a record from the list (List remove) it took ages to delete but its instant when i call a delete action of an entity.

Option B can work but either way i am saving these records in a temporary entity and would like to delete the records once the user is done. Deleting the records on submit won't help i.e if someone clicks email-the files are emailed and if i delete the records there then i will lose the record on screen if data is refreshed and the user will need to add the statement again. Or i can get an error if the record remains and the user clicks download now in the database the record is no longer there.

I love the second option B but i will need to clear everything at some point....question where? on load? on initialize, on render? iterating too many records might slow the process.

Hi RUDO,

For option B think about the IsDraft flag I mentioned as an IsActive flag. So you add an extra attribute to the record called IsActive and when you add the record to the database you set the IsActive = False. When the user presses submit, you update one by one the records with IsActive = False to have the IsActive = True. You won't need any screen event like OnInitialize, you just need to update the query to only show records with IsActive = True.

Also to add, it is not a very good practice to remove records on OnInitialize events as it is not clear for the user (nor the developer) what is happening leading to potential trouble maintaining that code, that's why the above strategy is a more intuitive one.

Let me know if it helps.

Regards,

João