Trigger Page Workflow vs Fetch Automatically

Ask us anything Tips and Hacks
,
1

Hi,
I am checking the topic: Best practices on 'App load' vs. 'Page load' workflows

But not 100% clear the best for each usecase.

If I have a collection that is fetched automatically, what is the main difference for a Trigger Page Workflow that will fetch that collection when page loaded? When is a “Fetch automatically” triggered itself?

I want to load a collection as a list in a page, if the user (xano) is authenticathed, Would it be best to disable the “Fetch automatically” from the collection and just load via the “Trigger Page workflow”?

Thank you very much.

2

If the collection is used at the time of it’s load on a page - e.g bound to a text, or a value somewhere, then it will re-fetch if you have set it to Fetch Automatically. If you have a conditionally rendered (hidden) element, then the collection for example won’t fetch and you’ll have to load it via the Page Workflow, or some other workflow.

3

Hi @Broberto,
Thanks for overview.

In my specific case, this is a list of values to be loaded in the page when an authenticated user enters the page. So I guess we stick to the first case since the page is also only accessible for authenticated users.

4

I think you should be fine with the Fetch Automatically, otherwise fall back to the manual fetching.

1 Like