It is possible to use perform logic on the On Execution event to modify the SQL statement that gets used by the import job. The SQL statement used by the import job is stored in a variable called SQL$ so you if your existing SQL statement ends the FROM clause, you can just append your WHERE clause to the SQL$ variable. Make sure to put a space or carriage return and line feed between the table name in the FROM clause and your WHERE clause.
You can even base your WHERE clause on values entered in temp fields set up as Runtime Assign fields.
------------------------------
David Speck II
Blytheco LLC
------------------------------
Original Message:
Sent: 03-25-2025 12:08
From: Robin Saacks
Subject: Visual Integrator - filtering dataset to import
Thanks for the reply Steve.
We only know the filter at the time of running the VI job. Is there a way to filter the source dataset from the VI job, rather than running through every record in the VI job to find the selected record needed to be updated?
Original Message:
Sent: 3/25/2025 8:29:00 AM
From: Steve Iwanowski
Subject: RE: Visual Integrator - filtering dataset to import
Could you create a SQL View that points to the Sales Order table and includes the filter and then have ODBC point to the View instead of the table?
------------------------------
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
------------------------------