Skip to main content Únase a nosotros en TDX, en San Francisco, o en Salesforce+ los días 5 y 6 de marzo en la conferencia para desarrolladores sobre la era de agentes de IA. Registrarse ahora.
Grupo destacado

* MuleSoft Composer *

Welcome! This group is dedicated to your success with MuleSoft Composer for Salesforce. Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. We look forward to seeing your MuleSoft Composer for Salesforce use cases! --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

I have two Mulesoft Composer flows that have a trigger event of record create or update in Netsuite. One is on Invoices and the other is on Credit Memos. A behavior I have noticed in both is that the runs will periodically fail on the trigger event. It looks like it may be timing out because each failed run length is the same amount of time at 1 min 30 sec. Any idea how to troubleshoot or resolve? Here is the error:  

 

Step 1

Trigger

Error Type

UNKNOWN ERROR

Error Message

java.lang.RuntimeException: Unexpected error while consuming the web service operation [search]

1 respuesta
  1. Shenoy Meghesh Umesh (Deloitte Digital) Forum Ambassador
    28 feb, 16:41

    Hi @Alison Mullins

     

    This looks like a technical error coming out of connector.  

    Kindly raise a case with Salesforce. As they can look into it more as we cannot debug the connectors . 

     

    Thanks

0/9000

As a MuleSoft customer, you have direct access to live chat for quick solutions on topics such as user permissions, runtime versions, deployments, CPU threads, Anypoint monitoring, auto-discovery API,

As a MuleSoft customer, you have direct access to live chat for quick solutions on topics such as user permissions, runtime versions, deployments, CPU threads, Anypoint monitoring, auto-discovery API, HAR files, Maven, Connectors usage, and more. 

 

To start a new Chat 💬 session:

  1. Log in to Salesforce Help
  2. Click Contact Support
  3. Enter a short summary of your issue
  4. Choose the related Product & Topic and severity choice
  5. Click the Live Chat option
2 comentarios
0/9000

Trailblazer Community Satisfaction Survey - Your input is very important!

 

Take ➡️ THIS ⬅️ brief survey (It will only take 1 min!) and let us know how was your recent Q&A experience in the Trailblazer Community.

 

Your satisfaction is very important to us; your responses are completely anonymous, and every answer you give will help us build a strong and impactful community. We greatly appreciate your valuable time and feedback. 

 

Thank you from the Trailblazer Community Team!  🙏

0/9000

Hi All,

 

I'm building an integration with NetSuite and I need to send the Order Product information "Start and EndDate" both are defined as "Date" into Saleforce, but when I try to set on field set as "Date" into NetSuite it's requested a format of DateTime.

Is there any workaround to convert in a Custom Expression a Date field into a Datetime? 

9 respuestas
  1. 6 abr 2022, 16:28

    Hi @Fabio Maturo - Great question! 

     

    We will be launching typecasting formulas in the Custom Expression Editor (like fromDateToDateTime) by the end of the month.

     

    If you need a workaround in the meantime, you can create a new formula field in Salesforce of type DateTime = DATETIMEVALUE(Date field:Start Date). This converts the Date to a DateTime and then the Composer can use that field to map to NetSuite.

     

    Keep in mind, however, that for the Salesforce formula, the time will be set to 12:00 a.m. in Greenwich Mean Time (GMT), and then converted to the time zone of the user viewing the record when it’s displayed. We recommend that the integration user should have its time zone set to UTC in both Salesforce and NetSuite.

     

    Hope this helps!

0/9000

We're making a GET HTTP callout to a REST endpoint, the example response is JSON and when the search is successful, the GET returns a value everything works as expected. However, when the search is unsuccessful (nothing found) the service returns a null body and Composer errors out (presumably trying to deserialize a null). This is a commercial endpoint that we have no control over.  

 

Is there a way in Composer to check the response before the deserialization attempt occurs? We can't find a way to avoid this error.  

 

Thanks!

