Multiple Statements in a DB Reader (11 replies)
Great!
Great!
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
I’ve noticed that when I have a transformation type of DB read that includes multiple DB statements (which is probably a bad IMAN hack anyway) I get the attached results in the audit.
What’s a better way to do what I want to do? I guess I am looking for some design advice. Details below.
Audit email:
What I’m trying to do (which works but gives me the audit notice of failure):
--- this job finds the current records where a price list exists that starts today, inserts them to a staging table, and then directly deletes from Sage.