Template name auto populating as Project name | Community
Skip to main content
Level 2
May 7, 2025
Solved

Template name auto populating as Project name

  • May 7, 2025
  • 2 replies
  • 433 views

Is there a way to stop the project name from autopopulating as the template name that is being used to stop the project?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Daniel_Clarke

Hi @brittanyge if you are creating a project straight from the template (not converting from a request) it will always use the template name by default. Two other ways to have a different name:

  1. Convert requests into projects using the template - this will use the name of the request instead of the project template name
  2. Use Fusion! With Fusion you could have a trigger that watches for new project creation and have the name update to any fields, for example the {referenceNumber} - {DE:Asset Type} - {Campaign Name} - {Entry Date YYYY} resulting in "#5647 - Social Media - Summer Campaign - 2025"

I am a big fan of using Fusion for project names for consistency sake, even if it is converted from a request, being able to append a prefix / suffix is excellent for some quick organization.

2 replies

MorganHatcher
Level 4
May 7, 2025

Hello - 

 

If you are opening project from a Template, it will auto populate the Template Name and add a - Project at the end. Example: Media Template - Project. In this case you will need to update the Project Name in the popup screen when setting the New Project Details, from my knowledge there is no way to not have it auto populate with the Template Name in the Project Name field. 

Daniel_Clarke
Community Advisor
Daniel_ClarkeCommunity AdvisorAccepted solution
Community Advisor
May 8, 2025

Hi @brittanyge if you are creating a project straight from the template (not converting from a request) it will always use the template name by default. Two other ways to have a different name:

  1. Convert requests into projects using the template - this will use the name of the request instead of the project template name
  2. Use Fusion! With Fusion you could have a trigger that watches for new project creation and have the name update to any fields, for example the {referenceNumber} - {DE:Asset Type} - {Campaign Name} - {Entry Date YYYY} resulting in "#5647 - Social Media - Summer Campaign - 2025"

I am a big fan of using Fusion for project names for consistency sake, even if it is converted from a request, being able to append a prefix / suffix is excellent for some quick organization.