Hi Jici
Besides that last method, I’ve also tested with and without quotation marks.
I did this by combining it with safe JSON in the Workflow, trimmed,
etc., all combinations. Always testing by looking at the result step
by step.
I await your information.
Jici, ok.
I'll do that, but I've done it before.
Secure JSON preserves the value but creates quotation marks around it. I'll do it now and show you.
Thank you very much
hi Jici
Hi Jici
Look, that didn't work either. See the screenshots of the connector API, workflow (strings with safe JSON), and the screenshots of the steps.
Note that all the data that should be passed is intact.
thank you
Can you now, send the request to a beeceptor endpoint and provide the result of beeceptor (data received), also include headers screenshot)
You can also inspect, using step by step or logs, what is provided in customer field. (actually, the error is related to that)
Hi Jici, I received a response from ASAAS.
From the screenshot, the body is completely empty.
I will send a screenshot of the ASAAS response.
I’m having this serious problem here.
You confirmed with my screenshots that the values are correct up to the last step of the workflow.
I don’t have any problems with the call headers, because the initialization call works fine.
I need Bubble to consider this a serious problem and give it maximum attention.
I will await your urgent action.
Best regards,
Felix Mauricio
Campos com valores você DEVE enviar formatado com o separador decimal PONTO e não virgula.
Errado: 1.000,00
Correto: 1000.00
You didn’t sent the screenshot of beeceptor. But the issue is how you are providing data to the dynamic value. Privacy rules? Reference to the correct information? (you are using a lot of current cell… is there’s something in this current cell value?
The problem is not Bubble… this is on your side and settings.
Will send you a PM later.
Olá Nilson
Boa tarde.
Eu vou formatar e testar novamente.
Obrigado.
Att,
Nilson
Mesmo modificando o formato no meio de pagamento (workflow), formatou incorreto para os EUA.
Algum recurso para forçar enviar certo?
Teoricamente, teria que enviar como está no banco (eua), por isso não formatei, e não observei.
Veja os prints.
Abraço,
Value is a comma and not a dot. Format the number differently using :formatted as. No thousand separators (no separators at all)
Also, you provided screenshot with json formatted but it doesn’t look like it’s applied because the value doesn’t have the encoding… that sound strange and could be a bug in this case. But without sending it to a tool like beeceptor, it’s always hard to know exactly what was sent.
Hi
I'm using the format as it is, in the US standard. It should be formatted correctly, but it didn't work. I tried again, including only decimal, it didn't work, it didn't format.
I'll also track it with the beeceptor.
See the screenshot.
Hi
Is it possible that this field could invalidate the entire call?
Keep in mind theses debugging tools for API: jsonlint to validate JSON structure, beeceptor to inspect payload and headers sent by Bubble and Bubble logs to have more informations about the request.
I totally agree that the error message could be better from this provider.
Hi
Problem solved.
Using Beeceptor, I managed to find part of the problem, which was the formatting of the billing amount. I had formatted it in the workflow, but it only resolved after clearing the cache.
By the way, Bubble should improve the detailed guidance on markers.
That only worked with < > without quotes and using JSON safe.
Sorry, but I was already going crazy.
The return message (400) from Asaas didn’t help either, because that should show the problematic amount.
Thank you very much for everything.