Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Salesforce is one of the hot data sources for statisticians. With the size and variation of user instances, SAS JMP integration helps make sense of the data.
SAS JMP is a great tool which enables users to gain quick “Statistical Discovery” of their data and easily create visualizations. Progress has a long partnership with SAS, and we are continuously invested in improving their end-user’s experience—especially ease of use.
Of course, one of the hot data sources available for statisticians today is Salesforce. With the size and variation in users' Salesforce instances, a tool like JMP certainly helps users understand their data. This tutorial is specifically for connecting one’s Salesforce instance into SAS JMP.
The two obvious pieces that are required for this tutorial is SAS’ JMP as well as the Progress Salesforce Driver. For the purpose of this tutorial, we will be using the Windows based JMP and the Salesforce ODBC driver. Do keep in mind that it is possible to run the JMP software as we as well as the Progress drivers on different OS flavors and environments. Progress has many tutorials covering these different setups in videos which can be found here.
The download pages for trial versions of the required software:
I am also going to start with the assumption that both the Salesforce driver and SAS JMP are installed with the default settings.
The goal of this tutorial is to enable quick discovery of your Salesforce data utilizing SAS JMP. By the end of this tutorial you should be able to create wonderful data visualizations with your Salesforce data.
We will begin by setting up the Salesforce driver to your organization or sandbox instance of Salesforce. The first key piece of information we need is your security token. This is required for all applications that accesses the Salesforce API. If you do not have your security token, please follow the steps below, otherwise skip to step 5.
Now we are going to import the Salesforce data into a JMP table. We will then be able to create visualizations.
In this final section, we will create a simple chart in JMP using the Salesforce data we previously imported.
Our connectors offer real-time access to Salesforce data via ODBC, JDBC, OData or cloud. These drivers instantly connect from your existing applications to Salesforce and come with ongoing support for the latest quarterly Salesforce updates. Based on your workload, we also leverage multiple Salesforce interfaces for the best experience possible. Give it a test run for free for 15 days!
Julien Mansier is a Sales Engineer at Progress. Prior to his time as an SE, he was a developer focusing mostly on testing and fault-tolerance. Julien’s interests include OData, Mobile Development (iOS), and IoT; in fact, he can often be found tinkering with his Raspberry Pi. Julien strives to utilize his experience and technical prowess to develop high-performance applications.
Julien Tweets @JulienMansier.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.