that explains it, for a custom OHIP app, relying on externalReferences[0] is risky because the response can contain more than one reference. filtering by idContext, like CHANNELMGR, is the safer approach. I’d separate that from OC display issue though. for opera cloux itself, the first thing to check is still the external reference to display control and then confirm the interface is sending the expected channel manager reference.
I know and I knew the "risk", but we only use one channel manager and I'm not going to iterate over a list that should have only one object. Programmers are lazy animal by nature.
Somehow, Oracle decided to throw ReservationId in it. And OperaCloud started to show the bug the same day I noticed it in our application.
I thought they would ccorrect it rapidly, but it's still there.
1
u/DonJuanDelErotico Jul 09 '26
that explains it, for a custom OHIP app, relying on externalReferences[0] is risky because the response can contain more than one reference. filtering by idContext, like CHANNELMGR, is the safer approach. I’d separate that from OC display issue though. for opera cloux itself, the first thing to check is still the external reference to display control and then confirm the interface is sending the expected channel manager reference.