Forum Discussion
Hi @rashmi ,
The execute snap may be able to run all the create statements followed by the select statement. However, it gives the output based on the first query. In your case, its a create statement so it gives the output with success message.
If you have all the create statements first followed by a select statement at the end, then I suggest you to try one of these two approaches:
- Approach1:
a) Use two snaps. The first snap has to be the Execute snap. In this first snap, put only the create statements.
b) The second snap can be an Execute snap with the select statement, or the Select snap itself.
- Approach2:
a) Use a multi-execute snap followed by a Execute/Select snap.
b) Put all the create statements in the multi execute snap.
c) And, use Execute snap with select, or the Select snap itself.
Let me know if this helped.
Did you configure your REST snap with an error view? If so, see if the error_entity field in the error document tells you anything useful.
The error view output tells the same story, that it is forbidden. We are asking another engineer who has worked on external APIs as well. We aren’t sure if it is a security/whitelisting issue. I appreciate your help. I might get back here for questions again if there is anything else on the SnapLogic side.
Related Content
- 3 years ago
- 4 months ago
- 10 months ago
- 2 years ago