Answers.Body: <p>Firstly I'd recommend splitting the first name and last name into seperate fields. That way in your templates it would look nicer:</p>
  
  <pre><code>{{ member.firstNameField }} {{ member.lastNameField }}
  </code></pre>
  
  <p>than having:</p>
  
  <pre><code>{{ member.firstNameField }} {{ member.title }}
  </code></pre>
  
  <p>when outputting their names.</p>
  
  <p>Once you have done that, in your entry type settings you can set the entry title to run off these first name and last name fields:</p>
  
  <pre><code>{firstNameField} {lastNameField}
  </code></pre>
  
  <p>The slug will be automatically generated from this as well. I may have mis-understood your question, but I hope that helps.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-11T15:02:49.183Z
Answers.Text: Jamie. I would suggest just setting the sections 'title' to `{ firstName } { lastName }` and leave the 'uri' set to `/people/{slug}`. The slug will automatically pick up the title if left blank when saving the entry. It will also not throw an error if you have 2 records with the same firsName/lastName, and you will still be able to use the 'slug' attribute in your templates if you need to.
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-11T15:05:02.373Z
Answers.Text: @DouglasMcDonald Good thinking, thanks. I'll update the answer.
Answers.UserDisplayName: Jamie Wade
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-11T12:43:29.990Z
Answers.LastActivityDate: 2015-02-11T15:07:27.517Z
Answers.LastEditDate: 2015-02-11T15:07:27.517Z
Answers.UserDisplayName: Jamie Wade
Body: <p>I have a 'Profile' channel that gives the profile of people.</p>
  
  <p>I have 'Last name' as the title, 'first name' and I'd like to use first name in the slug rather than have to add the first name to the title and then need to create another field to store the last name.</p>
  
  <p>I thought, similar to {entry.type} I could've gone for {entry.firstName} but that doesn't work.</p>
  
  <p>Possible?</p>
  
Tags: <url><slug><custom-field>
Title: customised slugs using custom field
ThreadText: # customised slugs using custom field
  
  (Asked by: username_0 on 2015-02-11)
  
  I have a 'Profile' channel that gives the profile of people.
  
  I have 'Last name' as the title, 'first name' and I'd like to use first name in the slug rather than have to add the first name to the title and then need to create another field to store the last name.
  
  I thought, similar to {entry.type} I could've gone for {entry.firstName} but that doesn't work.
  
  Possible?
  
  **Tags:** url, slug, custom-field
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-02-11. Score: 3 | Accepted answer
  
  Firstly I'd recommend splitting the first name and last name into seperate fields. That way in your templates it would look nicer:
  
  ```
  {{ member.firstNameField }} {{ member.lastNameField }}
  
  ```
  
  than having:
  
  ```
  {{ member.firstNameField }} {{ member.title }}
  
  ```
  
  when outputting their names.
  
  Once you have done that, in your entry type settings you can set the entry title to run off these first name and last name fields:
  
  ```
  {firstNameField} {lastNameField}
  
  ```
  
  The slug will be automatically generated from this as well. I may have mis-understood your question, but I hope that helps.
  
  > **Comments:**
  > **username_2**: username_1. I would suggest just setting the sections 'title' to `{ firstName } { lastName }` and leave the 'uri' set to `/people/{slug}`. The slug will automatically pick up the title if left blank when saving the entry. It will also not throw an error if you have 2 records with the same firsName/lastName, and you will still be able to use the 'slug' attribute in your templates if you need to.  
  > **username_1**: @username_2 Good thinking, thanks. I'll update the answer.  
  
  ---
  
  