Adding the result key means WeWeb is now getting the array of items you need, not an object containing the array. This enables the Collection Page to work more fluidly.
When you’re ready, can you re-publish your site and let me know if this solved the issue with the slugs?
Interestingly, I am using Airtable and don’t see such options. Any ideas?
And I am using Static Collection as my data will not be changing after the build.
My homepage is my listing page, and from there every item is connected (tried URL with parameter and workflow with parameter) to a page > Report 2 (in this instance).
Both options work fine when previewed on WeWeb, but broken when published.
URL seem to break the linking, and workflow one doesn’t work when the site is published.
URL link to takes the page to a link with random id (see image), not sure where that number is coming from.
It is definitely related to my URL path, but couldn’t crack the rationale. When it is a collection page URL paths are not editable at all, I need to recreate the collection page by copying it to edit the page name.
Below some of the elements related to the explanations.
No worries, that’s something were we want to rework the UX in our product.
Static collection pages get prerendered and generated during build time (better for SEO), while dynamic ones are generated frontend side when a user goes to them.