Open BerndZw opened 1 year ago
Okay, let's work on this together. Changes needed for Oracle are no problem, for PowerBI we need to be a bit careful. The beauty of a standard, you know: Everybody interprets it differently.
Regarding the last question, I would remove the $format=json
from the URL.
The normal way is that the caller adds a http header of the expected format, json or xml, and the odata library provides the data in this format. The $format=
provides an option to overrule that, which is handy for browsers.
I have considered Oracle and PowerBI before but thought that Oracle has a Restful interface and for PowerBI you would access databases directly, not via OData. Therefore I cam to the conclusion it is not important. Given that you are using both, I am obviously missing something why this is a valid use case and should be supported. Any input?
wasn't aware of this, to be frank. Will inquire with our Oracle team...
Thank you very much for providing this!
We are also interested in using odata primarily in order to get data from an Oracle database in PowerBI.
I got this to work in general with our Oracle DB, but when using this as an OData source from PowerBI or Excel, I am encountering issues, see attached pdf.
Thanks for any pointers on this.
Best regards, Bernd
JDBCoData_PowerBI.pdf