One small Salesforce (SFDC) connector feature, one giant leap for Data Source sizes

Every once in awhile, our product team releases a feature that really turns my head.  That happened this week, when the team released a simple but powerful change to our SFDC connector.  

As many of our customers that use Klipfolio with SFDC data know, we have an excellent solution that elegantly connects, and allow you to build beautiful visualizations, mash data silos, refresh in real time, and affordably put the information that matters into the hands of 100’s of stakeholders across your organization.  Much has been written on this and I won’t delve into this here.  All integrations, no matter how great, have limitations.

One such limitation is a 2000 row limit from Salesforce when fetching your SFDC Reports for use as a data source in Klipfolio.  Thankfully our Klipfolio SFDC integration also allows you to fetch data using a standard SOQL query.  

For those comfortable working with SOQL, this is powerful, flexible and does not have the 2000 record limit issue.  The catch with this method, is that SOQL fetching method returns the data in JSON format.  For those familiar with JSON, this is not an issue, but for many less technical users, JSON can be unfamiliar and intimidating.  

Therein lines the beauty of a new feature just released that now allows users to choose the Tabular (CSV) format instead of JSON.  But, that’s not even the most exciting part.

The really exciting part is that the tabular data format returned from SFDC can be 3 times smaller than the exact same data returned in JSON. It turns out that JSON is not only challenging for non-techies, it’s also a very inefficient storage format.  

So, here is the GIANT LEAP.

For those of you bumping into the Klipfolio 10MB datasource limit with SFDC data sources, you can now retrieve dramatically more data using SOQL.  

Just choose Tabular as your output format, and enjoy!!!!

For a demo of this new feature, watch this video: https://www.youtube.com/watch?v=Rbibk7lWnVk


  • 1
    Zach Kathnelson

    Agree, and love this feature.  I've been updating a number of our larger data sources.  When you change a data source to tabular, Klips using the original JSON data will need to be updated.  To make sure everything works smoothly, this is the route I've been taking: 

    1.  Find existing large SOQL data sources

    2.  Duplicate the data source.  

    3.  Reconfigure the new (copied) data source --> choose correct Token --> change Retrieval Format to tabular --> Save with a new Name

    4.  I then edit an existing Klip that was using the SOQL --> Add my new Tabular Salesforce data source in the Klip Editor --> Go through each part of the Klip and repoint the formulas to the new Tabular data source.  

    Step 4 takes a few minutes, but is really simple since I can clearly see every existing reference to the original data, and can repoint it to the same data in the new data source.  

    Keep in touch and let us know how we can help!  

  • 0
    Roger Crist

    Wow this is a great change!  Because of the row limit, I have since become an expert in SOQL queries and because of the dynamic variable nature, I don't think I can go back to tabular.  Good to know if I run into data limits that this is an option.

Please sign in to leave a comment.