1 respuesta
  1. Shenoy Meghesh Umesh (Deloitte Digital) Forum Ambassador
    13 feb, 16:59

    Hi @Kelley Austin

     

    1. This behaviour is part of the HTTP Connector and not related to the external system. 

    2. In order to bypass it you can use the Error handling blocks in MuleSoft Composer to efficiently process the data if returned from the external systems and if not then execute other set of actions.  

    3. You can refer to this video:

    https://youtu.be/gzjEpvjJt-k?si=ChmEgPlyMjXO6fnX

     

     

    Thanks 

     

0/9000

Hi guys, I am going through the practice exam and of possible, I would like help with the following question:

 

the table Score says the correct answer is (A) but I think it returns a JSON object (C).

 

What do you guys think is the correct answer?

 

AnyAirlines has a MuleSoft RPA process that automates the process of extracting payroll data from

PDF files and uses it to construct a JSON array. In a MuleSoft Composer flow, there is an action step

that invokes this RPA process and uses the response in the same flow.

What is the output type of the response in MuleSoft Composer?

A List

B Map

C Object

D String

1 respuesta
0/9000

🎉 🎉 🎉 WELCOME 🎉🎉🎉   

 

We're back in action on this marvelous Monday to welcome some new members! Team, as always, please join me in sending a HUGE WELCOME to our newest  @* MuleSoft Composer *  AND  @* MuleSoft RPA *  Community Members that joined the last week!  

 

📌 Consult our Community 📌

 

Get the tips and tricks you need to access the full potential of MuleSoft Composer & RPA with these helpful Community resources:

 

  • Community Groups: The  @* MuleSoft Composer *  and  @* MuleSoft RPA *  groups serve as a designated space for you (and your team!) to stay up to date on the products, learn best practices, review resources, ask questions, and share experiences with other automation enthusiasts. 
  • Trails: Refer to Trailhead modules for more in-depth training, like helping your team understand the fundamentals of MuleSoft Composer + MuleSoft RPA
  • Community Meetups: Learn, network, and share with MuleSoft professionals and enthusiasts in cities near and far. Check out our Composer and RPA product group to find a list of our recorded enablement sessions so you can continue to level up your flows. 

We know finding your way around a new product can take some time, but we’re here to help. Join us by saying "hello" in the thread below to get started today!

 

Welcome 👏👏👏 @Priyanka Shankarpale @Edna Nayibe Palma Hernandez @Femi Agbaje-Williams @saqib syed @Madhu Salukhe @Anurag Bhardwaj @Leslie Utley @Sergio Carvalho @Priscilla Botirca @Tadalapur jaipal S @Rammohan Rao Palle @Katie Stewart @Ian Bennett @Souhila Bellakrach @Tushar Rahane @Pruek Siriwatcharakul @Nicolas Meier @Vibha Srivastava @KARIM MAAB MARA @Mahathi K 👏👏👏 

 

We're so happy you are here! 

4 comentarios
0/9000

Hello, 

 

is there anyone who can help me clear something out? In the practice exam for question nr. 18. the correct answer is C. And i don't get it, why not A (payload + queryParam)? 

 

According to: https://blogs.mulesoft.com/dev-guides/api-design/mule-flows-101-types-attributes-variables/

 

in Http request the payload and query params are passed to child flows. Why it's not the case in here? What am I missing?

 

I would appreciate some feedback and clarification :)

Practice Exam Question Clarification: HTTP Request in Flow

2 respuestas
  1. 22 dic 2024, 10:38

    Hi @Nadia Bica,

     

    If the Mule event was passed to the child flow using a flow reference, then the payload, attributes and variable (answer d) would all be accessible in the child flow. However, the HTML snippet below the illustration shows that the POST request sent to the child flow doesn't include any attributes. In addition, it doesn't show any configuration for the outbound payload, so it uses the default configuration, which is the current payload stored in the Mule event (answer c).

     

    The blog post you referenced, doesn't indicate how the attributes would be sent. The HTTP request processor acts just like a REST client. You must configure everything, with the exception of the payload, which defaults to the current payload, but you can also change that. You can send the query parameter from the parent to the child, but it's not automatic.

