Advanced naming convention
Sjaak Velthoven avatar
Written by Sjaak Velthoven
Updated over a week ago

This article builds upon the following articles:

The article can be followed without having read these articles but it might be useful to look through them as there might be information about conventions that is not mentioned in this article. In this article you will learn all the ways conventions can be used.

The following topics will be described in this articled in this article:


By setting up this convention you will learn all you need to know about naming conventions so you can pick an choose the blocks you like for your own convention.

Say you organize all your 3D models and construction drawings locally.

  • You have a dash ( - ) in the name of the file so in order to separate the different blocks you will have to use an underscore ( _ ) as a separator.

  • These files start with the date of when file was made.

    This is useful to you because even though it usually says this in different places it is just more visual for you to have have your files alphabetically ordered by date of creation.

  • After that the you will have the name of the file that can be any length.

  • At the end of the file name you have some status to indicate what version of the file you have.

    This part is just some extra text you use to tell your files apart locally. You do not want to see this part of the file name in Catenda Hub document name as it is only useful to you locally and has nothing to do with other people in the project.

  • Finally you have decided to make sure you only keep specific file types in this folder.

    You will limit the filetypes to IFC, PDF, DWG, SMC, PL and RVT

Initial setup

Documents with the following file names will be used in this article. You can prepare these beforehand or make them when you get to it that part of the article:

Local files:




A fourth block for the file status

The date of the file looks a little like the code from the example in the medium naming convention article. The block containing the name of the document should also be the same as the filename block in that article. The only block you need to add that is different from the example from above is a block for the status part of your file name.

Convention setup

For this example you will use the naming convention shown in the image below as a starting point.

Custom fields in conventions

There are three different types of custom fields that are useful in conventions:

Integer, Text and Dropdown custom fields can be used as sources for convention blocks.

In the image above the source of the first block is set to text. If we try to upload our first file 230219_Elevation_Draft.PDF you will see that it uploads without a problem. However, you could also upload six letter instead of numbers like: aaaaaa__Elevation_Draft.PDF and it would be fine too. In order to limit this to only be numbers make a new integer custom field called NC_Date. It is named like that just to keep it organized in the custom fields list. Then set this custom field as the source of the first block by clicking on the dropdown list where it currently says text and selecting custom field you created.
You will now see that aaaaaa__Elevation_Draft.PDF is no longer accepted while 230219_Elevation_Draft.PDF is accepted.

For the second block you could leave the source as text since any text is accepted here. It is still recommended to use a text custom field that could be named NC_Filename for future compatibility.

The status can also be any word of any length so make a text custom field called NC_Status and set it as the source for the third block.

For these two blocks you will not notice a difference in the upload process. You will be able to see that the preview in different places now reflects the name of the custom field.

Name same as code

For last block that contains the extension, only a specific set of phrases are to be accepted. To do this make a dropdown custom field called NC_Extension. In this custom field set the dropdown options IFC, PDF, DWG, SMC, PL and RVT. Make the name and the code the same. Be careful that these have to be added one-by-one because a code has to be specified. Now try to upload 230219_Elevation_Draft.pdf and see that it will not be accepted.

This custom phrase is case sensitive. If you want the lowercase extensions to be accepted as well you have to add those to the dropdown custom field as well.

Different name and code

Another good example of what you could do with a dropdown custom field is having a different name and code. Say you have drawings from mechanical, structural and electrical engineers all with their respective blocks. In Catenda Hub you want these drawings to all just be called Engineering. What you could do is make a dropdown custom field multiple options that have the name Engineering and the code of the type of engineering you expect to be in the name of the file. When you upload the file then you will see that even though the name of the file had mechanical, structural or electrical in it the name of the document will always say Engineering.

Document identifier

In the beginning of this article it was mentioned that it was important that the status part of the file name did not show up as the Catenda Hub document name.
That is what the document identifier does.
When this option is turned off this part of the file name will not be used to make the document name in Catenda hub at all.

Try to uploading 230219_Elevation_Draft.PDF and then 230219_Elevation_Final.PDF Notice how, even though the file name was different, the document name will be the same.
This is useful because if the document name is the same, the naming convention will automatically recognize that the second file is a revision of the first.

Finally, this is what your naming convention with custom fields and document identifiers should look like:

Did this answer your question?