SnapLogic DateTime Conversion Guidelines
The SnapLogic Elastic Integration Platform native DATETIME data type is time zone-aware. For service endpoints that do not expose data types that are not time zone-aware, the SnapLogic Expression L...
Forum Discussion
It looks like this error can be raised by either the Redshift BulkLoad or S3Upsert snap. It seems the generated SQL has a placeholder or something that is causing it to be interpreted as a parameter in a Statement object. These snaps use both PreparedStatements and Statement objects.
A stack trace would be super helpful to investigate this.
I’m not sure if this is the stack trace that you are looking for. If not, can you lead me to where I can get it?
Thanks!
There is not iteration capability within the SOAP Snap, so here’s an idea:
Turn your SOAP request into a triggered pipeline, which you call from a pipeline with the REST Snap. For each request that responds with processing, use that to set the “Has Next” option, and the REST GET Snap will iterate for you. In the “host” pipeline you may want to filter out the responses with Processing by adding a filter Snap.
Would that work for you?
