I wanted to create a property that is based on a specific date. The idea is that every year, the calculation adds a year to the input. I want there to be two properties.
Property A (Initial Input Date)
Property B (Rolling Input Date)
Where Initial Input Date means the date we entered a company within the CRM.
Property A will remain uniform while Property B always changes depending on the year. For example:
Property A (Year 1): January 1, 2025
Property B:
> Year 2: January 1, 2026
> Year 3: January 1, 2027
Ideally, these properties should be the only ones that exist to ensure CRM hygiene.
and so on…
Any ideas how I can achieve this using calculated properties?
Hi @Zenitsu22,
Could you maybe - without referring to HubSpot features - explain what you’re trying to achieve by doing that? What’s the use case / goal? This feels like it may be adding steps to something that could be simpler or solved in a more elegant way.
In your goal property, what information will be stored? How will you use it?
Best regards
Planning to use it as a lead reactivation and renewal property that changes year by year. For example, if a lead is lost on January 1, 2025, I wanna use it as a way to easily track when a company’s upcoming renewal date is year by year so I can reach out effectively.
@Zenitsu22 so what would the calculation property return exactly? The “anniversary” of that lost date?
If so, there are other potentially easier ways to solve this:
- Use a yearly recurring workflow based on that date to create a task for you
- Use a segment to filter by anniversary date, see below - this would allow you to create a filtered view of all contacts who have their lost “anniversary” within 14 days from now, for example
