Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Valeo
Contributor
Contributor

SQL Values not being retreived

I am trying to load a SQL view into QlikSense.

When I look at my view in PL/SQL I can see the following values.

COMPANYACC_YEARACC_PERIODGL_ACCOUNTCOST_CENTREVAL1VAL2
SFL20201250500850154919.8313333.33
SFL20202250500850152454.0413333.33
SFL202032505008501535269.2413333.33
SFL2020425050085015013333.33
SFL2020525050085015013333.33
SFL2020625050085015013333.33
SFL2020725050085015013333.33
SFL2020825050085015013333.33
SFL2020925050085015013333.33
SFL20201025050085015013333.33
SFL20201125050085015013333.33
SFL20201225050085015013333.33
       

 

When I load this into Qlik through a script I get the following...

SCRIPT:

T:

LOAD COMPANY,
"ACC_YEAR",
"ACC_PERIOD",
"GL_ACCOUNT",
"COST_CENTRE",
VAL1,
VAL2;
SQL SELECT COMPANY,
"ACC_YEAR",
"ACC_PERIOD",
"GL_ACCOUNT",
"COST_CENTRE",
VAL1,
VAL2
FROM IFSAPP."CR_QLIK_GL_OHSUM1";
store T INTO [lib://QLIK DEVELOPMENT SOURCE (valeofoods_s-cognossvc)/GL Balances_Budgets.QVD] (QVD);
Drop Table T;

 

QVD Shows the Values as :

COMPANYACC_YEARACC_PERIODGL_ACCOUNTCOST_CENTREVAL1VAL2
SFL2020125050085015013333.33
SFL2020225050085015013333.33
SFL2020325050085015013333.33
SFL2020425050085015013333.33
SFL2020525050085015013333.33
SFL2020625050085015013333.33
SFL2020725050085015013333.33
SFL2020825050085015013333.33
SFL2020925050085015013333.33
SFL20201025050085015013333.33
SFL20201125050085015013333.33
SFL20201225050085015013333.33
       

 

The Values for Period 1, 2 or 3 are not retreived.

 

6 Replies
Gysbert_Wassenaar

Are you sure you're looking at the same records? What I mean is are there really only 12 records retrieved by you PL/SQL statement? And is that the exact same statement that you use to retrieve the records for the qvd? If there are more records than those 12 then is it possible there are records for period 1 where the VAL1 value is 0?

And what are you using to look at the data from the qvd? A qvd viewer or Qlikview or Qlik Sense?

 


talk is cheap, supply exceeds demand
Valeo
Contributor
Contributor
Author

Yeah, it's the same view I'm looking at.

I have limited my view in SQL to only these 12 records.

 

Valeo
Contributor
Contributor
Author

Also I used a QVD Viewer to view these records, but even when I connect to my SQL database in the Load script and preview the data I can see that the values for VAL1 are all zero.

Gysbert_Wassenaar

Are you sure you're looking at the same source database and table?

Are you using the same user with the same priviliges?

Does the ODBC/OLEDB driver have a limitation with regards to the field type of VAL1?


talk is cheap, supply exceeds demand
Valeo
Contributor
Contributor
Author

No Limitations as far as I'm aware.

I have connected to this database multiple times over the past few months and retreived data from tables/view in this database with no issues. This is the first time I have come across this issue.

Gysbert_Wassenaar

Is there a difference in transaction isolation levels? In other words could you be seeing data in PL/SQL that isn't committed yet and thus not visible to what you see in Qlik Sense or vice versa?


talk is cheap, supply exceeds demand