Update EO attributes when the corresponding VO atttibutes are calculated

Question

Hi All,
An existing VO on an existing PLSQL EO when opened in Editor displays the EO table attribute fields (attribute1 - 15) as calculated. The corresponding ViewAttribute(s) in VO XML definition do not refer to the EO Attributes.
We need to pass table attribute fields to the PLSQL API (setting the EO attributes will suffice since EO attributes are input to PLSQL API) so that they also get updated in the DB call. Setting the VO attributes does not help (probably because no mapping between VO and EO attributes). If we set these table attributes directly in the DB (via a seperate DB call), the EO PLSQL API execution resets these attributes to the old values.
Please let me know if a solution exists.
Thanks and Regards
Harjan

Answer 1

Hi Steve
Thanks for the reply and apologies for my tardy follow-up.
2 comments following your post:
1) In the returnListener backing method I added your EL helper to set the binding directly:
public void returnDialog(ReturnEvent returnEvent) {
  String eventNoStr = (String)returnEvent.getReturnValue();
  // eventNo.setSubmittedValue(null);
  // eventNo.setValue(eventNoStr);
  EL.set("#{bindings.EventNo.inputValue}", eventNoStr);
  // AdfFacesContext adfContext = AdfFacesContext.getCurrentInstance();
  // adfContext.addPartialTarget(eventNo);
  // adfContext.partialUpdateNotify(eventNo);
}If I don't include the commented out lines, the fk field is not updated on the screen, nor after a submit. I understand where you're coming from with your EL helper routine here and would have expected this to update the binding at minimum (visible after a submit). Obviously as this isn't updated, the other fk fields aren't either.
2) I've seen the ADF SRDemo approach and not a big fan as the LOV screen and pageDef through the inclusion of the calling page's iterator is not generic. This implies a LOV screen cannot be re-used across several locations in your app as it needs the hardcoded iterator from the previous screen.
Ideally the launchListener on the calling page could pass in the EL binding string to update, and the closeDialog call on the LOV could update this setting. The other fk fields would then automagically be updated in the calling screen. I tried getting your EL helper routine to set the binding directly via EL.set("#{data.editEventBookingsPageDef.EventNo.inputValue", value); in the closeDialog routine, but no luck.
Any suggestions?
Thanks for your assistance,
CM.