Trigger report subscription from change in Custom Table

Out of the box, no. I'd start by creating one of two things:

• Custom event handler which performs that count each time a custom table object is entered. Downside of this is it makes an additional COUNT(*) call for every insert action.
• Scheduled task which runs every X minutes and does the same thing. The upside of this is it will always run at a given time and is predictable. The downside is you will need to store what the last count was after each count so you have something to compare with.

The sched task is what I was going to do if there isn't an easier way.

I was hoping to leverage the 'condition' field of a report subscription in some magical way.

Well you could write a macro and the possibly utilize the 'condition' field but I think your best approach (less intensive and invasive) is the scheduled task. Ask yourself these questions:

• How frequently will these "reports" be read?
• Is there a need to have the report automatically send at the exact minute EVERY TIME the count reaches 100?
• What happens when the automation errors out? (doesn't matter it it's global event handler, scheduled task or a macro)

If you arent deleting any of the rows and the ItemID is always in sequence without any breaks you might try using the event handler and checking to see if the ItemID is dividable by 100 without any remainder (mod) then trigger the report. If you need some info on custom table event handler..

[CustomTableInterceptor]
public partial class CMSModuleLoader
{
    public class CustomTableInterceptor : CMSLoaderAttribute
    {
        public override void Init()
        {
             CustomTableItemEvents.Insert.After += CustomTableItem_After_Insert;
        }

        protected void CustomTableItem_After_Insert(object sender, CustomTableItemEventArgs e)
        {
            CustomTableItem customtableitem = (CustomTableItem)e.Item;
            string tablename = customtableitem.ClassName;
            //etc
        }
    }

Thanks Laura - I think I'm going to go with your & Brenden's suggestion of using an Event Handler. I'll need to update another custom table with some values so that I can track the emails sent and avoid duplicate messages.