Skip to main content

Hello Community, 

I am trying to build a workflow that will update a custom numeric field named “Sequence”. This field will run on the Project object and then assign a numeric value to every Milestone regardless of how many.For example:

Milestone1 = 1001

Milestone2 = 2001

Milestone3 = 3001

etc.

 

The issue I am having is the variable I am configuring within the rule only provides me the last Milestone value and then assigns it to all the Milestones. Per my example above, there are 3 Milestones and the last Sequence value is 3001. All 3 Milestones are given this value creating an undesired duplication when ran on Sub Items from Project object. 

 

Question: Is there a way to make this run so that the values are specified correctly per my example above without the duplication?

There is an standard field on Hierarchy called ‘Sequence Order’. My understanding is that is will be unique. When a milestone is created, you could read the value of Sequence Order and save it into your custom field.

Maybe this is too complex for what you’re trying to achieve, and just having a custom field holding the ‘last used sequence number’, defaulting to 1. Each time you need to vreate a new milestone read the value, incrementing it by 1000 to get your Sequence value and resaving the new number into the ‘last used sequence number’ field


Thank you for the information, however Sequence Order is not exposed to workflow rules. 


Sequence Order is available in the workflows, but you have to use it in workflows on the ‘Parent’  (in All Links → Hierarchy → Parent) object. 

Without fully understanding your use case, I suspect that the Sequence Order solution is more complicated than you need, and instead, just maintaining your own custom field holding the last number used as I also mentioned in my reply may be sufficient for you.

Julian