Forum Discussion

gsalas's avatar
gsalas
Advocate II
9 years ago
Solved

Direct Import ODBC connector does not return all rows

Hi Everyone!  I have encounted an extremely strange issue with the ODBC connector on the Direct Import funciton in Power Bi Desktop.  The ODBC connector is not returning all rows on a query.  When I run the SQL query below:

 

select date, caller_number, duration, numlookup_state, numlookup_zip, ipRegion, ipPostalCode from vanalyticsCBO where date > dateadd(mm,-4,getdate()) and ProgramId in (11227, 10869, 11697, 11378, 10343, 10345, 10308, 10310, 10309, 10311) 

 

I only get 4 rows on this particular "caller_number" value:

 

When I add "clickTime" to the query, I get all the values I should:

 

select date, caller_number, duration, numlookup_state, numlookup_zip, ipRegion, ipPostalCode from vanalyticsCBO where date > dateadd(mm,-4,getdate()) and ProgramId in (11227, 10869, 11697, 11378, 10343, 10345, 10308, 10310, 10309, 10311)

 

Is there some kind of row limit with Direct Import?

 

  • Anonymous's avatar
    Anonymous
    9 years ago

    Hi gsalas,

     

    It is hard to reproduce your issue, can you share something detailed?

     

    In addition you can also test with below methods:

    1. Does this issue appears if you direct run these query on your database?
    2. Has there any specific security settings on your datasource?
    3. If you use other way to get data from the datasource with the same query, does this issue fixed?

     

    Regards,

    Xiaoxin Sheng

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi gsalas,

     

    It is hard to reproduce your issue, can you share something detailed?

     

    In addition you can also test with below methods:

    1. Does this issue appears if you direct run these query on your database?
    2. Has there any specific security settings on your datasource?
    3. If you use other way to get data from the datasource with the same query, does this issue fixed?

     

    Regards,

    Xiaoxin Sheng

    • gsalas's avatar
      gsalas
      Advocate II

      I can't directly access the source data.  It is likely on the DB side, so I will mark this one as resolved.