Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Import from Oracle database bring null values

Hi guys,

 

We have a stranger issue in the team.

 

We are pulling one view from Oracle database, and after import in Power query we can’t see data from two columns even though these columns have value in the Oracle view.

 

For one teammate everything is fine – he can see data correctly, but for two others - the issue appears.

We tried reinstalling Power BI Desktop, but it didn’t help.

 Has anyone had similar issue? Maybe you have some ideas where to look? 

 

Thanks in advanced

 

Have anyone dealed with similar issue? Maybe you have some ideas where to look? 

 

Thanks in advanced

 

Need Help

6 Replies

  • amitchandak's avatar
    amitchandak
    Super User
    5 years ago

    Anonymous , Open data in edit query/ Data Transformation, you should see some error there in yellow color or column with error and link. If so share the error.

  • Greg_Deckler's avatar
    Greg_Deckler
    Community Champion
    5 years ago

    Anonymous - Couple questions. Is what you are showing immediately after the Source and Navigation/Promoted Headers step or later in the transformation? If later in the transformation, can you post the Advanced Editor code? If you import the data (or is this Direct?) do you get anything? Could be a security issue on the database itself. 

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Hi Greg_Deckler 

       

      Yes, it shows immediately, not just after the Source and Navigation steps, but even in data Load window.
      We use import mode. With Direct connection we get the same result.


      We had a guess that maybe there is something wrong with Power BI accounts and tried creating table in power BI Service dataflow, but in this case all three members see null in the table, even he, who can see values in PBI Desktop.


      The only different that we found, is that the person, who see values, doesn’t have installed recommended provider (‚Oracle.DataAccess.Client‘). Maybe that caused the problem?