Answers.Body: <p>It is not possible to have dynamic tags within Entry Template settings, no. All fields that do allow dynamic tags will say so in their instruction text.</p>
  
  <p>The reason it’s allowed in some settings but not others is because there is a performance hit each time those dynamic settings are rendered. (We actually spin up Twig to do the parsing, but since the settings are not stored as actual files, Twig must re-recompile the settings every single time.) So we only do it in areas where the performance hit doesn’t matter much. Entry URL Format settings, for example, only have to get parsed when an entry is saved, not each time that the entry is actually requested on the front end.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-14T21:35:50.990Z
Answers.LastActivityDate: 2016-01-14T21:35:50.990Z
Answers.UserDisplayName: Brandon Kelly
Answers.Body: <p>Sounds like you're looking for something like this: <a href="https://craftcms.com/support/entry-type-templates" rel="noreferrer">https://craftcms.com/support/entry-type-templates</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-14T21:29:37.627Z
Answers.Text: I think he wants to know if he can do it *without* doing that; by using something like `something/{type}/{slug}` for the URI and `something/{type}` for the Entry Template
Answers.UserDisplayName: andrew.welch
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-14T21:30:23.167Z
Answers.Text: Won't be the last time I've been wrong!
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-14T21:36:53.847Z
Answers.Text: @khalwat was right about what I was asking, but I didn't even stop to think about using variable includes instead, which should work just fine. Thanks!
Answers.UserDisplayName: John O
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-14T21:21:41.790Z
Answers.LastActivityDate: 2016-01-14T21:21:41.790Z
Answers.UserDisplayName: Brad Bell
Body: <p>When specifying the URL and template used to render a section, it's possible to set variable URLs using something like <code>/{postDate.year}/{slug}</code>. Is there any way to accomplish something similar for the entry template, or do all the differences have to be handled within one template that checks for entry type?</p>
  
Tags: <templating><entry-type>
Title: Different templates for different entry types within a section
ThreadText: # Different templates for different entry types within a section
  
  (Asked by: username_0 on 2016-01-14)
  
  When specifying the URL and template used to render a section, it's possible to set variable URLs using something like `/{postDate.year}/{slug}`. Is there any way to accomplish something similar for the entry template, or do all the differences have to be handled within one template that checks for entry type?
  
  **Tags:** templating, entry-type
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-01-14. Score: 5 | Accepted answer
  
  Sounds like you're looking for something like this: <https://craftcms.com/support/entry-type-templates>
  
  > **Comments:**
  > **username_3**: I think he wants to know if he can do it *without* doing that; by using something like `something/{type}/{slug}` for the URI and `something/{type}` for the Entry Template  
  > **username_2**: Won't be the last time I've been wrong!  
  > **username_0**: @khalwat was right about what I was asking, but I didn't even stop to think about using variable includes instead, which should work just fine. Thanks!  
  
  ---
  
  ### Answer by username_1 on 2016-01-14. Score: 5
  
  It is not possible to have dynamic tags within Entry Template settings, no. All fields that do allow dynamic tags will say so in their instruction text.
  
  The reason it’s allowed in some settings but not others is because there is a performance hit each time those dynamic settings are rendered. (We actually spin up Twig to do the parsing, but since the settings are not stored as actual files, Twig must re-recompile the settings every single time.) So we only do it in areas where the performance hit doesn’t matter much. Entry URL Format settings, for example, only have to get parsed when an entry is saved, not each time that the entry is actually requested on the front end.
  
  
  ---
  
  