To expand on what Steve correctly said, you cannot trigger at the exact date and time specified in a field of a table. Reports are triggered at the most once a day at the time you specify when you configure the Report.
You could achieve an approximation of triggering at the DateTime found in the table by doing the following:
- Create a table that contains one row for each DateTime you wish to trigger at. Let’s call the table “TriggersAt”. Each record would contain a DateTime field called “TriggerAt” which specifies when the thing should be triggered. Also include a DateTime field in each record called “LastTriggeredAt”. Initialize “LastTriggeredAt” to a datetime in the past.
- Create a Report that is triggered at a particular time each day, say 8:00 AM daily.
- Have that Report check each row in the “TriggersAt” table and sends an email, SMS, notification, or whatever if the “TriggerAt” datetime in the “TriggersAt” table has been reached and the “LastTriggeredAt” is earlier than “TriggerAt”.
- Have the Report include a Data Change action that updates the “LastTriggeredAt” field to the current time.
- Configure copies of the Report to fire each hour during the day. This would cause the trigger to fire within a hour of the desired time.
- The obvious problem with this approach is that the triggering is only as responsive as the frequency with which your configured Reports fire. You can configure more Report instances to make things more responsive but there is a practical limit to how responsive you can make it doing this. I am not sure how to overcome this limitation.
Someone else in the community may have a better suggestion.