Remove hardcoded values for InfoInvoiceWindow (BPartnerID / IsSOTrx) and InfoPaymentWindow (IsSOTrx)

Hi

looks me there is oracle syntax? (i mean DUAL) in Postgres migration scripts.

norbert

Hello Norbert,

AFAIR, the table DUAL has been added years ago in PG schema, so migration script can be registered using the same query

Nicolas

Hello Nicolas.

thanks. an error log is reproducible in the latest 7.1z test.idempiere.org - then another parsing issue exists.

GridField.defaultFromSQLExpression: (IsVendor) - Default SQL variable parse failed: @SQL=SELECT CASE '@IsSOTrx@' WHEN '' THEN '' WHEN 'N' THEN 'Y' ELSE 'N' END AS DefaultValue FROM DUAL [322]

Hi ,

Haven't checked the error, but wondering if there is not a "functionnal" issue.
I've made following test on test.idempiere.org : I open the InvoiceInfo search panel ; SalesTransaction was ticked.
Then, I opened the Business Partner Info panel ; but the Customer field was empty.
I would have expected it to be filled with Yes (as I was looking for a Sales Invoice).

wdyt ?

Added pull request 309 to fix the "Default SQL variable parse failed" log message.