Oracle Analytics Cloud and Server

Home› Oracle Analytics› Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Remove Extra Row of Excel Export

Received Response
131
Views
6
Comments
mrmmickle1
mrmmickle1 ✭✭✭
edited August 13 in Oracle Analytics Cloud and Server

When I use the keyboard Shortcut Ctrl + Down to go to the last used row of my spreadsheet I land on the empty row below my OBIEE data export.  I have found that sometimes when importing data into Access this extra row gets picked up, so I have been having to manually remove it in a number of reports.  Is there a setting that will allow me to eliminate this extra "blank" row?  While  I can delete the row it would be nice if I can create an export that doesn't have this extra "blank" row embedded in my data.  It is always one below the last row that contains data.  Anyone have any ideas? Is this some kid of carriage return or something that's being picked up that I can't see?

I'm not referring to the merged row that says "Rows 1-XXX".

Answers

  • ArijitC
    ArijitC ✭✭✭✭✭

    I don't think you can change it. This is how export to excel works. You can check oracle documentation here

  • Gianni Ceresa
    Gianni Ceresa mod

    Hi,

    I would say the wrong tool for the job ...

    If you export the CSV it will be faster and probably not have the issue. CSV will export the result of the query instead of export the result of the view like Excel will do.

    And last option: why don't you connect to OBIEE directly by ODBC and run a logical query against OBIEE directly to get the data?

    I was thinking at something inspired by this: https://www.rittmanmead.com/blog/2017/02/working-with-obiee-data-in-excel-using-odbc/

  • ArijitC
    ArijitC ✭✭✭✭✭

    Thanks for sharing the blog. This is good.

  • Christian Berg-0racle
    Christian Berg-0racle ✭✭✭✭✭

    Yeah for such a requirement go as direct as possible. What's the point of dragging the data into the OBIPS and then into the browser and then locally into a file when you can do it directly through ODBC while still retaining the semantic layer.

  • mrmmickle1
    mrmmickle1 ✭✭✭

    Gianni,

    Thanks so much for your response.  Just returning from vacation.  Exporting as a CSV fixed the issue.

    Christian Berg,

    I try to everything I can in the tool itself.  My OBIEE skillset isn't quite there yet, but that's why I'm here!!  Trying to learn.

  • Christian Berg-0racle
    Christian Berg-0racle ✭✭✭✭✭

    @mrmmickle1 Wasn't a comment against you. Just wanted to point out the potential for extra workload and network traffic when doing a front-end export. Most people aren't aware of this or just disregard it because "the users say it has to be like this".