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

Description

None

Environment

None

Activity

Show:
Norbert Bede
September 4, 2020, 2:24 PM

Hi

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

norbert

Nicolas Micoud
September 4, 2020, 2:29 PM

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

Norbert Bede
September 4, 2020, 2:33 PM

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]

Nicolas Micoud
October 21, 2020, 5:40 AM

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 ?

Carlos Ruiz
October 21, 2020, 8:57 AM

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

Fixed

Assignee

Nicolas Micoud

Reporter

Nicolas Micoud

Labels

Tested By

None

Priority

Major
Configure