Unable to write to user-specific column for new item

Hi everyone! Looking for some help here.
So I made a small app for people to store their favourite quotes. I created a user specific column so that people could write their own fav quotes in it. However when I try to choose data for my component, there is no option of the user-specific column I have created.
Quote1 is my user-specific column.

But I dont see it in the column data so I may add it.

I have been stuck on this for the past hour. Will be really grateful for any help.

Is there at least one row of data in the destination table? (apart from the header row).
Your User Specific Column needs an available row to write to, and if there isn’t one then it won’t be available.

I don’t really think you need a User Specific column here. As you’re using Add Form, each entry will create a new row, so you may as well just use a normal (basic) text column.

1 Like

Hola @Shubham_Gupta

USC cannot be used in forms. Other than that, do what @Darren_Murphy just said. :point_up_2:t6:


oooh, I never knew that. But I never use native forms, so I’ve never tried it. But yeah, that makes perfect sense when you think about it :+1:



Last year I had a bunch of USCs and could not see them in the form. So I emailed support and that was the answer I got.

I have not used them in a form ever since.

1 Like

Is this documented any where?

Perhaps there should be a new Category created for undocumented rules and features.

I don’t know if it’s officially documented, or at least I couldn’t find it, but in general I question why a person would need to populate a user specific column when submitting a form. Generally if you are adding a new row that’s specific to a user, then either the entire row has row owners enable, or the data is filtered to only the signed in user. If the new row is available to everyone, then a user specific column could be populated with data from several different people, so most likely they would be editing the existing row.

I’m not saying that there aren’t unique situation where a someone would need to populate a user specific column when adding a row. I’m sure there are some situations where it’s needed. But in general, I would question why someone would want to populate a user specific column through a form.

Also, part of the limitation might be because user specific columns require a row ID. I think that row ID has to exist so user specific values can attach to the proper row. When submitting a form, a row id hasn’t been assigned yet, so user specific values would possibly be lost.


If it’s absolutely necessary to populate the USC, I believe you can do a “set column action > This Item” as part of the “On Form Submit” action sequence.


I need a User specific column so that the person using the app sees only those rows which he/she has added. That was the main purpose. Basicually a repository of quotes where each person with a gmail login sees only his/her quotes and not everyone else’s. Not sure how I will do that without USC?

How do I make the sure the data is filtered for a certain user? i.e. when I login onto the app, I want to be able to see only what I have entered. And no one else’s data.

Based on your description that should not be a user-specific column, it should be a normal column that holds a value that is unique to the signed in user (either their email or rowID in the profiles table).

Suppose I have 10 users. Then should I have 10 columns? that doesn’t seem right. How can I make sure that the rows that I have added are seen only by me?

Sounds like you need to be using Row Owners


No, you don’t need 10 columns. Each user will have their own row and if you use row owners as Darren suggested, they will only see their own row. You can use an email column for that.


Got it. Thank you ! Will try that

Thanks! Will try that…