I have a form with the following fields:
I would like the submission title in the dashboard to be the full_name field, but instead I’m getting the child_grades one.
Is there a way to achieve this?
Any advice is appreciated.
I don’t think there is any way to specify which field is shown there, @zomars. Most customers use a notification (email or webhook) for form submissions, or download the csv of all submissions, rather than trying to click into each in our UI. There you’ll see all the fields 
Is there a reason why is choosing that specific field? Is it random?
Hi @zomars , no real reason other than it wasn’t designed that way. The UI displays it as it receives it from the API. Sorry about that!
I’m running into this too. What’s most frustrating about it is that Netlify is using one of my optional inputs as a title, which means that the vast majority of submissions appear with no title (see attached screenshot).
It would be great if we could choose a title field in the Netlify UI, or at least infer from the input’s name attribute which ones are most useful (e.g. name, email, username, etc.)
Your best bet will be to export the submissions to some other system where you can review them, Dan. Your voice has been added to the feature request, but I don’t expect we’ll implement it soon.
Very disappointing this is still an issue. Surely it’s a < 10 minute job to add a tiny bit of logic so that form submissions at least attempt to have usable titles? I understand making fundamental changes to your platform have huge consequences and layers of approval, but this can be done entirely in the front end template for the form submissions page, no?
Inside the submissions, the fields are listed in the order they appear in the form, so you obviously have that order at your disposal, and you have all the field names, so I would suggest something like:
if: theres a field called ‘name’, or ‘email’, use that
else: use the first field
Currently it appears to be a totally random field.
Even better would be to specify the primary title field in an attr in the form itself like: data-netlify-primary=“name”, but I imagine that would involve much more dev time.
Come on, please just give this a tiny lick of paint, it’ll make a lot of difference.
Hi there, @jdd 
I totally hear that this is an obstacle for you, and I appreciate you taking the time to share not only your feedback here but also examples of changes you would like.
Unfortunately, I cannot provide a timeline for these changes. That being said, I have included your feedback in full to the appropriate team.
Thanks again for sharing this with us!
I didn’t see it mentioned here anywhere, so I thought I would add an example “workaround” for controlling the submission title.
There are two components to this workaround:
*Note: it does not matter what order you submit the data during POST when submitting the form programmatically. What matters is what Netlify reads first from the HTML as it pertains to the form.
Example:
/// index.html
...
<form name="queue-mystery-tag" action="/queue-mystery-tag" method="POST" netlify=""
data-netlify-honeypot="bot-field" hidden>
<input type="hidden" name="form-name" value="queue-mystery-tag">
<input type="hidden" name="playerId" required>
<input type="hidden" name="mysteryImageUrl" required>
<input type="hidden" name="tag" required>
<input name="submission" type="text" required>
<input name="player" type="text" required>
<input name="hint" type="text">
<input name="tag" type="text" required>
</form>
...
When I post this form (programmatically) I get the results:
I would be curious to know if this is a usable workaround for others. It worked for me and multiple of my forms, every single submission.
@zomars I’m not sure if this is even still relevant to you or not…
@jdd maybe try this workaround and let me know if it works for you?