Sure, here's a bit more:
What I meant is that the naming pattern you want to use:
${tcc_sample_id}
...is just saying to use the value in the "tcc_sample_id" column of your data (source spreadsheet is how I phrased that).

However the data will be provided, that column will have to exist and have unique values to provide the unique sample naming. One solution is to rename that column in your data to be "Name" instead. If that's possible, then your samples will automatically end up with those names.

If you can't change the incoming data, another possibility is to use an import alias. Essentially, you tell the "Name" field that it should look for "tcc_sample_id" in the data and put that directly in as the sample Name.

Some relevant documentation:

• Creating Sample Types - has more about naming and defining fields in general
• Sample Naming Patterns - The <SomeDataColumn> example is the ${tcc_sample_id} syntax you're showing in your UI image.
• Import Aliases - this is one of the "Name and Linking Options" available for any field in LabKey.
  -- To set this for a default field, like 'Name', you'd use the schema browser to edit the metadata of that field.

Note that I have not specifically tried the alias on the Name field for a sample type being set via API, and we're not able to provide detailed developer support on this forum, but I believe it is settable there, and that's something else to try if you can't change the actual incoming data field name.

Another resource you may find helpful as you learn the various LabKey terms and options is the playlist available here:

• LabKey Fundamentals Training

Hope that helps,

--Molly