0/9000

I haven’t found much documentation on best practices for flow structure in Mulesoft Composer. I know in Salesforce flows, you should never perform DML inside a for loop. However I can’t figure out a way to NOT perform the update inside of the for loop in Mulesoft Composer. My goal is to get data from Snowflake and update the matching account records in Salesforce with the data from Snowflake. The MongoDB ID is the external ID in Salesforce that I am using to match to the account in Salesforce. In my test flow, I am only getting three records from both Snowflake and Salesforce but there will be hundreds of records in production. I’m trying to determine the best flow structure. Below are the two flows. What is best practice in Mulesoft Composer or is there another way that I am missing so that I am not performing a get records and update inside of a for loop?

Test Flow #1 - makes 13 API calls, has two for loops and one if/else statement.

Mulesoft Composer Flow Structure Best Practices

  1. Scheduled Flow
  2. Get all Snowflake records 
    1. For each account, gets the MongoDB ID (external ID to Salesforce) and the data that will be used to update the account record in Salesforce.
  3. Get all Salesforce account records - the filter *should return all of the same account records as what I’m getting from Snowflake.
  4. For Each Loop on Salesforce accounts - loop all Salesforce Accounts
  5. For each loop on Snowflake result set - within Salesforce Accounts loop, loop through Snowflake results
  6. If Else statement
  7. If Snowflake MongoDB ID = Salesforce Mongo DBID
  8. Update Salesforce Account with Snowflake Data

Test Flow #2 - Makes 19 API Calls but only has one for loopSCR-20241204-n2q.png

  1. Scheduled Flow
  2. Get Snowflake records
    1. For each account, gets the MongoDB ID (external ID to Salesforce) and the data that will be used to update the Salesforce account. 
  3. For each Item in Snowflake Results
  4. Get Salesforce account where MongoDB ID matches current Snowflake record
  5. Update Salesforce account with Snowflake data 
1 respuesta
  1. 4 dic 2024, 23:16

    There isn’t a clean way of updating/creating records outside a loop in Composer, but fear not, it’ll be fine. In my experience it self-regulates so it won’t hit governor limits.

    I have one Composer flow that goes into 3 loops for a single record and each of those loops has an update or create outcome. This runs once a day and processes about 200 contacts. It takes 8-10min to run, which is why I believe it self regulates.

    I’d pick the flow with the less number of API calls.

    Hope that helps!

0/9000

Hi Team,  

 

Currently working on a MS Composer integration between SF and NS. 

There are fields in NetSuite that I do not see in the MuleSoft Composer Connector. I have updated the Role settings, but the button still does not work and keeps crashing. 

Can you see on your end what the error is? 

 

The HAR file mentions an internal server error. it makes me think that this is not a permission issue.  Can you let me know what you think?  Yoann.  

 

NetSuite: Retrieving metadata for the step failed. Try saving and refreshing the page.  

Error details in screenshots attached

 

Error details: INTERNAL_SERVER_ERROR 

Trace ID: a442efc28b9efaa383fdc2a6a512b57a-83fdc2a6a512b57a-0 

Include the Trace ID in your ticket to help the support team quickly diagnose, reproduce, and solve your issue.   

 

Request URL: https://composer.mulesoft.com/citizen-xapi/api/v1/organizations/d4dad332-b10b-44f7-b133-050d85d447dd/connectors/netsuite/connections/2342fb48-1bb4-4c41-a431-4c4ddf9fd3ab/metadata?refresh=true 

Request Method: POST 

Status Code: 500 Internal Server Error 

Remote Address: 34.234.99.13:443 

Referrer Policy: strict-origin-when-cross-origin

6 respuestas
  1. 16 sept 2022, 3:32

    Hi Yoann, when I had this issue I was able to resolve it by resetting the trigger element. For example, try changing it from "Updated Record" to "New Record" and then setting it back to "Updated Record". See if you are able to refresh the fields after that. I don't know why this worked but it happened several times and this fixed it for me each time. Good luck.

0/9000