The form view within the original doc works as expected, but if it is embeded into another doc or is accessed via the published link, the filter() formula doesn’t work (neither in column formulas nor validation formulas) despite:
Is this behaviour by design because of some security concerns or is it a bug?
Hey @Pablo_DV ,
For my docs it does work (and has been working for years, except for a brief period when a bug prevented the filter to work properly).
I just checked one of my published forms and it works (access through the published link).
Can you share a dummy doc in which this fails?
Greetings,
Joost
Hmmm, that’s weird because @Felipe_Arnhold was also having the same issue and he shared with me on Slack a workaround he had found.
I updated my dummy doc with his workaround, but I just duplicated it and recreated the issue for reference here.
I copied your doc - I can see the difference between the embed and published, but I don’t understand what you are trying to do.
When filtering the related column, you normally put your filter formula in the options, but you try to fill the column with a formula - I don’t think this can work.
What was the workaround?
I have to edit the title to make it clearer: Filter() depending on current value of a form doesn’t work when it’s published.
Having a field with a filter() formula depending on the current values introduced on the form doesn’t work in any way, but I think that’s known.
What I find weird is that if I use filter() formulas in the validation of the fields it works within the form view in the doc, but not when published.
With these validation rules I check if the introduced values in the form would create a duplicated row and prevent the user from doing so.
Hello
I just posted a detailed explanation of my workaround.
Tips using forms: Validation - Ask the Community - Coda Maker Community
Bets Regards,
Arnhold
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.