Custom Field issue

Hi Rich,

Are you trying to do this as a formula? I'm not sure what the results would be if you did.

But I do something like this already. Actually it's the truncated name of the parent project with the right type. With our setup it may be the parent, the parent's parent or even the parent's parent's parent. So this proves it can be quite robust.

I create this name as the result of a custom action that we use to create structured subprojects

I also just tested your forumula:

           Left(ToString($ParentProject.Name),7)

And it works fine as a Custom Action. So you've done it correctly.

So a better bet - I do a similar thing to combine two fields that is triggered as a workflow rule when the name of the project changes (or first time) which might be closer to what you need.

Good luck,

CE

Yes, I see now that I can do it as a workflow rule and it works.  I was trying to do it as a custom field, that's where the equation failed.  It seems silly to generate it over and over as a workflow rule...

Hi Rich,

Glad it's working for you. Clarizen is a little funny about new work items, they don't have any awareness of where they are until after they are created which is why the formula option would fail.

Using the workflow rule should be pretty clean, you can trigger it when a new task is created or when the name changes and thus would only run when you needed it to.

And I'm glad you posted as it reminded me of a similar problem I was having with filtered relationships (I shelved it at the time)

Best of luck,

CE

A note on custom field formulas: You can only access fields from the current object in custom field formulas which is why $ParentProject.Name didn't work. Workflow rules don't have this limitation and.