#MuleSoft Community Posts35 discussing

I have requirement to call PATCH method of a resource where user can update of the details mentioned in the request . Account ID which is the key is passed as URI. User can update any or all of these parameters. Since request parameters are not fixed i need to dynamically build UPDATE query.

{

   "name": "Mule",

"phone": "888888888",

"balance": "2000",

"billingCity": "London"

}

Below is the dataweave that is written to build set query. I have tried all combinations to execute update query.

%dw 2.0

import * from dw::core::Strings

output application/json 

---

((({

name: payload.name default "",

phone: payload.phone default "",

balance: payload.balance default "",

billingcity: payload.billingCity default ""

}pluck (($$)++'='++"\""++($)++"\"") ) 

reduce(item, acc="")-> acc ++ (if(!isEmpty(substringAfter(item,"="))) item++"," else "")) substringBeforeLast(",")) as String 

DB query

UPDATE account

SET :query

WHERE idaccount = :accID

Input parameters

output application/java

---

{

query: vars.query,

accID: attributes.uriParams.accID as String

}

vars.query is expected as name="Max",phone="9999999999",balance="20000",billingcity="Bangalore" to work properly. However it is not working . Tried replacing escape character with "" but then it doesnt work.

"name=\"Max\",phone=\"9999999999\",balance=\"20000\",billingcity=\"Bangalore\""

Kindly let me know if any better ideas to make this work

I am getting below error as I have a HTTP requester node where we have a PUT call so there is no response body.

So while creating inbound response we get below error on Transform node.

Unable to parse empty input, while reading `payload` as Json

If I do a setPaylod like below with empty body then it works.

<set-payload value="#{}" doc:name="Set Payload" doc:id="4d3edefb-a8c4-43af-bfa4-4625f536509f" />

However I am looking for a solution to handle this in the transform node itself.Please let me know how to handle this in transform node in the best possible way ?

Important Update: Anypoint Platform is migrating to a New Email Server System starting April 6, 2026What’s changing:

Starting April 6, 2026, we are transitioning Anypoint Platform’s mailing distribution system to Salesforce Marketing Cloud Next. As a result, you or your company-provided mail server will begin receiving emails from the new email system, which will use new sender (‘from’) and reply-to (‘reply-to’) addresses. 

This transition period begins April 6, 2026, and we expect all emails to be sent exclusively from the new processing system by April 30, 2026. Between April 6, 2026 and April 20, 2026 your server will continue to receive emails from both the existing and new systems. 

Why is this changing:

Anypoint Platform is transitioning to a new email distribution system to improve security and resilience of our email alert notifications service. 

What do you need to do:

To continue receiving all necessary communications from Anypoint Platform, take these actions:

1. Configure your email server system to allow emails from the new email processing system, which uses the new sender and reply-to addresses. 
2. Update configurations in your email server to prevent Anypoint Platform emails from being incorrectly identified as spam. 

Review this Knowledge Article for more details on how to prepare for this upcoming change and implement changes. We request that you take these actions because MuleSoft doesn’t have knowledge about your email server or configurations to automate this on your behalf. 

What happens if you don’t make the change:

If you don’t make this change, then effective April 6, 2026 you will risk losing access to critical emails from Anypoint Platform. This change does not affect your runtime APIs or integration flows. 

We appreciate your attention to this important update, and your partnership in keeping our ecosystem secure. For questions, contact your MuleSoft account team.