Some examples

Assume that we have a project with the following data.

Based on this data, the table below shows sample formulas, the output of that formula and also provides an explanation.

Examples of the formula field

Now, lets try creating some formula using custom dields and using some logic :

• Accessing a custom field of Client of a Project on a Task Report
  Let us say you have a requirement to flag all tasks in a project where the client is rated 1 as 'High' priority tasks, 2 as 'Normal' tasks and 3 as 'Low' priority tasks. There is a custom field for Client which rates the client as 1 or 2 or 3 depending on the client's value to my business. The custom field is called 'Rating' and has a formula key 'rate_01'. Now, you need to create a custom formula field on task. Let us name this 'Task Importance'. The formula will look like this :
  ${entity.project.client.rate_01 == 1 ? (High) : ' ' || entity.project.client.rate_01 == 2 ? (Normal): ' ' || entity.project.client.rate_01 == 3 ? (Low) :' '} 
  
  Now if display 'Task Importance' column in a task report and you will know the importance of the task and can follow up accordingly.

• Date Arithmetic
  Let us assume that one of the projects where you are a PM has completed. Now, you want to compare which of your resources, took more days to complete the task due to which the project's deadline was not met. For this, you need the Actual (Finish) date of the task and the deadline of the project. Then, subtract these values and you will get the results. Since, these two fields are dates, you cannot perform direct operation on them.  You need to first convert them to a number and then perform the operations. Create a formula field for task and get the variable for the two fields i.e  Actual (Finish) (entity.actualFinish) date of the task and Project's deadline (entity.project.deadlineCalendar). Then, the formula will look like:
  ${(entity.project.deadlineCalendar.time.time - entity.actualFinish.time.time)/86400000}
  
  When you write ".time.time" it means that the date field is first converted to milliseconds for both the fields, then the subtraction is done. The result is again in milliseconds which needs to be converted again in days and hence, it is divided by 86400000. This gives the extra or less days taken by the resources to complete the task due to which the deadline was affected.
  
  
• Define your own health indicators
  Your company may have a different logic on how a budget/schedule status for your task/project is calculated and so you do not wish to use the one provided by us. Lets take an example that you actually want the schedule status to show the status depending on the baseline dates; instead of the projected dates. Then, your formula will look like:
  
  ${set ("label", 'Unknown')}
  ${set ("label", entity.projectedFinishCalendar.time.time <= entity.baselineFinish.time && entity.percentComplete!=100 ? 'On Time' : label)}
  ${set ("label", entity.percentComplete!=100 && Date.now().time > entity.baselineFinish.time ? 'Overdue' : label)}
  ${set ("label", entity.projectedFinishCalendar.time.time > entity.baselineFinish.time && Date.now().time < entity.baselineFinish.time ? 'At Risk' : label)}
  
  ${set ("color", 'Neutral')}
  ${ set ("color", label eq 'On Time' ? '#008000' : color)}
  ${ set ("color", label eq 'At Risk' ? '#FFA500' : color)}
  ${ set ("color", label eq 'Overdue' ? '#FF0000' : color)}
  
  

  <span style="display:inline-block;width:10px;height:10px;background-color:${color} ;border-radius:5px;"></span>&#160;${label}