3. Bug Fixed

Fixed Database Query Field: Incorrect Query Generated When Mapping Fields from Parent to Child

We have fixed an issue that occurred when generating a database query for fields mapped from a parent object to a child object. Previously, when a parent field was mapped while querying the child object, the generated SQL statement could include the parent object field without the correct join/reference. This caused the database query execution to fail with the following error: “Failed to process message: Database query execution failed: PreparedStatementCallback; uncategorized SQLException for SQL [SELECT Account.accbillingcountry, lastName, acc_id, contact_id FROM Contact WHERE acc_id IN (?)]; SQL state [S0001]; error code [4104]; The multi-part identifier "Account.accbillingcountry" could not be bound; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The multi-part identifier "Account.accbillingcountry" could not be bound. This issue has been resolved by updating the query generation logic. Parent fields are now removed from the child interface query statement. After this fix, the child interface query can be generated and executed successfully without the SQL multi-part identifier error.