Hi All,
This is a followup to the question which you were involved with last month. I did not want to muddy the waters with a slightly different question in the comments.
Like Jerry, we are working on automations that are linked to a custom date field. As you stated that field holds a range, and should accept a single date. Storing a single date gets this error. (either hardcoding a date, using now/today etc etc)
Error editing issues
ROAD-5 (We couldn't save your changes. Copy your content, then try reloading the page.)
As the field holds a range, using google sheets we were able to ascertain the format in the field to be: {"start":"2023-04-30","end":"2023-04-30"} which we were able to store using Json.
The problem with the field needing to both a start and enddate means its hard to manipulate the field with automations or using exported.
Any way for us to add a feature request to have a date-range field and a date field? or, the current field being able to also accept a single date
Hi Rohan,
Thanks for the feedback, i looked at the solution and will see if it works. Having said that: It would be awesome if we would get the feature in the future. Dates are so critical to work with in workflows.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.