Openui5: MessagePopover intermittent hadling

[KCezar]

OpenUI5 version:
sap.ui.core: "1.74.0"
sap.m: "1.74.0"
sap.ushell: "1.74.1"
sap.ui.layout: "1.74.0"
sap.ui.unified: "1.74.0"
Browser/version (+device/version):
Chrome
Version 80.0.3987.122 (Versão oficial) 64 bits
Any other tested browsers/devices(OK/FAIL):

URL (minimal example if possible):

User/password (if required and possible - do not post any confidential information here):

Steps to reproduce the problem:

1. In onInit
   this._MessageManager = Core.getMessageManager();
   this._MessageManager.registerObject(this.oView.byId("page"), true);
   this.oView.setModel(this._MessageManager.getMessageModel(),"message");

1. In View "semantic:FullScreen"
   
   
   
2. On Handler
   var oMessagesButton = oEvent.getSource();
   if (!this._messagePopover || this._messagePopover.bIsDestroyed) {
   this._messagePopover = new MessagePopover({
   items: {
   path: "message>/",
   template: new MessageItem({
   description: "{message>description}",
   subtitle: "{message>additionalText}",
   type: "{message>type}",
   title: "{message>message}"
   })
   }
   });
   oMessagesButton.addDependent(this._messagePopover);
   }
   this._messagePopover.toggle(oMessagesButton);
   this._arrayForDestroy.push(this._messagePopover);

What is the expected result?
Every time when have some erro message, the message manager can handler de exception.

What happens instead?
Somes message it's handling by Messagepopover others are not.
Any other information? (attach screenshot if possible)

Adicional response information:

RESPONSE OF MESSAGE HANDLED
HTTP/1.1 400 Bad Request
DataServiceVersion: 1.0
Content-Type: application/json
Content-Length: 1135

{
"error": {
"code": "",
"message": {
"lang": "pt-BR",
"value": "Erro na validação da programação - consulte o log"
},
"innererror": {
"transactionId": "5E5979C16CCA6B80E10080300A418016",
"timestamp": "20200304191632.938",
"Error_Resolution": {
"SAP_Transaction": "Run Troubleshooting UI on Gateway Cockpit. Check for entries with the timestamp and transaction id above for more details.",
"SAP_Note": "See SAP Note 1964574 for error analysis (https://service.sap.com/sap/support/notes/1964574)",
"Additional_SAP_Note": "See SAP Note https://service.sap.com/sap/support/notes/0000000000. This SAP Note contains application specific information on the backend."
},
"errordetails": [
{
"code": "ZCHR_FIORI/074",
"message": "Dias de gozo não podem exceder os 30,00000 dias de direito",
"propertyref": "",
"target": "/$batch/Prdia",
"severity": "error"
},
{
"code": "ZCHR_FIORI/080",
"message": "Opções selecionadas ultrapassam o saldo remanescente de 30 dias de férias",
"propertyref": "",
"target": "/$batch/Prdia",
"severity": "error"
},
{
"code": "ZCHR_FIORI/000",
"message": "Erro na validação da programação - consulte o log",
"propertyref": "",
"target": "",
"severity": "error"
}
]
}
}
}
--batch_458e1029-1ab2-42f3-aeac-bca2fab52215
Content-Type: application/http
Content-Transfer-Encoding: binary

RESPONSE OF MESSAGE NOT HANDLED
HTTP/1.1 400 Bad Request
DataServiceVersion: 1.0
Content-Type: application/json
Content-Length: 786

{
"error": {
"code": "",
"message": {
"lang": "pt-BR",
"value": "A pessoa já está sendo process.por C19090012"
},
"innererror": {
"transactionId": "5E5FB8D692548B80E10080150A418016",
"timestamp": "20200304191841.885",
"Error_Resolution": {
"SAP_Transaction": "Run Troubleshooting UI on Gateway Cockpit. Check for entries with the timestamp and transaction id above for more details.",
"SAP_Note": "See SAP Note 1964574 for error analysis (https://service.sap.com/sap/support/notes/1964574)",
"Additional_SAP_Note": "See SAP Note https://service.sap.com/sap/support/notes/0000000000. This SAP Note contains application specific information on the backend."
},
"errordetails": [
{
"code": "ZCHR_FIORI/000",
"message": "A pessoa já está sendo process.por C19090012",
"propertyref": "",
"target": "",
"severity": "error"
}
]
}
}
}
--batch_75bbb6fe-bfc2-4245-977f-65e929af7464
Content-Type: application/http
Content-Transfer-Encoding: binary

[RDamos]

I am experiencing the same issue

[ivomenezes]

Same issue when implementing MessagePopover

[d3xter666]

Hi @KCezar ,

Could you provide a working JSBin sample so we could see the whole scenario?

Currently, I could only see some failing requests and application handling of the messages in the MessagePopover.

Yes, the MessagePopover could self subscribe to messages from the MessageManager, but this is in the case where nothing has been bound to the MessagePopover.
In your case, it seems that:

• the application does this
• the "message" model collides with the internal message model.

Could you provide working a sample, so we could debug a bit further?

Cheers

[KCezar]

Hi @d3xter666 ,
I made a more complete debug with my team, we discovered the following scenario:
The backend throws an exception, with a list of details;
The messagemanager does the message handling process;
When building on the model it duplicates one of the errors, with the same target, the target being the name entityset called;

The work around was to place a fixed target for a certain exception. But even so, he duplicates the message, puts the fixed number and the other, the name of the entityset.

Sorry I can't provide an example in Jsbin.

[Shtilianova]

Hello @KCezar ,
Thank you for sharing this finding. I've created an internal incident 2080375414. The status of the issue will be updated here in GitHub.
Regards, Diana

[Shtilianova]

Hello @KCezar ,
With provided information we are not able to debug the issue. Please provide isolated reproducible example via jsbin or url to the application with instruction how to reproduce the issue.
Regards, Diana

[ctapisab]

Having the same issue as well

[Shtilianova]

Hello @ctapisab
Could you help us investigate the issue by providing a reproducible example via jsbin ?
Regards, Diana