Delta Aggregation on Web Services SaaS Connector

Hi All

Having an issue with enabling Account Delta Aggregation on the Web Services SaaS Connector.

Documentation says that it is a supported feature and specifically here indicates that $application.lastAggregationDate_account$ holds the last successful aggregation timestamp, but I can not get that placeholder to be replaced within the context URL for the Delta Account Aggregation HTTP operation.

Based on that naming convention, I would expect to see that attribute in the Source attributes, but it’s not there.

Looking at the logs, I can see a ‘state’ parameter getting passed as input to the aggregation "state": {"lastAggregationDate_account": "2026-01-16T10:31:49Z"}, so I’m sure it’s getting saved somewhere, but I’m not aware of how to get that value into a context url.

Has anyone successfully enabled Delta Aggregation on the SaaS Web Services Connector by using a variable in the context URL?

Hi Jeremy, probably not your issue but throwing it out there in case. Have you already run a full aggregation at least once?

1 Like

Thanks Margo. Yes, full aggregation was run successfully prior to the attempted delta.

So I had something similar happen with the VA-based version of the Web Services connector. Not sure if this applies the SaaS version or your situation. My issue was that I was in early development stages so I just playing around trying to get it to work and I didn’t have the response mappings setup yet on the Delta Aggregation operation, so the connector was falling back to the regular Account Aggregation operation.

Thanks Patrick, but I can see from the logs that it is actually making the delta call with the unresolved variable $application.lastAggregationDate_account$

Could be a bug with SaaS version. A lot of SaaS connectors are just wrappers around the Java based VA type connectors, so maybe it’s not passing that delta property properly. Not sure.

That’s sort of what I’m thinking, so hoping to find out if anyone has made it work