MuleSoft Feed

 The best way to retain tracking fields like CorrelationId while using a time-based aggregator and aggregator listener in MuleSoft is to explicitly persist and propagate the value as part of the aggregated payload or metadata, rather than relying on flow variables alone (since they are not automatically preserved across aggregation boundaries). Typically, you should include the CorrelationId in the message payload, attributes, or as a custom object before aggregation, and configure the aggregator to group based on that CorrelationId. When the aggregator completes, ensure the aggregated result still contains this field so that the aggregator listener can access it. A common and reliable approach is to store the CorrelationId in an Object Store or external persistence if needed for long-running aggregations, and always map it back into the final message structure, ensuring end-to-end traceability across asynchronous processing. 

Hello, 

Please try the below dataweave.  

%dw 2.0

output application/java

---

"[Booking Loca] in (" ++

((payload[0]."Booking Loca" map ("'" ++ ($ replace "'" with "''") ++ "'")) joinBy ",")

++ ")" 

Thanks!

Data Loader does not require a System Administrator profile.

Any user can use Data Loader as long as:

•  They have the appropriate Salesforce permissions (such as API Enabled). 
•  Their profile or permission sets grant the necessary object-level permissions (Read, Create, Edit, Delete, etc.). 

Object restrictions: Yes, a user can be restricted to specific objects. Data Loader only allows operations on objects for which the user has the required permissions.

Record restrictions: Yes, record-level security still applies. Data Loader respects:

•  Organization-Wide Defaults (OWD) 
•  Role Hierarchy 
•  Sharing Rules 
•  Manual Sharing 
•  Teams/Territories (where applicable) 

Therefore, a non-admin user can use Data Loader, but they will only be able to access and modify the objects and records that their Salesforce permissions and sharing settings allow.

Note: Some Data Loader operations (for example, exporting all records using special permissions such as "View All Data" or modifying records they do not normally have access to) require additional permissions that are typically assigned to administrators.

Hi @Elisabeth Guinard

, 

I'm just checking my notes. I think the schedulers reappeared for me by themselves after a little while. I also found that, although they weren't showing in the UI, the schedulers were still running.

Are you seeing something similar?

Just a couple of questions:

• Are you deploying them using Anypoint Exchange V3?
• Do you have a development environment for the API? If so, are the schedulers visible there?

Kind regards,

Dan

You can simplify it. In Mule 4 DataWeave, you usually don’t need input payload application/json. Just use:

%dw 2.0
output application/json
---
{
  myRootElement: payload
}

The payload type comes from the message metadata/header (content-type: application/json).

Hi @Richard Muhumuza

Please refer to the below link - 

https://www.youtube.com/watch?v=-2OS6QylZQ0

If you are targetting to upload files under any specific record - mention the same under FirstPublishLocationId. 

If you want the files to be uploaded under the Salesforce Files - give your user Id under  FirstPublishLocationId.  

You can try with workbench by omitting the ContentDocumentId field - works this way too

Hey,

Another way to do it first create query variable and store below DataWeave logic

%dw 2.0
output application/json
var data = {
    "name": "Mule",
    "phone": "888888888",
    "balance": "2000",
    "billingCity": "London"
}
---
"UPDATE account SET " ++
((data filterObject ((value, key, index) -> (value != null and value != "")) mapObject ((value, key, index) -> {
    myData : (key as String) ++ " = :" ++ (key as String)
})).*myData joinBy  " AND ") ++ "WHERE idaccount = :accID"

Its gives you query like below I have stored it query variable

"UPDATE account SET name = :name AND phone = :phone AND balance = :balance AND billingCity = :billingCityWHERE idaccount = :accID"

Another DataWeave to stored the input parameters its stored like below DataWeave

%dw 2.0
output application/json
var data = {
    "name": "Mule",
    "phone": "888888888",
    "balance": "2000",
    "billingCity": "London"
}
---
{
    idaccount : "12345678"
} ++ 
(data filterObject ((value, key, index) -> (value != null and value != ""))) default {}

Output

{
  "idaccount": "12345678",
  "name": "Mule",
  "phone": "888888888",
  "balance": "2000",
  "billingCity": "London"
}

And Finally in the DataBase Update Operation I have provided the both variable query and inputparametes as below

SO its dynamic with Paramterized.

Regards,

Shekh