SharePoint Tool Activating Despite Filter Outputting 0 Records

[Charchote]

Hello everyone,

I'm facing an issue in Alteryx where my SharePoint output tool activates even when its upstream filter shows 0 records passing.

I use a "Filter" tool set to `ID is not null` (or `!IsNull([ID])`). My goal is to prevent the connected SharePoint tool from running if no records meet this condition.

the thing is when no valid `ID`s exist, the filter's "True" output correctly shows "0 records displayed" in the results pane. However, the SharePoint tool (connected to this "True" output) still seems to activate and show me error, which I want to avoid.

How can I reliably block the data flow to a downstream tool (like SharePoint) if the filter's output is genuinely empty (0 records)? Is there a better way to handle this "no data" scenario to prevent tool activation?

Thanks for any insights

[aatalai]

I would create a batch macro counting number of records, and then use a detour (or opening and closing containers) based on whether or not there are zero records.

I've also attached a macro (you will need to configure the SharePoint output accordingly. @Charchote please let me know how you get on

[dataguyW]

I would  also suggest putting it inside a Control Container assuming you are running AMP.   Then I would sent your filtered list to the input of that container.   It won't turn on if 0 records are passed, and therefore will not execute your SharePoint control.