If I understand it correctly…or at least how I do it…is that I have a custom action that clears the USC columns prior to the Link To Screen action, and/or I clear the USC columns in a custom action after first Adding the Row. You shouldn’t be adding a row prior to the Link to Screen action. Really, in most cases, you will be editing the same (most likely the first) row every time you use and submit the form.
One suggestion I have is to create your 50 USC columns, but in a separate table with only one row. It will just be a work table to temporarily hold data while filling out the form. That way you can keep it separate from your form response table. Display your tab or screen using that new work table, fill out the form, and have it submit to you existing form response table.
Yep, this is what I usually do. Although sometimes I’ll leave the user specific columns intact, and use them to build a CSS table to present the row that’s just been created, and give the user an opportunity to review and/or edit it. So I’ll show the user the table, plus a button bar with “Edit” and “Go Back” options. If they choose Edit, then they get an edit form pre-populated with the User Specific values, and if they choose “Go Back”, only then I’ll clear the User Specific columns.
Okay. So it depends on whether or not you’re using row owners. If you are, just add a component and you’ll find that you can use columns from your User Profiles as the source. Row owners will ensure that you’re selecting from the row that belongs to the currently signed in user.
If you’re not using row owners, then it’s a little trickier. Essentially you’d need to create a single relation between the current table and your User Profiles table (using a template containing the current users ID or email address), and then import whatever columns you need using lookups via that relation.
This might be a case where a custom form isn’t a good choice - I can’t say for sure.
What are you trying to do with the user data? Are you trying to display it on the screen or pass it through the custom form when you submit the form? What you are showing with the user columns in the native form is to pass the user profile data into the form sheet. In a custom form, that same information would still be there, but in an action, such as Add Row. If I understand correctly, you should still be able to do what you want, but you just need to look in a different place to get that user data written to the form sheet.
So I am using conditions, in the action editor, and checking for user-specific fields that are written into from a selector. However, is does not hide my button bar or disable the button if the fields are empty. Please help.
Which button do you expect to not be visible here? You’re using a button bar, and your screenshot shows that you have multiple branches of condition, if one of them is satisfied then your button will still be clickable.