Forum Discussion
Thanks Prashant for your answer.
Think I didn't explain myself.
My format numbers are European (actually Brazilian that further complicates UTF-8 issues)
A.- In a pipeline I read one number.
B.- In another step I copy that number to another table that is also European formatted
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.
I thought maybe I could force with a jinja expression to keep the format 123.456,78 (European)
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+ which I solved transforming the number to text format.
------------------------------
eduardo valdes
------------------------------
Thanks for the explanation. You can similarly force the number to text in Jinja as well with a string filter
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.
Maybe you can also see how pipeline is reading by checking the logs , that's how I discovered the milliseconds .
------------------------------
Prashant Maheshwari
------------------------------