RunQuery JDE Parameters Error
Posted: March 9th, 2022, 10:41 pm
When configuring a RunQuery service for a JDE query with parameters (:Param), it errors if the number of parameters defined doesn't match the number of parameters in the query.
Would it be feasible to have the parameters in the query automatically mapped to the defined parameters so that it functions more like MSSQL parameters (@Param) and thus easier to maintain?
For example, given param1, param2, and param3, have param1 and param3 mapped twice while param2 is excluded from the below query.
Would it be feasible to have the parameters in the query automatically mapped to the defined parameters so that it functions more like MSSQL parameters (@Param) and thus easier to maintain?
For example, given param1, param2, and param3, have param1 and param3 mapped twice while param2 is excluded from the below query.
Code: Select all
SELECT *
FROM TESTDTA.F0101
WHERE (ABAN8 = :param1 OR ABAN81 = :param1)
AND ABALPH = :param3
AND ABALP1 != :param3