I am using Aggregator and HTTPCaller in conjunction with eachother to create an API POST URL and am having issues with the Aggregator output and URL encoding.
I'm using Aggregator to concatenate and merge records and am using a separator of "&fee_id=" as the field will end up as part of the query string parameters:
The output is correct:
But when I run HTTPCaller and view the URL that ends up getting generated in the translation log, only the "&fee_id=" that was added by the aggregator gets messed up.
Example:
https://TARGETURL.COM?api_key=KEY&amount=2000&PARAM1=50&payment_method=PYMT&paid_timestamp=20220628000000&transaction_id=yna4EcJMDk6gBvcEce0wlg&fee_id=EPVDnnsMl0K9Qj91eyKOWg%26fee_id%3DXjix%2FpQsd0aKiT9Ikn4aWw
I have tried various combinations and orders of the TextEncoder, TextDecoder and StringReplacer transformers to try and force the URL to format correctly, but I'm not having any luck. I've also tried setting different Content Types in HTTPCaller.
Anyone have any suggestions, or maybe an alternate way of accomplishing this? I would like to use FME to do the aggregation of the field instead of doing it DB-side if possible.