Projectal lets you create different types of custom fields so you can store exactly the information that you require. The various types of custom fields are described below.
Boolean
A boolean custom field is a field that has two possible values - true or false. Boolean custom fields are a great way to store true/false or yes/no values from users.
Example: You want to have a custom field that records whether a staff has been trained in the company policies or not. So you create a boolean custom field called "completedCompanyTraining" for the Staff entity.
String
A string custom field is a text field that the user can type in text. String custom fields are a great way to get text input from users.
Example: You want a text field for your projects that records the special project code that your company uses. So you create a string custom field called "projectCode" for the Project entity.
Integer
An integer custom field is a numeric field that contains no decimal places. Examples are "1", "240", "600000", "-535". Integer custom fields are a great way to store numbers such as counts, totals and indexes.
Example: You want to have a custom field that records the number of desks at an office location so you know how much staffing capacity you have. So you create an integer custom field called "numberOfDesks" for the Location entity.
Long Integer
A long integer custom field is the same as an integer custom field except it is able to store very large numbers. It is a numeric field that contains no decimal places. Examples are "165079283", "2385389823", "-2739462903". Long integer custom fields are a great way to store very large numbers such as large counts, totals and indexes.
Example: You want to have a custom field that records the total number of renders made in a VFX project so you can perform post mortem analysis to compare against other projects. So you create an long integer custom field called "numberOfRenders" for the Project entity.
Float
A float custom field is a numeric field that can have decimal places. Examples are "1.5", "8500.2845", "-45.63". Float custom fields are a great way to store floating point numbers such as average values, median values and analytic values.
Example: You want to have a custom field that records the frame rate of video content that you are creating, so your team knows what frame rate is required. So you create a float custom field called "freameRate" for the Task entity.
Double
A double custom field is the same as a float custom field except it is able to store very large floating point numbers. It is a numeric field that can have decimal places. Examples are "29005831.00065", "99999999.995", "-100000.00001". Double custom fields are a great way to store very large floating point numbers such as large average values, median values and analytic values.
Example: You want to have a custom field that records the precise weight for your resources. So you create a double custom field called "weight" for the Resource entity.
Byte
A byte custom field is a numeric field that contains no decimal places. It only requires a single character for storage and is limited to values in the range of -128 to 127. Examples are "1", "140", "-128". Byte custom fields are a great way to store small numbers such as counts and indexes.
Example: You want to have a custom field that records the number of monitors that each staff needs for their work. So you create a byte custom field called "numberOfMonitors" for the Staff entity.
Date
A date custom field is a calendar date field that lets you store the day, month and year. Examples are "2026-06-25", "2020-10-12". Date custom fields are a great way to store any dates that you need to record.
Example: You want to have a custom field that records the date when a staff member completes their company induction. So you create a date custom field called "dateInductionCompleted" for the Staff entity.
List of Strings
A list of strings custom field is a way for users to choose a text string from a known set of text strings that you have defined. Each text string in the list of strings is separated (or delimited) by a "|" character. An example list of strings is "Small|Medium|Large|Extra Large|Huge". The user can only choose one of the text strings from the list. This is a great way to store text strings and control what text string the user enters.
Example: You want to have a custom field that records the type of project that your company is completing. So you create a List of Strings custom field and add the possible values as "Animation|Episodic|Long Form|Games Trailer|Commercial" for the Project entity.
List of Integers
A list of integers custom field is a way for users to choose an integer from a known set of integers that you have defined. Each integer in the list of integers is separated (or delimited) by a "|" character. An example list of integers is "100|200|300|400|500". The user can only choose one of the integers from the list. This is a great way to store integers and control what integer the user enters.
Example: You want to have a custom field that records the pipeline status code for a task. So you create a List of Integers custom field and add the possible values as "101|102|103|201|205" for the Task entity.
List of Long Integers
A list of long integers custom field is a way for users to choose a long integer from a known set of long integers that you have defined. Each long integer in the list of long integers is separated (or delimited) by a "|" character. An example list of integers is "55058393282|3249638383|282920400". The user can only choose one of the long integers from the list. This is a great way to store long integers and control what long integer the user enters.
Example: You want to have a custom field that records the asset number for a resource. So you create a List of Long Integers custom field and add the possible values as "10000000|20000000|30000000|40000000|5000000" for the Resource entity.
List of Floats
A list of floats custom field is a way for users to choose a floating point number from a known set of floats that you have defined. Each float in the list of floats is separated (or delimited) by a "|" character. An example list of floats is "1.0|1.5|2.0|2.5|3.0". The user can only choose one of the floats from the list. This is a great way to store floating point numbers and control what float the user enters.
Example: You want to have a custom field that records the aspect ratio for video content. So you create a List of Floats custom field and add the possible values as "1.33|1.66|1.78|1.85|2.39" for the Task entity.
List of Doubles
A list of doubles custom field is a way for users to choose a double floating point number from a known set of doubles that you have defined. Each double in the list of doubles is separated (or delimited) by a "|" character. An example list of floats is "100000.00005|1500000.00205|4000052.30005". The user can only choose one of the doubles from the list. This is a great way to store double floating point numbers and control what double the user enters.
Example: You want to have a custom field that records the precise value for special task attribute that you are monitoring in your projects. So you create a List of Doubles custom field and add the possible values as "3938434.00045|9237347.55501|8273830001.45026" for the Task entity.
List of Bytes
A list of bytes custom field is a way for users to choose a numeric byte value from a known set of bytes that you have defined. Each byte value in the list of bytes is separated (or delimited) by a "|" character. An example list of integers is "1|2|3|4|5". The user can only choose one of the bytes from the list. This is a great way to store numeric byte values and control what byte values the user enters.
Example: You want to have a custom field that records the department code for a department. So you create a List of Bytes custom field and add the possible values as "10|20|30|40|50" for the Department entity.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article