I am trying to transfer a euro amount e.g. 99.800ā¬ into a number field in Airtable.
The good news is that Bardeen only transfers the numbers, although the ā¬ sign is marked. The bad news is that Bardeen only transfers the numbers before the dot. However, the dot is only a thousands separator.
So the question is: How do I get the complete price of 99800 into a number field after Airtaible?
Maybe I need to prepaire the marked selectors? But I do not really understand how
Many thanks for your help at this late stage. I have copied your suggestion in my environment. Unfortunately, it did not help. Only the number 99 of the amount is saved in my Airtable cell. I am attaching two screenshots here. Maybe you can see if I have made a mistake?
In the meantime I have learnt to work with regex formulas and to use them. I thought maybe I would try to remove the dot and the Euro character using the regex command. But that didnāt work either.
Iām thinking we mightāve uncovered a couple of bugs here, but tagging @vin_bardeen, @ivan to take a second look as Iām not super familiar with Airtable. Thank you!
FWIW - Iām encountering the same behavior on my end of testing that @LastSamuraj mentions:
could you please take a look on my problem?
Iām still not able to scrape a simple euro amount into an airtable digit field. As I already told above, every time I scrape e.g. this amount 90.900 ā¬, I only get the 90 as digit in my airtable field.
I think maybe the problem is the dot inside the amount. For this reason, I tried to remove the dot using a regex. But no matter which RegEx formula I tried, it didnāt work. Each time only the number 90 was transferred to Airtable.
Thanks for following up on this and for your patience while we resolved this issue. Weāve just released a new version of Bardeen (2.39.0) which is meant to have fixed this issue. Do you mind updating to the latest version and seeing if it persists for you please ?
Hello @vin_bardeen , after bardeen update to 2.39.0 the transfer of fields that are not unique no longer works. This means that all fields that worked yesterday (e.g. 300 HP, 500 km, 180 km/h etc.) are no longer transferred. And the price is not transferred either.
I get the following success message after running my workflow.
Previously, Bardeen always said: āYou are trying to use a different kind of data than the current argument expects. Bardeen will convert it, but the result may be unexpected.ā
Apparently it doesnāt work anymore since the update
Hallo @vin_bardeen I have just seen in this post that my current problem, which I have been despairing about for days, is already six months old. Have you been able to find a solution to the problem? I still have the problem that many fields cannot be assigned " due to schema mismatch.