@emmanuel I just created a new date field on a table that has preexisting data in it. So while the column is added, it is empty for all the existing records. I also have a workflow that runs only when that date field is more than 3 months old.
Will the workflow run on my existing records right away since they are empty?
Or…
Will those records never get picked up because the date is empty and therefore doesn’t pass the < today - 3 months expression?
Trying to figure out if I need to go update all my existing data with a dummy date so they get picked up.
My advice would be to test it. If everything is already set up, throw it to a test and see what happens.
If it is not working as you want it to and bubble is for some reason taking an empty date and not allowing it to be recognized as not past three months, then you may need to do something.
My assumption is this data is already in your database, which is why it is easiest to just test it and see. If there is an issue and you need to create a dummy date, then perform a recursive workflow on your existing data and make the date current date + 4 months.
Hey @dillon.blakes did you resolve this? I’m facing the same thing. I want to have a date field that can remain empty and then get ignored in a search. (But if I “ignore empty constraints” on all the constraints, it’ll screw things up).
So did it run on those existing records or did it not pick them up because date was empty.
thanks
Fred
It did not run on the empty items. I ended up backfilling the date for my purposes.
