#MuleSoft Community Posts13 debatiendo

In Mule 4, you can convert JSON data to PDF by first transforming the JSON into an HTML or other printable format and then generating the PDF using a suitable PDF library or connector. 

For simple datasets, DataWeave can be used to format the JSON values into an HTML document, which can then be converted to PDF. If you have a large JSON file or need a more straightforward approach without developing a custom Mule flow, a dedicated tool can be easier.

Hi Vya, 

Here's the DataWeave 2.0 script for this filter (ComplteDate <= today + 180 days): 

%dw 2.0 

output application/json 

var cutoffDate = (now() as Date) + |P180D| 

--- 

payload filter ( 

    (item.ComplteDate as Date {format: "yyyy-MM-dd"}) <= cutoffDate 

) 

Applied to your sample payload, this returns: 

%dw 2.0 

output application/json 

var cutoffDate = (now() as Date) + |P180D| 

--- 

payload filter ( 

    (item.ComplteDate as Date {format: "yyyy-MM-dd"}) <= cutoffDate 

) 

Key points on how this works: 

1. now() returns the current DateTime. Casting it to Date strips the time portion, so you're comparing pure dates, not datetime with time-of-day noise. 

Reference:

2. |P180D| is a Period literal representing 180 days, this is DataWeave's native way of expressing durations (Period type), introduced in DataWeave 2.4.0. Adding it directly to a Date value shifts the date forward by that period. 

Reference:

3. item.ComplteDate as Date {format: "yyyy-MM-dd"}: your ComplteDate field comes in as a String ("2028-05-01"), so it needs an explicit cast to Date with the matching format before it can be compared against another Date value. Comparing a String directly against a Date will not work correctly. 

4. filter iterates the array and keeps only elements where the condition evaluates true, standard DataWeave array function, no import needed for filter itself (only the Dates/Periods module functions need explicit import if you use more advanced ones like today() or the dw::core::Dates module functions). 

If you'd rather use the more explicit Dates module (cleaner syntax for date-only arithmetic, avoids DateTime timezone quirks entirely): 

%dw 2.0 

import * from dw::core::Dates 

output application/json 

var cutoffDate = today() plusDays 180 

--- 

payload filter ((item.ComplteDate as Date {format: "yyyy-MM-dd"}) <= cutoffDate) 

Reference:

Either version works, the second is arguably more readable for pure date math since it avoids mixing DateTime and Date casting.

Hi @Vidyasagar Mundhe​ ,

Check this script:

%dw 2.4
output application/json skipNullOn="everywhere"
var payload = [
  {
    "personal_information": {
      "first_name": "Emiliano",
      "middle_name": "Romoaldo",
      "last_name": "Lesende",
      "ssn": "001-08-84382"
    },
    "login_information": {
      "username": "3miliano",
      "password": "mypassword1234"
    }
  },
  {
    "personal_information": {
      "first_name": "Mariano",
      "middle_name": "Toribio",
      "last_name": "de Achaval",
      "ssn": "002-05-34738"
    },
    "login_information": {
      "username": "machaval",
      "password": "mypassword4321"
    }
  }
]
 
var sensitiveFields = ['ssn','password'] map upper($)
 
fun processValue (value,key) = if(typeOf(value)~=Object) removeSensitiveData(value) 
                                    else 
                                (if ((sensitiveFields contains upper(key))) null else value)
fun removeSensitiveData(item) = item mapObject (value,key) -> (key): processValue(value,key)
 
---
payload map removeSensitiveData($)

Here I'm walking first through the array of elements, and per each element I'm doing the mapObject. Then I'm checking in a recursive way if the value is an object or not. Based on that I'm removing the content of the attribute if the key is in the list sensitiveFields. With the skipNullOn directive I'm removing it from the result.

Be aware that it won't remove object in this code, only values.

Hope it helps

Good luck!

Juan Cruz Basso

Hi @tejakkk ,

Could you try using next?

%dw 2.0

output application/java

---

{"employees":{

"employee":

(payload.employees.*employee map{

"name":$.name

} )

}

}

I hope the above helps! If you have any doubt do not hesitate to contact me.

Regards,

Arianna Flores

Hi Stephanie, 

A few things that might help, since

's own channels. 

1. Why you're getting bounced back on Support 

The

Support/Case portal is only available to Professional or Enterprise paid subscribers. If you're on the Free tier, submitting a case there will redirect you, since free users are directed to the Community Forums instead of direct support tickets. That's likely why you keep getting sent back to the home page. 

2. Alternative way to reach them 

If the in-app Help Center login loop won't let you submit a ticket, you can email them directly instead:

This bypasses the portal login issue entirely. 

3. On the login-loop / repeated failures 

Since you've already cleared cache, tried incognito, and different browsers, a few other things worth checking with your Salesforce Admin (if you're not the Admin yourself): 

   - Setup > Connected Apps OAuth Usage — check if

shows a "Blocked" status with an "Unblock" button next to it. If so, it needs to be unblocked there. 

   - Check if your Profile has "Enforce Canvas UI" enabled under Settings > User Profile — if so, you may only be able to log in through the embedded canvas app inside Salesforce, not the standalone

website. 

   - Confirm there are no IP restrictions on your Profile blocking

's published IP addresses. 

   - Confirm "API Enabled" is checked on your Profile under Administrative Permissions. 

4. If uploads keep failing (not just login) 

Since you mentioned it's taking 20-30 attempts to get an upload through, and not just login issues, this could also be an intermittent platform issue on

's status/community forums to see if others are reporting the same thing around the same dates — that'll tell you if it's a known outage versus something specific to your org's setup. 

Given the support portal limitation, the email route (

Greetings, @Nate Schaufler

From the outside looking in, it looks like you have all the required fields. Can you do the following to confirm that you are not missing anything: 

1. Export one working EventRelation record (from an event that already has a contact) 

I suspect you might have to use TRUE & FALSE instead of 1 & 0. 

Be well- 

Katende 

Use Data Loader → Export → EventRelation 

Export fields: EventId, RelationId, IsInvitee, IsParent 

This lets you see the correct structure and flag values.

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