S
Stefan Drissen
Guest
Hi Rama, Thanks for the explanation, clearing the mapping when updating is a bit drastic and user unfriendly, but I can live with it. I have pinpointed what is triggering the incoherent error message: @openapi.openedge.export FILE(type="REST", executionMode="single-run", useReturnValue="false", writeDataSetBeforeImage="false"). DEFINE TEMP-TABLE tt NO-UNDO RCODE-INFORMATION FIELD adm_nr AS INTEGER FIELD debtor AS INT64 FIELD name AS CHARACTER INDEX ttix IS PRIMARY UNIQUE adm_nr debtor . DEFINE TEMP-TABLE ott LIKE tt. &IF TRUE &THEN DEFINE DATASET debtors FOR ott. /* fails with ott, succeeds with tt - simply adding preprocessing influences this... */ &ENDIF @openapi.openedge.export(type="REST", useReturnValue="false", writeDataSetBeforeImage="false"). PROCEDURE findDebtor: DEFINE INPUT PARAMETER i_iadm_nr AS INTEGER NO-UNDO. DEFINE INPUT PARAMETER i_i64debtor AS INT64 NO-UNDO. DEFINE OUTPUT PARAMETER DATASET FOR debtors. END PROCEDURE. If I add code that is not code it also works - this disturbs me deeply: @openapi.openedge.export FILE(type="REST", executionMode="single-run", useReturnValue="false", writeDataSetBeforeImage="false"). DEFINE TEMP-TABLE tt NO-UNDO RCODE-INFORMATION FIELD adm_nr AS INTEGER FIELD debtor AS INT64 FIELD name AS CHARACTER INDEX ttix IS PRIMARY UNIQUE adm_nr debtor . DEFINE TEMP-TABLE ott LIKE tt. &IF TRUE &THEN DEFINE DATASET debtors FOR ott. &ENDIF &IF FALSE &THEN DEFINE DATASET debtors FOR tt. /* adding this non code change the behavior!!! */ &ENDIF @openapi.openedge.export(type="REST", useReturnValue="false", writeDataSetBeforeImage="false"). PROCEDURE findDebtor: DEFINE INPUT PARAMETER i_iadm_nr AS INTEGER NO-UNDO. DEFINE INPUT PARAMETER i_i64debtor AS INT64 NO-UNDO. DEFINE OUTPUT PARAMETER DATASET FOR debtors. END PROCEDURE.
Continue reading...
Continue reading...