Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Q&A with Qlik - Qlik Cloud Migration: Questions about migrating to Qlik Cloud? Catch the latest replay!
cancel
Showing results for 
Search instead for 
Did you mean: 
Domenico_Arcamone
Contributor
Contributor

Numeric values from VSAM lose comma in BigQuery via Qlik Replicate

Hi all,

I’m facing an issue with decimal values coming from VSAM via ARC Studio and replicated to BigQuery.

  • ARC field type: NUMSTRING_U
  • Source value: 123,12
  • Target (BigQuery via Qlik Replicate): 123

So the decimal part is lost during replication.

Has anyone experienced this behavior?
Is there a recommended way to handle comma-based decimal values (e.g. replace with dot or change data type) before replication?

Thanks in advance!

Labels (1)
1 Solution

Accepted Solutions
Rahul_Kale
Support
Support

Hello Domenico_Arcamone,

Thank you for reaching out to the Qlik community,
 

This is expected behaviour. Your value 123,12 is treated as a string / localized number. BigQuery expects a dot (.) as decimal separator and interprets a comma as thousands separator → so 123,12 becomes 123. Also, Qlik Replicate may map such fields as STRING (e.g. NUMSTRING_U), losing decimal semantics unless explicitly cast. 

The best fix for this:- 

  • Best: replace before replication:-
    REPLACE(col, ',', '.')

  • Or cast in BigQueryCAST:-
    (REPLACE(col, ',', '.') AS NUMERIC)

Recommendation: Convert to proper numeric (DECIMAL) before replication to avoid data loss.

View solution in original post

2 Replies
Rahul_Kale
Support
Support

Hello Domenico_Arcamone,

Thank you for reaching out to the Qlik community,
 

This is expected behaviour. Your value 123,12 is treated as a string / localized number. BigQuery expects a dot (.) as decimal separator and interprets a comma as thousands separator → so 123,12 becomes 123. Also, Qlik Replicate may map such fields as STRING (e.g. NUMSTRING_U), losing decimal semantics unless explicitly cast. 

The best fix for this:- 

  • Best: replace before replication:-
    REPLACE(col, ',', '.')

  • Or cast in BigQueryCAST:-
    (REPLACE(col, ',', '.') AS NUMERIC)

Recommendation: Convert to proper numeric (DECIMAL) before replication to avoid data loss.

Domenico_Arcamone
Contributor
Contributor
Author

Hi Rahul,

thanks for your reply, very clear.

Just to add: I also tried converting the field to a decimal type directly in ARC Studio, but in that case the value with comma (e.g. 123,12) is not correctly handled and the decimal part is still not preserved.

So I was wondering if there is any alternative way to handle this directly in ARC (e.g. field definition, formatting, or transformation), instead of applying the conversion in Replicate or BigQuery.

Thanks again for your support!