One of main use cases with Salesforce that MuleSoft customers use involves uploading records that are stored in CSV format to Salesforce. MuleSoft has provided various ways to fulfill this use case. We have dataloader.io, the most popular Data Loader for Salesforce on Salesforce AppExchange, and also have Anypoint Platform’s Salesforce Connector with various operations.
We added another option to help you easily accomplish the above use case.
Today, I’m pleased to share that MuleSoft has entered into an agreement to be acquired by Salesforce. This is a major milestone for the company and potentially one of the most game-changing technology acquisitions in history. I believe it will accelerate us on our mission to enable organizations across the world to change the clockspeed of business with application networks. I could not be more excited about this next chapter for MuleSoft.
We are introducing new features and lots of improvements in Mule 4. In support of Mule 4, we are also focusing on improving user experience of the Salesforce Connector, one of the most popular SaaS applications. In this blog post, I will showcase a demo that provides insight into the new capabilities in the Salesforce Connector.
At Dreamforce ‘17 this week, we are repeatedly hearing about the importance of improving the customer experience. Customers today expect more and demand more, wanting a consistent buying journey across all channels. This idea of “unified commerce” requires more than thinking about your strategy for each distinct channel; but, rather meeting customer expectations across their entire experience ––from shopping and personalization to fulfillment and customer service.
So far in this 3-part series, we have looked at variables (Part 1) and functions (Part 2) in order to leverage them to our advantage. In this third and final part of the real-world DataWeave series, we will look at another common problem area, that of performing nested loops in data structures.
In the first part of this series we tackled the issue of defining and also using variables within DataWeave as opposed to using the legacy set “Variable” module. Today, I need to raise the topic of functions in DataWeave as a key thought when working with MuleSoft has to be “can I reuse this?”
We are back at Dreamforce ‘17 for yet another great year. This year’s exciting agenda will cover APIs and microservices––from using MuleSoft to maximize ROI from force.com to learning how to create, deploy, and manage Microservices. Attend our sessions to learn more about these topics, drop by booth 441 to talk to MuleSoft experts about connectivity, and participate in fantastic giveaways!
Over the last few years at MuleSoft, I have had the opportunity to work with many different customers covering a wide range of use cases, inevitably requiring data transformations of one sort or another. I have observed some recurring patterns and “gotchas” when DataWeave is used in the real-world and I will address these in this 3-part series.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.