Modified on Tue, 25 Jun at 9:01 PM

Auto-naming helps creative and marketing teams ensure consistency in the naming structure of their Campaigns and Projects by automating the previously manual naming process. You can choose to create unique auto-naming formulas for Projects and/or Campaigns, each with a maximum limit of 255 characters.

Auto-Naming is only available for Business and Enterprise customers.


Auto-Naming Overview

Once auto-naming is enabled in your account, users will not be able to manually update names of Projects and Campaigns. Instead, the name field will be pre-populated with default text, as seen below.

You will also see a reminder when creating and updating Project Templates.

When you create a Project or Campaign, it will be automatically named based on the specifications your defined formula! If the formula pulls in custom field values or dates, you'll want to ensure these are populated so the full name can display. The name of the Project or Campaign will dynamically update if the formula values change - so if you pull in a custom field value, and update the custom field selection, the name will automatically update as well.

Configuring Your Auto-Naming Formula

In order to implement auto-naming in your account, we'll create a standardized formula to your specifications that automatically creates read-only names for all new Projects and/or Campaigns, with the exception of imported work items. This guide will walk you through what we can include in that formula, and what information we need from you. When you're ready to enable auto-naming, submit a ticket to the Lytho Support Team with an example of your requested formula, as detailed below.

Let's say we want to build a Project naming structure using the Project creation date, auto-numbering, a shortened version of our Request name, and a Project custom field for the assigned department.

Here are the sample values we'll use for those components:

- A Project creation date of December 31, 2019
- Auto-numbering starting at 101
- A Request named "Event Request"
- A dropdown custom field called "Department" with a value of "Marketing"

Using auto-naming, we could transform those values into a naming convention that would output “12/31/2019 101 - Event - Department: Marketing”. Throughout this guide we'll illustrate how we can use the auto-naming formula to achieve that result and show you what we can build for your team!

Auto-Naming Components

Here is a comprehensive list of all available auto-naming components for Projects and Campaigns.

Because Projects fall under Campaigns, you can use Campaign components in your Project auto-naming formula, and it will populate relevant information for the Project's parent Campaign.

Project Created DateX
Project Start DateX
Project Due DateX
Project NumberX
Project Custom Field NameX
Project Custom Field ValueX
Project Custom Field Abbreviation*X
Campaign NameX
Campaign Created DateXX
Campaign Start Date
Campaign Due DateXX
Campaign NumberXX
Campaign Custom Field NameXX
Campaign Custom Field ValueXX
Campaign Custom Field Abbreviation*XX
Request NameXX
Request Accepted DateXX
Request Submitted DateXX
Request NumberXX

* All Dropdown custom fields can be edited to include abbreviations for each of the dropdown values. Once auto-naming has been enabled in your account, add your abbreviations on the Custom Fields page under ACCOUNT SETTINGS

In our Project naming example, we would use the Project Created Date, Project Number, Request Name, Project Custom Field Name, and Project Custom Field Value components, which will output “12312019101Event RequestDepartmentMarketing”. We can also add in spacing, punctuation, and other text between components in the formula, changing it to “12312019 101 - Event Request - Department: Marketing”.

Note that we can't add any characters inside a component; for example, we couldn't change our Request name from "Event Request" to "Events Request" using the formula.

Date Formatting Options

By default, dates are output as ddmmyyyy ("12312019"), but we can use date formatting to either clean up the formatting, or pare it down to just the year, month, or quarter.

"Quarter" refers to calendar quarter and cannot be customized to a different fiscal quarter.

Date TypeExample
Year (4 digits)2019
Year (2 digits)19
Month (written out)December
Month (numeral)12
Day (numeral)31
Quarter (numeral)4

Using date formatting options, we can change our Project Created Date field from the default, non-formatted option of "12312019" to "12/31/2019." So now our output will be “12/31/2019 101 - Event Request - Department: Marketing”.

Truncate Components

You can truncate individual components to help minimize the overall name length. Truncation works like the LEFT function in Excel; we can truncate down to a specified number of characters starting from the left (beginning) of a text string, but not from the right (end). You can truncate a component down to 9 or fewer characters.

In our example, if we truncate down to the first five characters of our Request Name, it will change "Event Request" to "Event," making our final output “12/31/2019 101 - Event - Department: Marketing”.

Let's say that the next request to come in is called "Instagram Ad Request”, the Project is created on January 1, 2020, and the Department custom field is set to “Creative". Our auto-naming output for that Project would be “1/2/2020 102 - Insta - Department: Creative”.

What We Need from You

When you're ready to enable auto-naming, submit a ticket to the Lytho Support Team with the following information:

  • Whether you want auto-names for Projects and/or Campaigns.
  • What components you want in your auto-naming formula(s).
  • Any spacing, punctuation, and text you want added in between components. 
  • Any date formatting you need, and what timezone we should use for your dates.
  • Any components you want truncated, and how many characters you'd like them truncated to (no more than 9).

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article