Bug with sending data via form button from a lookup column

[Jeff_Hager]

I studied your videos a few times and your logic seems sound. It reminded me of a similar post where somebody was having the same issue and got around it by displaying the value on the screen. You could put the NextStatus on the form and hide it with visibility as something to try. It sure seems like a bug to me.

Could not send a "Lookup" column by Form and workaround

Hey guys, I encountered this problem in Form, which is I couldn’t send a data column to the spreadsheet (it made an empty cell) if the column is created by “Lookup” of a relation. Then I found it works correctly if I use the column as a component. As a workaround, because I did not make it appear, I made a template of <!--ID--> where ID is the column I wanted to send to the spreadsheet. Then I used the template as a component of the form. Finally, boom!! I am posting this because I thought…

Here’s a snippet of a private conversation I had with Mark a couple weeks ago. I couldn’t duplicate the issue myself, but when I tried it, it was a very simple test, so maybe something else was a factor in it not working.

@Jeff_Hager

I’m not sure. The way I understood it is that he is viewing a detail page in his app from a sheet that has a lookup column. He has a form button and he wants to use the Column Values (including the Lookup column) to pass along with the form submission to the form response sheet. Apparently it’s not passing that lookup value along. As a workaround, I’m guessing he created a template column from the lookup column and is displaying it with comment html tags in a rich text component to get it to pass through to the sheet. The comment tags probably prevent it from showing on the screen. That’s my interpretation anyway. In my staging app, I created a lookup column and I’m passing it through as a Column Value. It seems to work for me.