![]() The Query tab lets you input SOQL code to perform In database Selects, performed directly on SFDC’s cloud platform. The next tab is the most exciting, yet the least explicit: Ensure that you are extracting only the fields relevant to your analysis, for performance. This is where you specify target tables, which fields will be extracted and rename them if need be: Note that I have seen some tables missing from the pick list, just type their name directly and it will work. Once the credentials are input, the Table tab comes alive. The reason those Remote Access keys are required is that they can be used for the SFDC Input connector as well, which can be used to write data to SFDC from Alteryx Remote Access Consumer Keys and Secret are obtained by your SFDC admin after he configures the API connection:.Security token is obtained by going to your top right name > My Settings > Personal > Reset My Security Token.The current version of the SFDC connector, as of Alteryx V9.5, Looks like this: No wonder Tableau, the company, is not using that connector to process their own SFDC data, as explained in this great description of their internal dog food approach… In my case, I use Alteryx to gain the agility needed for deeper analysis. There is no in database selection, all the records need to be extracted first, hence the long processing time with the extracts.to blend SFDC with a different data source, such as sales targets, you need a separate data source and the blend has to be done using queries in Tableau, a major pain….On the flip side, a major shortcoming for this solution: the data is not “live” and the performance to create the extract is not that great…Īmong other shortcomings of the solution: Once the initial extract is created, incremental refresh is available, a blessing for large data sets. ![]() Clicking on Sheet will launch the mandatory creation of an extract database:.It is possible to customize the joint with a few drag and drops, Tableau will automatically suggest joints based on SFDC’s DB schema. In this example, the customized SFDC instance includes contacts in the Lead table. You are offered a series of “Standard Connections”, a set of connected tables meant to cover the most frequent use cases as predefined by Tableau for standard configs of SFDC (Leads analysis in this case):Īnd below is a list of existing Tables in your instance of SFDC, including custom tables, to let you prepare custom extracts:.If your password is mypassword, and your security token is XXXXXXXXXX, then you must enter mypasswordXXXXXXXXXX to log in. That security token can be collected promptly in SFDC by going to your top right name > My Settings > Personal > Reset My Security Token. Use your SFDC login and password, appended with your security token.Tableau offers a native connector out of the box, and even pre-built dashboard templates for SFDC, the only data source a template is available for, as far as I know… Returning to Tableu though, with both options, which one should be used? I will offer my perspective, as each is attractive in the right context:įor a quick overview, standard report or on the fly analysis, Tableau Connector works great. In fact, this functionality is often used between other applications, such as a Salesforce ActiveCampaign connection option that can help fully populate user data with what each side of the system has. This leadership offers convenience when it comes to handling data from many cloud database platforms, as both Tableau and Alteryx provide standard connectors to extract transactions. For convenience, I will systematically refer to as SFDC.Īs the largest CRM vendor according to Gartner, SFDC is pretty ubiquitous, and the odds are that most Tableau users dealing with sales figures have already run into this data source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |