Callback method for ROW-UPDATE is not fired when record is updated

Callback method for ROW-UPDATE is not fired when record is updated This article discusses the ROW-UPDATE event bu ther same applies to ROW-DELETE and ROW-CREATE events when a record is deleted or created, respectively

May 31, 2017
Knowledge

Title

URL Name

Callback-method-for-ROW-UPDATE-is-not-fired-when-record-is-updated

Article Number

000178437

Environment

Product: OpenEdge Version: 11.5 and later OS: All supported platforms

Question/Problem Description

Callback method for ROW-UPDATE is not fired when record is updated

This article discusses the ROW-UPDATE event but ther same applies to ROW-DELETE and ROW-CREATE events when a record is deleted or created, respectively.

Callback method for ROW-DELETE is not fired when record is deleted
Callback method for ROW-CREATE is not fired when record is created

Steps to Reproduce

Clarifying Information

Testing a wizard-generated Business Entity (BE) exposed as a Data Object REST resource service.
The BE contains a callback method ROW-UPDATE.
Testing the service using POST http verb, record is updated on the database but callback does not fire (e.g. contain a rule that should prevent the update or write a PASOE log message).

Error Message

Defect Number

Enhancement PSC00356047

Enhancement Number

Cause

You cannot expect a ProDataSet ROW-UPDATE event to fire within the generated BE.
As the documentation for the event says, the event fire before the record is updated in the temp-table.
But in the current scenario, the temp-table data is sent to the BE AFTER the record has been updated, i.e. the complete temp-table with all its CUD updates is created on the client, and then sent to server (i.e. BusinessEntity).

Does it means that only FILL events are going to fire in a server side BE?
Why does the REST structure for a PUT should contain "prods:rowState": "modified"?.
Also, assuming the dataset "change events" (ROW-UPDATE,ROW-DELETE, ROW-CREATE) are not going to work as for the "fill events" (succesfully tested), how can we achieve this functionality?

           In fact the 11.6 Progress Developer Studio training guide reads, "Lesson 5: Event Handling with Datasets" Page 5-2 (read last paragraph):

           In your application you can write code that handles system-generated events related to datasets. For example, a system-generated event is triggered when a row is created for a temp-table.
           The system-generated events used with datasets and their related objects that you will work with in this lesson can be categorized as:

           • Fill events
           • Change events
           • Query events

           Fill events are used only in the server code where the dataset fills occur. All other dataset events could occur in the client or server.

Yes, currently the FILL event will fire in a server-side BE, but not the ROW-CREATE, ROW-DELETE, or ROW-UPDATE events.

The "prods:rowState" : "modified" property is used for the before-image support, so the backend Submit operation can differentiate between the various CUD operations.

As stated earlier, with the update as example, the event is not firing because the updated record is already in the temp-table, and the ROW-UPDATE event is fired before the record is updated in the temp-table.

Resolution

This is currently expected behaviour
We are investigating how best the generated BE can support these events.

Workaround

In the meantime, you can update your BE code to explictly fire the row event handlers . Here is an example of the UpdateCustomer method below.

@openapi.openedge.export(type="REST", useReturnValue="false", writeDataSetBeforeImage="true").
@progress.service.resourceMapping(type="REST", operation="update", URI="", alias="", mediaType="application/json").
METHOD PUBLIC VOID UpdateCustomer(INPUT-OUTPUT DATASET dsCustomer):

FOR EACH ttCustomer :
// Depending on how you are sending your data over, this check may not be necessary...
IF BUFFER ttCustomer:ROW-STATE EQ ROW-MODIFIED THEN
RowUpdate(INPUT DATASET dsCustomer).
END.

SUPER:UpdateData(DATASET dsCustomer BY-REFERENCE).
END METHOD.

METHOD PUBLIC VOID RowUpdate(INPUT DATASET dsCustomer):
MESSAGE "IN Customer ROW-UPDATE CALLBACK for custnum: " ttCustomer.Custnum.

ttCustomer.Name = ttCustomer.Name + "-TEST".

END METHOD.

Notes

References to Other Documentation:

"ProDataSets: Updating Data with ProDataSets : ProDataSet Change Events." OpenEdge 11.7 Documentation: ABL. Web. 31 May 2017. <https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dvpds/prodataset-change-events.html>;.

Keyword Phrase

Last Modified Date

5/31/2017 6:48 AM

Callback method for ROW-UPDATE is not fired when record is updated

Files(0)

Was this article helpful?

Was this article helpful?

Callback method for ROW-UPDATE is not fired when record is updated

Information

Related Articles