Noodlesoft Forums

I have a rule which looks for a date within the contents of a PDF (contents contain match) and uses that custom date in the actions to move, rename and tag the file. What I'm looking for is a way to use the file's Date Created attribute (or other attributes) within the same rule in the event that a date can't be matched in the contents. For example:

If [Any] of the following are met for [the current file or folder]
-- [Contents] [Contain match] [* Date]
-- [Date Created] [Matches] [* Date]

But I can't see a way to do this...you don't get a "Matches" or "Contains Match" option when using attributes like Date Created. Anyone know a way to do this?

Why do you need to capture Date Created into a custom attribute?

Mr_Noodle wrote:Why do you need to capture Date Created into a custom attribute?

I need the new filename and tags to be derived from either a date matched within contents or (if no date able to be matched in contents), the file's creation date. My assumption is I'll need to reuse a custom date token to cater for both scenarios in the same rule.

For now, you'll probably need to check if the custom date is blank and use date created which may require a separate rule.