Number formatting in pipelines.

Question

Number formatting in pipelines.
&nbsp;
I am trying to pass some number values in a pipeline.
Simple from one table to another
&nbsp;
My number formats are 123.456,78. I don't use 123456.78 or 123,456.78
&nbsp;
Pipelines only work if the original number format field and the destiny field both are formatted with 123456.78.
&nbsp;
Other setting multiplies de number by 10.
&nbsp;
Have tried to look up the record before copying the value.
&nbsp;
Only works with a run import API call, but I have to complicate the pipeline to use run imports….
Use a shadow table, transform the data and do an api call, merging the tables.
&nbsp;
Is there a jinja transformation needed that can solve the problem?
&nbsp;------------------------------eduardo valdes------------------------------

prashantmaheshw · Answer

This is Straight cut and paste from chatGPT , maybe useful to you , since I have never across this number format (I am from India)

---&nbsp;

Yes, in Quickbase with Jinja templating, you can manipulate the format of numbers to suit your needs.
Given the number format you've mentioned (123.456,78), it seems you're using a European-style number format where the period is used as the thousands separator and the comma is used as the decimal separator.
If you want to convert this format (123.456,78) to a more standard format (123456.78), you can use Jinja's string manipulation capabilities.
Here's a step-by-step breakdown:
1. Replace the period (.) with nothing, effectively removing it.2. Replace the comma (,) with a period (.).
Here's how you can achieve this using Jinja:
{% set number_str = '123.456,78' %}
{% set standard_format = number_str.replace('.', '').replace(',', '.') %}
{{ standard_format }}
This will give you `123456.78`.
Now, if you have this number in a field in Quickbase, you'll have to reference that field in your Jinja template, and then apply the above transformations.
Remember, this approach assumes that your number is always formatted with a period as the thousands separator and a comma as the decimal separator------------------------------Prashant Maheshwari------------------------------

eduardovaldes · Answer

Thanks Prashant for your answer.
&nbsp;
Think I didn't explain myself.
&nbsp;
My format numbers are European (actually Brazilian that further complicates UTF-8 issues)
&nbsp;
A.- In a pipeline I read one number.
&nbsp;
B.- In another step I copy that number to another table that is also European formatted
&nbsp;
The number gets multiplied by 10. 
Seem that in the middle the number is converted to 1234546.78, and in the import process the 2 numbers are in different formats.
&nbsp;
I thought maybe I could force with a jinja expression to keep the format 123.456,78 (European)
&nbsp;
I am going to try performing a Bulk upsert to see if that works.
When I perform an api call (run import) numbers keep their formats.
I remember I had a similar problem with exact forms+ &nbsp;which I solved transforming the number to text format. ------------------------------eduardo valdes------------------------------

prashantmaheshw · Answer

Thanks for the explanation. You can similarly force the number to text in Jinja as well with a string filter&nbsp;
Pipeline is pretty stiff currently when it comes to interpreting few things , for example all duration fields are stored in milliseconds, it could be doing something similar to you number fields by stripping comma , but I am not clear with this.&nbsp;
Maybe you can also see how pipeline is reading by checking the logs , that's how I discovered the milliseconds .&nbsp;------------------------------Prashant Maheshwari------------------------------

Forum Discussion

Number formatting in pipelines.