tQVDOutput component data type issue

[Bhumiraj23]

I am using Talend Real-time Big Data Platform 8.0.1 May 2025 with Build id: 20250521_1150-patch. 
I am using tQVDOutput component to generate Qvd files 

But when I loaded the generated Qvd file into Qlik Sense Enterprise May 2025 the data type got changed 
Like Numeric fields got changed into text & Dates got manupulated.

In my tQVDOutput schema the datatype is interger ,big decimal only still in qvd the data type is getting converted into text. 

NOTE : When I converted date fields into string then loaded into tQVDOutput component then the dates came correctly in the QVD file when loaded into Qlik sense. Converted the date by below code in tMap

row16.DateApproved != null ? TalendDate.formatDate("yyyy-MM-dd HH:mm:ss", row16.DateApproved) : null

Is there any Bugs in tQVDOutput component ??
Is there any new patch available which can fix this tQVDOutput component issue ?

So can anyone guide me how to solve this data type issue in generated Qvd file through tQVDOutput component of talend. 

[gouravdubey5]

Hello,

This behavior is by design for the tQVDOutput component and is not a confirmed product defect in Talend Real-time Big Data Platform 8.0.1 (May 2025 patch).

tQVDOutput writes data using Talend/Java data types, but QVD field typing is determined by Qlik Sense at load time, not by Talend. As a result, numeric and date fields may be interpreted as text when the QVD is loaded into Qlik Sense, depending on value patterns and formatting.

This is why:

Numeric fields (Integer, BigDecimal) may appear as text

Date fields may be misinterpreted unless explicitly formatted

Converting dates to strings in Talend works, as Qlik Sense can then re-interpret them using its date parsing logic

At this time, there is no patch available that changes datatype enforcement behavior in tQVDOutput.

Supported and recommended resolution

Option 1 (Recommended – Qlik-supported approach):
Handle final data typing in the Qlik Sense load script, for example:

Date(Date#(DateApproved,'YYYY-MM-DD hh:mm:ss')) as DateApproved

Option 2 (Talend-side workaround):
Explicitly format date and numeric fields as strings in Talend before writing the QVD, and let Qlik Sense re-cast them during load.

Best practice

tQVDOutput should be treated as a data export mechanism, not a tool to enforce Qlik field data types. Final typing and formatting should always be handled in Qlik Sense, where QVD semantics are fully supported.

Thanks,

Gourav