Need to clear values that are “hidden” by visibility, but still have data written to them. I was thinking i could do this on form submit. Unfortunately i can only check the logic of one item then clear that item. I am unable to go down a list of a whole bunch of different “clear value if” that act independently of each other. Video explains it better.
What you can do is create a few if-then-else columns in your table.
Each one would be something like:
- If some column is not empty, then value of some other column (your user specific column)
- Else empty (nada, nothing)
And then on your order summary screen, use those if-then-else columns in place of the original column values.
If you’re worried about leaving those values dangling there for the next time, a nice approach is to use a Set Column Values action to clear them all as a user enters the form screen.
Seeing that you have a custom form here, what you can do is create a series of if-then-else columns to “fix” those values.
Say if this switch is true then I want to write it as an empty value, else I want to write it as whatever the user’s input is. When you add a row, you write those if-then-else values to the destination table, not the original values.
In the video below, originally I thought you would need JS columns to achieve what you want, but ITE columns like above would do. This should still apply to a normal form scenario when you have multiple conditions to clear values. I explained why I had to use JS instead of ITE columns.
Just had one question regarding the “If then” so that i understand the logic behind the scenes for future builds:
All my values that people are writing to for this custom form are user specific. The “if then” type column doesn’t allow me to specify user specific. But technically everything is working fine. At first I thought “well it is pulling values from user specific columns so each answer should be different”. But then what confused me is that even though it is pulling different user specific values to create this logic column, isn’t it technically setting that logic column to that value, which at that specific point in time is the same for everybody using my app because the column isn’t user specific?
I’m probably explaining it poorly. It scares me because everything is working fine, but I don’t quite understand why it is.
Actually I made a video in hopes that I can try and articulate what I mean a bit better.
Computed columns are computed on the user’s device. Not the server. They will compute with whatever value they see. In this case the computed columns see the user specific value. It will be different for every user because their device is doing the work.