Hi. I am facing the exact same problem with a self implemented oData API in Cloud Integration. Via trace I could verify that navigating from list report to object page the oData APIs iFlow for the requested entity is called (read operation with keys)...
I ran into the same issue storing XML payload into table in on-premise MSSQL Server because the JDBC-Adapter is not able to store multiple rows in a table. Is there any workaround or planned enhancemants to JDBC-Adapter?