I need a Transaction or Background Task Logic Block to run automatically when an application opens in List View, without requiring a user click or opening a record.
Form is Initialized only fires in Detail View, and Load Data on List Form appears limited to UI Logic Blocks.
I can work around this with a scheduled job that updates the records, but I would prefer to avoid that.
Is there a supported way to trigger Transaction/Background Task logic automatically on List View load? Thank you
There is no way to trigger transactional work on the load of a list view. The principle behind that limitation is that the list view is a read, not a write, and to open up writes means that on every refresh of that page, every filter criteria change, is issuing mutations to the database. While I’m sure your case would be a responsible DB write, there is nothing to limit the scope of the DB impact of such an event.
Can you describe what you would be doing if you had such a hook and why it’s important to your user flow?
Thanks, Kendra. The use case is a view only summary list showing current open-item counts per assignee (on a dashboard card), based on records in two source applications. I was looking to refresh those counts automatically when the list opens.
Given that this cannot be triggered transactionally from List View, what pattern would you recommend for keeping those summary counts current?
@lpopovici here’s an option that might get you closer:
An app that has a subtable on it
Dashboard card is configured such that it opens the detail view of the app (it will always open a new record)
Form Init of the app populates the subtable (assuming you have enough information available to know what to fetch)
Associated dashboard page has Auto Refresh set to true (not what you asked for but something that makes sense for dashboards which are live views of data)