That is true. However, the delivered Fiori application HCM_PEP_PROFILE uses this same gateway service. The delivered application queries the gateway service by PERNR as well and has a section for the qualification set.
In my application, on the left hand side, I see a number of employees and I select one, then I am also querying the same gateway service by pernr.
I was trying to review the delivered application to see how they do it. I'm having difficulty following it, but I noticed in the component-preload-dbg.js, their query path is essentially the same, they get the pernr then get the data. I don't know that I'm interpreting this delivered application correctly, but they seem to get back a list of the data then process it in this function:
sortedQualificationsList.forEach(function(result)
Do I need to implement something similar?
EDIT: I did implement a similar function with a .forEach and that worked. However, this is explicitly initiating an oData.Read call, getting the results and looping through them as follows:
var newpath = eeServiceUrl + "/QualificationSet";
oEeModel.read(newpath, null, null, true, function(response) {
var sortedQualificationsList = response.results;
var count = 0;
sortedQualificationsList.forEach(function(result) {
if (count < 6) {
var vertContainer = new sap.ui.layout.VerticalLayout();
//vertContainer.addContent(bulletChart);
vertContainer.addContent(new sap.m.Label({
text: result.Name,
design: "Bold"
}));
vertContainer.addContent(new sap.m.Text({
text: result.ValidUntil,
wrapping: true
}));
oView.byId("qualificationSetList").addContent(vertContainer);
count++;
}
});
Can this be achieved in a similar manner with a bind aggregation as we were trying previously?