# Date field called "Invalid" in rules

**URL:** <https://forum.asana.com/t/date-field-called-invalid-in-rules/990794>\
**Category:** Asana In Practice\
**Tags:** custom-fields, tasks, rules\
**Created:** [2 December 2024 22:58 UTC](https://forum.asana.com/t/date-field-called-invalid-in-rules/990794 "2024-12-02T22:58:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jack\_Freeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jack_freeman/32/104312_2.png) [@Jack\_Freeman](https://forum.asana.com/u/Jack_Freeman)\
**Post date:** [2 December 2024 22:58 UTC](https://forum.asana.com/t/date-field-called-invalid-in-rules/990794/1 "2024-12-02T22:58:44Z")

</div>

I have a template that uses rules referencing a custom field, which is a Date. When I make project based on this template and other rules reference this custom Date field, the project’s Rules referencing that custom Date field say they are referencing a field called “Invalid.”  
If I change the rule in the project itself, the rule works again. It looks like a part of the template use process breaks the link between the custom field and the rules.  
Does anyone have experience with this, and is there some kind of workaround? Or a fix?  
Thanks!

---

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [3 December 2024 19:26 UTC](https://forum.asana.com/t/date-field-called-invalid-in-rules/990794/2 "2024-12-03T19:26:47Z")

</div>

That sounds like a bug, for which it is best to [contact support](https://forum.asana.com/t/how-to-contact-our-support-team/87774)

Having said that, I’d advise against using rules in project templates.

> [@Leveraging project templates - a deep dive](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/1):
>
> While customisation (just below _Project Membership_) is an option, I would advise caution against adding customisation to your template. This would make sense from a standardisation perspective. Yet I remind you that our goal is not standardisation, our goal is to set a baseline for improvement. And customisation directly in a template - assuming they are not in a [bundle](https://help.asana.com/hc/en-us/articles/14309313756827-Bundles) - will require one of two things before any change is adopted across the organisation:
> 
> - Wait until all existing projects are completed.
> - Change all of the rules in all of the projects made from this template to change them.
> 
> That is a hassle you don’t want to force on anyone.