Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsAs temporary workaround, one of the followings can be used (choose 1 of 3):
1) increase maximum char count for problem column
2) change VARCHAR and VARCHAR2 problem column type to NVARCHAR or NVARCHAR2
3) update all existing queries (which have truncated data) with following syntax:
SELECT "COLUMN1",
"COLUMN2",
CAST(COLUMN3 AS NVARCHAR2(100)) as "COLUMN3" ,
CAST(COLUMN4 AS NVARCHAR2(100)) as "COLUMN4",
"COLUMN5"
FROM "OWNER_NAME"."TABLE_NAME";
where:
COLUMN1, COLUMN2 and COLUMN5 are normal columns without problems.
COLUMN3 and COLUMN4 are columns with truncated data.
We can use any value instead of 100 - this number was chosen because customer has same string size.
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us