Post

1 follower Follow
0
Avatar

Custom field formula on $Children is not evaluating ???

I have defined a custom field on Project that I want to reflect the Completion status of a specific sub-project (screenshots attached).  I am using the $Children related items fields, but the custom field is not being updated.  Am I missing something?

Appreciate your help with this,

Thanks,

Richard

Richard Udy Answered

Please sign in to leave a comment.

6 comments

0
Avatar

Richard, 

 

Thank you for contributing to the Community. We would need more information to see how you configured this. 

I would need to know what you are trying to accomplish here. Based on the image you provided you are updating a custom field as 'Completed' when the Project Type is 'Salesforce Stage' and and Onboarding Stage is 'Preperation'.

Since we already have a Standard field that shows Project State (Completed), What is the Use Case here?

 

For further clarification, since Clarizen invites you to a free interactive, real-time demonstration of our features, let me suggest to join our Advanced Q&A webinars (see the link-> http://www.clarizen.com/resources/online-demo.html#second ).These are great resources for free consulting with our Customer Success Managers and visual answers to your questions. 

 

Boris Krutiy 0 votes
Comment actions Permalink
0
Avatar

Hi Boris,

I have a toggle field on the top-level project which I want to set true when the sub-project (Salesforce Stage + Preparation) is completed, and false when its not completed. The purpose is to support management reporting on top-level projects.

So I believe I have made the children of the top-level project the target, filtered them for the one that matches Salesforce Stage + Preparation, and taking the boolean result of comparing its stage with 'Completed' to assign to the toggle field on the top-level project.  I assumed that if no children match the filters the logic is simply ignored.

I have since managed to achieve this through workflow rules, when the sub-projects state changes, but originally thought I should also be able to do this more simply (and perhaps more elegantly) through this field logic.  Anyway, I would still like to understand how this works, and to know what it is that I'm missing.

thanks,

Richard

Richard Udy 0 votes
Comment actions Permalink
0
Avatar

Is there some good reason to use workflow rules instead of calculated fields?  Or is it just personal preference? 

It seems to me it should be possible to do this with calculated fields, so I would like to understand what I am missing with this.  Should I bring it up on a Q&A Webinar, or have I simply set it up wrong?

Thanks,

Richard

Richard Udy 0 votes
Comment actions Permalink