Itgensql001 error on Data Hub v20.0 with Exact Online XML accounts: salespaymentcondition-code_attr

Upgrading to Data Hub v20.0 from v17.32 … two SQL queries have issues with the new version (v20.0). Both problem queries work fine in the existing version (v17.32). All other queries still work fine.

Query 1. message from log:

2020-11-17 09:20:18.345 Warning itgendhb173: Context: select CODE_ATTR,STATUS_ATTR,NAME,PHONE,EMAIL,ISSUPPLIER,SALES...INE_SALES,LEADPURPOSE_CODE_ATTR from   ExactOnlineXML..Accounts
2020-11-17 09:20:18.408 Error itgencun016: Error itgensql001: itgensql001: Unknown identifier 'SALESPAYMENTCONDITION_CODE_ATTR'. Consider one of the following: CODE_ATTR.
2020-11-17 09:20:20.439 Error itgensql001: ValidationException

Query 2. message from log:

2020-11-17 09:24:29.819 Warning itgendhb173: Context: select DELIVERTO_VATNUMBER,FOREIGNAMOUNT_RATE,FOREIGNAMOUNT_VA...nlineXML..SalesOrders where STATUS_ATTR<>21 and STATUS_ATTR<>45
2020-11-17 09:24:29.866 Error itgencun016: Error itgensql001: itgensql001: Unknown identifier 'SHIPPINGMETHOD_CODE_ATTR'. Consider one of the following: EXACTONLINEXML..SALESORDERS.SALESORDERNUMBER_ATTR, EXACTONLINEXML..SALESORDERS.STATUS_ATTR, EXACTONLINEXML..SALESORDERS.ORDERDATE, EXACTONLINEXML..SALESORDERS.DELIVERYDATE, EXACTONLINEXML..SALESORDERS.DESCRIPTION_TERMID_ATTR.

Sales Order Query:

select DELIVERTO_VATNUMBER,FOREIGNAMOUNT_RATE,FOREIGNAMOUNT_VALUE,FOREIGNAMOUNT_CURRENCY_CODE_ATTR,SALESORDERNUMBER_ATTR,DESCRIPTION,YOURREF,STATUS_ATTR,SHIPPINGMETHOD_CODE_ATTR,ORDEREDBY_CODE_ATTR,ORDERDATE,REMARKS
from ExactOnlineXML…SalesOrders
where STATUS_ATTR<>21 and STATUS_ATTR<>45
local export results as “C:\Hantex\Data\Exact_Data\Exact_SalesOrders.csv” format csv

Accounts Query:

select CODE_ATTR,STATUS_ATTR,NAME,PHONE,EMAIL,ISSUPPLIER,SALESPAYMENTCONDITION_CODE_ATTR,CREDITLINE_SALES,LEADPURPOSE_CODE_ATTR
from ExactOnlineXML…Accounts
local export results as “C:\Hantex\Data\Exact_Data\Exact_Accounts.csv” format csv

Between versions there can be changes in data models and on some platforms (Visma NET, Discourse, Robaws, AFAS, Loket) even without changing version.

Can you add the two SQL queries that raise an error to your question?