<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Salesforce Summaries - Medium]]></title>
        <description><![CDATA[Save time with our key insights from Salesforce YouTube videos. - Medium]]></description>
        <link>https://medium.com/salesforcesummaries?source=rss----e8042433ee57---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Salesforce Summaries - Medium</title>
            <link>https://medium.com/salesforcesummaries?source=rss----e8042433ee57---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:04:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/salesforcesummaries" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Leverage Apex to Extract IoT Value from Your Data]]></title>
            <link>https://medium.com/salesforcesummaries/leverage-apex-to-extract-iot-value-from-your-data-94df38bf3054?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/94df38bf3054</guid>
            <category><![CDATA[api-gateway]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Fri, 22 Jun 2018 18:34:41 GMT</pubDate>
            <atom:updated>2018-06-22T18:34:40.564Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries.com is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p><strong>Introduction:</strong></p><p>In this presentation, you will learn more about how to leverage Apex to extract IoT value from your data.</p><p><strong>Details: ‘</strong><a href="https://www.youtube.com/watch?v=A67aNPwE5P8">Leverage Apex to Extract IoT Value from Your Data</a>’</p><p><strong>Presenter: </strong>Michelle Szucs, Tim Peng</p><p><strong>Details: </strong>20 minutes</p><p><strong>Key Terms:</strong> IoT, Gateway</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*bJ1Jk8qolcv0IBjBaSw3lw.png" /></figure><ol><li>@1.00 — The talk will focus most on how to get data from IoT devices into Salesforce. Salesforce IoT helps you get value from the data that you have already collected from IoT devices — it isn’t a platform.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*8DGDlGAp0Qd46nid6i02uw.png" /></figure><p>2. @2.10 — Salesforce takes in your data via Platform Events and from there, you can apply all the Salesforce features to your data. The 4 steps on how Salesforce IoT works is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*Ya8FXZTH7mO2m2pU-5y2CQ.png" /></figure><p>3. @3.15 — A gateway device offers many advantages for connecting IoT devices. Heroku can act as a gateway. To connect with Salesforce, authentication is mandatory. If you set up a connected app via OAuth, you have many steps to take: you need a client secret, the token, callback url etc. The reason for these steps and the emphasis on security is to ensure that the right devices are connected, that the right apps are sending the right data and that the right people are making the right actions in your org. So, it is challenging at times to connect to Salesforce because some configuration and sometimes development is required. This level of complexity is not suitable for many small IoT devices because the authentication process would become overly burdensome for them. It takes a lot of bandwidth to perform the OAuth handshake. So, what is the solution?</p><p>You can leverage a proxy gateway or an IoT device platform, such as AWS, to handle the authentication for the IoT devices for you into Salesforce. In other words, the gateway is a connector (bridge) between Salesforce and the IoT devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*Qz1Nyv2F7Iuh1BS0xM9ixg.png" /></figure><p>4. @10.15 — In this example, we will see how you can leverage Apex to convert a single gateway event into individual events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*zXbOJbfrjv4mSUwy-WBKpg.png" /></figure><p>5. @10.30 — The high level steps to take are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*Q054ZZM8kplTdNdCDSp-ZQ.png" /></figure><p>6. @10.50 — All of the events that come into Salesforce come in via <a href="https://trailhead.salesforce.com/en/modules/platform_events_basics">Platform Events</a>. Any service that produces event driven data that needs to be input into Salesforce would leverage Platform Events. An event is defined as a change in state that is meaningful in a business process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*iBO6h8F-3ADqEjTWw6FoWA.png" /></figure><p>7. @11.20 — Typically, IoT devices that will have its data feed into Salesforce via Platform Events do this by creating a JSON which is sent to an endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*FH21oDxGzdn-xJTtqNeIJw.png" /></figure><p>8. @13.00 — To create a Platform Event trigger to handle any automation that needs to happen once the IoT data has come into Salesforce, you can just select ‘new trigger’ from the Platform Event page. Platform Event triggers run in ‘after’ execution context because they fire once data has been received.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*S2ckXw9ON6qAoLGKj3IZTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*7Ni7XTBY2Mg-JcpFD0TGCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*XoZ1Dsbz0z1KW840ResG7g.png" /></figure><p>The trigger parses the JSON that is sent to Salesforce via Platform Events. <a href="http://json2apex.herokuapp.com/">JSON2Apex</a> can help to generate the Apex required to parse the JSON. More info on serializing and de-serializing Apex can be found <a href="https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_methods_system_json_overview.htm">here</a>. To see how if this works, let’s POST the JSON that the IoT devices sends via Workbench.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*Fbum1N2a6c3hARBLpDBUFA.png" /></figure><p>We can see that the trigger has fired and that this has impacted the data:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*5TM00pXm2lVHcgoP3DaJrQ.png" /></figure><p>There are so many use cases for leveraging IoT data with Salesforce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*BeHR_g6t45AYfmT_cRyjPw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94df38bf3054" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/leverage-apex-to-extract-iot-value-from-your-data-94df38bf3054">Leverage Apex to Extract IoT Value from Your Data</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Switching it Up with Apex]]></title>
            <link>https://medium.com/salesforcesummaries/switching-it-up-with-apex-4ba5c292f584?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/4ba5c292f584</guid>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Fri, 22 Jun 2018 18:27:27 GMT</pubDate>
            <atom:updated>2019-03-11T00:55:45.086Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries.com is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p>This article has moved to <a href="http://www.salesforceben.com/">SalesforceBen.com</a>. Please view this article <a href="https://www.salesforceben.com/salesforce-summary-switching-it-up-with-apex/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ba5c292f584" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/switching-it-up-with-apex-4ba5c292f584">Switching it Up with Apex</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sandbox Dataset Optimization for Salesforce Developers and Admins]]></title>
            <link>https://medium.com/salesforcesummaries/sandbox-dataset-optimization-for-salesforce-developers-and-admins-e4f3560fda2f?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/e4f3560fda2f</guid>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[sandbox]]></category>
            <category><![CDATA[metadata]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Fri, 22 Jun 2018 18:19:01 GMT</pubDate>
            <atom:updated>2018-06-22T18:19:01.466Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries.com is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p><strong>Introduction:</strong></p><p>In this presentation, you will learn more about the challenges when it comes to managing sandboxes and how the <a href="https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000007p6RYEAY">OwnBackup</a> solution from the Salesforce AppExchange can help.</p><p><strong>Details: ‘</strong><a href="https://www.youtube.com/watch?v=KXmTjfg2W9o">Sandbox Dataset Optimization for Salesforce Developers and Admins</a>’</p><p><strong>Presenter: </strong>Mat Kennedy</p><p><strong>Details: </strong>15 minutes</p><p><strong>Key Terms:</strong> Sandboxes, Development and deployment process</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/327/1*YoM7MO1vV2-V41nLN9Ll9g.png" /></figure><ol><li>@0.35 — Sandboxes are critical for developers and admins as you should test changes first. Full copy sandboxes can be expensive, and so at least, it’s good to leverage developer sandboxes.</li><li>@1.15 — OwnBackup app is one of the top rated backup providers on the Salesforce AppExchange.</li><li>@2.00 — There are a number of challenges when it comes to managing sandboxes. 52% of top companies release Salesforce changes at least once per month. To do these changes properly, you want to leverage sandboxes and run tests before the changes go into Production.</li><li>@2.45–43% of app developers spend almost 25% of their time debugging production app errors. This is hugely costly and detrimental.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*yJ9qlKLmkwBdT88TSLMS-A.png" /></figure><p>5. @3.30 — The three main benefits that leveraging sandboxes bring are that they enable you to build new features safely, enable you to test fully and also offers you a safe environment to do comprehensive testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/1*QgEdZ-5gJ_YLiZdlT_GcIw.png" /></figure><p>6. @4.20 — There are 5 main challenges when it comes to seeding a sandbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*YOz4L1cRziyAJBJnZGhyfg.png" /></figure><p>7. @4.40 — The first challenge is that it is very expensive to maintain partial or full copy sandboxes, and so it is imperative to get the most business value out of sandboxes. And so how can you ensure that you are getting the most value out of your sandboxes?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*flJsUXU7M9crqdfN0sxnKA.png" /></figure><p>8. @5.00 — The second challenge is that it is hard to test properly with incomplete data. So moving relevant data sub-sets to the relevant sandboxes can be time consuming. One of the reasons why this is so time consuming is that if you need a particular sub-set of data, you cannot specify this as an option when refreshing from production (for example, show me all accounts where the owner is based in San Francisco).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*KjL1Bqs1q7RuJHpBVuEKAA.png" /></figure><p>9. @7.30 — Another challenge is how you can mask confidential data, so that you have pure test data for an external developer/admin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*Zhb6urGq13LFCrD615uEHg.png" /></figure><p>10. @8:00 — Another challenge is that it can take a significant amount of time for your sandboxes to refresh once you initiate them to be refreshed. Also, once you move data from Production to sandbox, you don’t want that data to fire off triggers and workflows etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*d4Qvlen7TcEcLyDQDr-Zjw.png" /></figure><p>11. @9.15 — Another challenge is that cross-org comparisons are complex and time consuming. <a href="https://salesforce.stackexchange.com/questions/63067/metadata-compare-is-there-an-easier-way-than-selecting-all-components-in-eclips">Although one can do a meta-data comparison with Eclipse</a>, this is simplified greatly with OwnBackup. If a developer pushes a change set to a another sandbox, that could detrimentally impact that environment if the meta-data between the two sandboxes is not consistent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*o4C1x9r0RbwREr8HSRJc1w.png" /></figure><p>12. @10.20 — With OwnBackup, a much improved Sandbox seeding functionality is offered; which can save significant amounts of money in the mid-near term due to increased developer productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*TxHa-XLjw6Z7HCDBp9RYOg.png" /></figure><p>13. @13.00 — Everything that OwnBackup do is through the Salesforce API and because scratch orgs aren’t available through this, the tool doesn’t support scratch orgs yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/352/1*C6gljyhy0rKnF0lMjWj3xA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4f3560fda2f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/sandbox-dataset-optimization-for-salesforce-developers-and-admins-e4f3560fda2f">Sandbox Dataset Optimization for Salesforce Developers and Admins</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Einstein Bots: Build a CRM Powered Chatbot]]></title>
            <link>https://medium.com/salesforcesummaries/einstein-bots-build-a-crm-powered-chatbot-bb35b7756354?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/bb35b7756354</guid>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-einstein]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Fri, 22 Jun 2018 18:02:46 GMT</pubDate>
            <atom:updated>2019-03-11T00:54:42.422Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries.com is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p>This article has moved to <a href="http://www.salesforceben.com/">SalesforceBen.com</a>. Please view this article <a href="https://www.salesforceben.com/salesforce-summary-einstein-bots-build-a-crm-powered-chatbot/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb35b7756354" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/einstein-bots-build-a-crm-powered-chatbot-bb35b7756354">Einstein Bots: Build a CRM Powered Chatbot</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating Third-party APIs Using APEX RESTful Callouts]]></title>
            <link>https://medium.com/salesforcesummaries/integrating-third-party-apis-using-apex-restful-callouts-b681271351fe?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/b681271351fe</guid>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 10:51:17 GMT</pubDate>
            <atom:updated>2019-03-11T00:52:56.086Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p>This article has moved to <a href="http://www.salesforceben.com/">SalesforceBen.com</a>. Please view this article <a href="https://www.salesforceben.com/salesforce-summary-integrating-third-party-apis-using-apex-restful-callouts/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b681271351fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/integrating-third-party-apis-using-apex-restful-callouts-b681271351fe">Integrating Third-party APIs Using APEX RESTful Callouts</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Apex Code and the Salesforce Security Model]]></title>
            <link>https://medium.com/salesforcesummaries/your-apex-code-and-the-salesforce-security-model-67b1722671e6?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/67b1722671e6</guid>
            <category><![CDATA[apex]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Fri, 09 Mar 2018 17:30:02 GMT</pubDate>
            <atom:updated>2019-03-11T00:52:04.214Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p>This article has moved to <a href="http://www.salesforceben.com/">SalesforceBen.com</a>. Please view this article <a href="https://www.salesforceben.com/salesforce-summary-your-apex-code-and-the-salesforce-security-model/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67b1722671e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/your-apex-code-and-the-salesforce-security-model-67b1722671e6">Your Apex Code and the Salesforce Security Model</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Developer’s Guide to Heroku Connect]]></title>
            <link>https://medium.com/salesforcesummaries/a-developers-guide-to-heroku-connect-dcf5081a3a7d?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/dcf5081a3a7d</guid>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 17:49:30 GMT</pubDate>
            <atom:updated>2019-03-11T00:51:15.158Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p>This article has moved to <a href="http://www.salesforceben.com/">SalesforceBen.com</a>. Please view this article <a href="https://www.salesforceben.com/salesforce-summary-a-developers-guide-to-heroku-connect/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf5081a3a7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/a-developers-guide-to-heroku-connect-dcf5081a3a7d">A Developer’s Guide to Heroku Connect</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Serverless Applications]]></title>
            <link>https://medium.com/salesforcesummaries/introduction-to-serverless-applications-3a97e52c14db?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/3a97e52c14db</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[serverless-architecture]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 18:56:10 GMT</pubDate>
            <atom:updated>2018-03-06T18:56:09.752Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p><strong>Introduction:</strong></p><p>Serverless architecture is a new and emerging technology paradigm that is incredibly powerful and will help to democratize cloud computing.</p><p><strong>Details: ‘</strong><a href="https://www.youtube.com/watch?v=iSDokuZnRcI">Introduction to Serverless Applications</a>’</p><p><strong>Presenter: </strong><a href="https://serverless.com/">Austen Collins</a></p><p><strong>Details: </strong>65 minutes</p><p><strong>Key Terms: </strong>Serverless, micro-services, cloud computing</p><ol><li>@1.00 — The agenda of this presentation is:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*wkCR0FsxLAQfT63d84t_uA.png" /></figure><p>2. @4.30 — Getting stuff done is hard. Reducing the time it takes to get stuff done is incredibly valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*aWuz_ZABxoSXuTGVFLpDkw.png" /></figure><p>3. @6.40 — The invention of the cloud was a game changer. ‘<em>Why should you own and maintain infrastructure? Why not just rent the virtual capacity instead? Why not interact with our services programmatically via our APIs?</em>’. This was a huge innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*6h1VDlUWKckbZGH-7Ub9ug.png" /></figure><p>However, there is still a lot of scaling problems to be solved, like when Black Friday happens and millions view your site at once. Or when you have AWS bill and you’re not even using half of its features.</p><p>4. @10.50 — Serverless is a chapter in cloud history. It’s an evolution from virtual infrastructure. Serverless answers the question ‘<em>how can we offer the infrastructure without the cost and current issues</em>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*5R-BZCcQcd_869TIAk3LRg.png" /></figure><p>5. @11.00 — Today is the golden age of delivering value at a low cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*PYqzg91As6WFC0bQwH3jqA.png" /></figure><p>6. @12.00 — Heroku had the great concept of the ‘dyno’ when scaling. You can scale up as much as you require with additional cloud computing credits (dynos). But serverless is evolving that further asking ‘<em>why do you even need to scale up or down in the first place? Let’s remove that constraint. You shouldn’t have to think about scaling — you should just be able to think about solving problems</em>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*OJvHSenzkVoK8ebvx_nutw.png" /></figure><p>7. @13.00 — The big drawer of serverless is ‘pay per use’. If you put your code on ‘serverless compute’, then you only pay when your code runs. If your code runs for 1 ms, then your cost is 0.000001 cent.</p><p>8. @14.10 — The AWS Lambda started the ‘serverless’ trend in 2014.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*I0nhhNV-msfFY8OjQKXbKA.png" /></figure><p>You can write a function and upload it to AWS Lambda. The function will do just one thing, such as send a text message to a set of users, save a user login to a database etc. You can use a handful of programming languages to achieve this — Python, Go, JavaScript, Java etc. You don’t need to worry about administration because you will only be charged when the code is run and when it does run, it’ll cost fractions of a cent.</p><p>9. @16.00 — Also, the code you upload can be event driven. You can have it run automatically whenever certain infrastructure in your AWS stack happens. So half the value comes from how well it integrates with other technologies in the AWS stack and also the other half is in how efficient the code runs.</p><p>10. @17.05 — Once the success of Lambda took off, AWS started to refactor and produce a lot of other services that have serverless qualities. These are the most efficient building blocks that you can leverage to build applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*4UXhd2XUbcW-voVePpxYIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*YzIv53DSiPjHIYRMSC5h-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*DuKDV6s9Vz9rHG4FH2zVww.png" /></figure><p>11. @19.45 — These serverless services are like superpowers. You can leverage services to convert text to audio, real time processing of video, perform facial recognition etc. This is the golden age of the developer.</p><p>12. @21.00 — These are the types of serverless services which AWS customers are building.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*ix84XD2XHmKMAHtMVNC9yQ.png" /></figure><p>13. @22.15 — Chatbots are very popular. Again, you won’t be charged for your chatbots until they are being used.</p><p>14. @23.00 — Because this technology is so powerful, it attracts all types of use cases. It is liberating a lot of creativity that was previously suppressed due to overhead.</p><p>15. @23.40 — One of the most compelling stories that demonstrate the power of serverless technology can be found <a href="http://theconversation.com/root-of-census-failures-say-badly-done-ibm-and-abs-still-down-for-some-63845">here</a>. The Australian government in 2016 contracted IBM to build an online census survey that would scale. The cost for this was just over $9 million. The Australian government spent about 5x that amount on marketing urging Australians to complete the census online during a particular time period. Unfortunately, the survey was not serverless and so because the demand was so high during the certain time period, the website crashed. Relatively little data was successfully captured and a huge fallout occurred.</p><p>A few days after the calamity, two <a href="https://eftm.com/2016/08/how-two-uni-students-built-a-better-census-site-in-just-54-hours-for-500-30752">university students</a> built a replica using AWS serverless technology in less than 72 hours for less than $200 that scaled flawlessly and was able to handle even more than what the estimated demand requirement was for the census survey. In fact, they load tested the survey with 4 million page views per hour and 10,000 submissions per second. Although no data verification, audit trail or full logging functionality was implemented (<a href="https://news.ycombinator.com/item?id=12294475">which would reduce performance</a>), it does clearly demonstrates the power of serverless technology — it makes the power of the cloud accessible to everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*YEiolqY6Ck7xMOmpG1crIQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*MQIyC_RKugKwyk0OiP0s5A.png" /></figure><p>16. @28.00 — It is tricky to leverage all the different cloud technologies into a serverless application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*_XrNowRBVWWJ2ghKXwyOVA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*ov2UWi6av3aQJ0shPpE_bw.png" /></figure><p>17. @28.55 — In the AWS dashboard, you are presented with numerous products and it can be overwhelming. This is something that <a href="https://www.heroku.com/">Heroku</a> has done so well on — they answered the question ‘<em>there has got to be an easier way to do this stuff</em>’.</p><p>18. @29.30 — The <a href="https://github.com/serverless/serverless">serverless framework</a> is one of the most popular open source projects today and is an effort to make AWS more accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*C1SnM_gmS9PlAJROfMS67Q.png" /></figure><p>19. @31.00 —The serverless framework solves the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*jFRtq21T_nT5nAo9bZKG_g.png" /></figure><p>20. @32.00 — Serverless is vendor agnostic. You can use AWS or Google or Azure etc. Different vendors may have different specialities. For example, Google is very strong in machine learning.</p><p>21. @32.50 — The Serverless framework is a CLI written in node.js. The goal is to help you to deploy something as fast as possible without having to look at the AWS dashboard at any point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*mP-PNUHODRKZ38Fmm9DewA.png" /></figure><p>22. @33.10 — Serverless is a story of functions and events. It is an aggregation of plugins. This configuration file will setup a backend of your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*qHRBDrxJ_BiJmNpVYZxhtg.png" /></figure><p>23. @34.00 — Serverless comes with a number of different functions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*2KyAm3athULVme_s3Z0XkA.png" /></figure><p>24. @34.30 — The serverless framework comes with all types of languages:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*gJIG0Ct6uLyDo_DTAQuq9w.png" /></figure><p>25. @35.00 — There are hundreds of serverless plugins that have been created courtesy of the fantastic open source community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*t8ngNT7Av453hf3S24siEw.png" /></figure><p>26. @58.00 — There is a huge demand for moving to serverless architecture. Companies like Nike and Coca-Cola already have adopted serverless architecture.</p><p>27. @61.00 — This architecture is micro-service architecture. ‘<em>Let’s try to separate every single piece of logic in our application so that there will be no risk to the system overall if a swathe of changes are made</em>’.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a97e52c14db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/introduction-to-serverless-applications-3a97e52c14db">Introduction to Serverless Applications</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplify Lightning Component Development with Lightning Data Service]]></title>
            <link>https://medium.com/salesforcesummaries/simplify-lightning-component-development-with-lightning-data-service-a89c0c4c649e?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/a89c0c4c649e</guid>
            <category><![CDATA[salesforce-lightning]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 12:54:18 GMT</pubDate>
            <atom:updated>2018-02-28T12:54:18.244Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p><strong>Introduction:</strong></p><p>Lightning is a new development paradigm for Salesforce that depends heavily on JavaScript. Since its release, the benefits of adopting Lightning and building bespoke, mobile friendly Lightning components have been made clear. However, one downside was that a lot of duplicitous JavaScript and Apex code was required for fairly simple Lightning components because there was no Lightning equivalent of the <a href="https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/apex_pages_standardcontroller.htm">standardController</a>.</p><p>However, <a href="https://trailhead.salesforce.com/en/modules/lightning_data_service">Lighting Data Service</a> solves that problem as it is in effect, the Lighting version of the standard controller. There is no need to write Apex, SOQL statements or JavaScript methods to update records now.</p><p><strong>Details: ‘</strong><a href="https://www.youtube.com/watch?v=nHYnt0t0_NI">Simplify Lightning Component Development with Lightning Data Service</a>’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*4AbAQ8cjBI1r6LAhqqcVHw.png" /></figure><p><strong>Presenter: </strong>Marcus Torres and Carolyn Grabhill</p><p><strong>Details: </strong>33 minutes</p><p><strong>Key Terms: </strong>Lightning Data Service, force:recordData</p><ol><li>@1.50 — There are many considerations for custom Lightning components. And there are many considerations that are related to data, such as SOQL, field level security and record updates etc. However, you don’t need to consider those when using the Lightning Data Service.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*JRFozaRl7SzBkXCFSRc1PA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*oG2ub1zXWwHg_eJ8jISS7Q.png" /></figure><p>2. @3.05 — Every single component keeps a copy of its own record data. The components essentially ask the Salesforce server via the client side controller for some data, which is actioned by SOQL in the server side controller. So there are many steps involved to get the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*CUwhH7cr3iEiszbTHLMgvg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*VMn2ePoOcB34Vuzu2YQ1XQ.png" /></figure><p>3. @4.20 — The Lightning Data Service is effectively the standard controller for Lightning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*lsL6ChfmzjxPZhi833CHeg.png" /></figure><p>So instead of n number of Lightning components all keeping their own copy of the data, they all essentially have a pointer to a shared instance, so it’s effectively a shared cache.</p><p>4. @5.25 — Because it’s a pointer, auto-notifications on record changes are possible. Also, offline access for Salesforce1 is possible with the Lightning Data Service (LDS). In fact, offline access for Salesforce1 is powered by LDS.</p><p>5. @6.00 — The data flow looks like this, with LDS:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*RvHczvZcU5hzhcxtXSyEZQ.png" /></figure><p>Your Lightning components will use &lt;force:recorddata&gt; to leverage LDS. LDS connects back and forth with Salesforce.</p><p>6. @6.40 — The status of <a href="https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/data_service.htm">LDS</a> as of the time of the presentation (July, 2017) was:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*qXuiHsYco9iO5dgy-BDnRA.png" /></figure><p>7. @7.30 — &lt;force:recorddata&gt; is the flagship component of LDS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*J5HcX-xf2hR--XWE5-Fphg.png" /></figure><p>8. @7.50 — You will need to give the recorddata component an aura id, so that it can be referenced in JavaScript.</p><p>You will also need to pass in the recordId, and the fields that you want to load. This approach is fine but if you like, you can pass in a <a href="https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/data_service_load_record.htm">layoutType</a> instead of passing in hard-coded field values. layoutType = FULL] is all the fields defined on the page layout editor and compact is all the fields in the highlights panel at the top of pages in LEX (Lightning Experience). Or you can pass in both, and you would get the super set.</p><p>targetFields should be used if you want just the field API names whereas targetRecord is a JSON response with API names, field values, record type Ids etc. If you are using a lot of JavaScript logic, then you’ll want to use targetRecord.</p><p>targetError is where any error response will be loaded, which can then be referenced in your Lightning page.</p><p>Lastly, you need to give a mode. This will be ‘VIEW’ or ‘EDIT’. This controls whether LDS can automatically re-render data for you.</p><p>9. @11.25 — In the demo coming up now, there are three different Lightning components which leverage LDS to show you the power of this functionality. None of them use Apex controllers.</p><p>10. @11.50 — In this component, the Account Temperature icon is being pulled from the ‘Rating’ field on the record. This using LDS and has no Apex or JavaScript controller or JavaScript handlers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*-Cxf8EbopwMp4Ju8zKsLlA.png" /></figure><p>11. @12.05 — If the ‘Rating’ changes from ‘Hot’ to ‘Cold’, then the icon updates automatically:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*F86Mb5ModY-PRyNyLH16xw.png" /></figure><p>12. @12.30 — This component references the force:hasRecordId interface:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*TeNUNk99I724obsb-YB0Yw.png" /></figure><p>This interface will give the component the record Id attribute of the record being viewed. That record Id attribute can be passed to the &lt;force:recorddata&gt; component. This way, no SOQL is required to get the Id of the record being viewed.</p><p>Since the mode of this component is ‘VIEW’, if any change to the record is mine whilst we are viewing it, then LDS will auto-render it again.</p><p>13. @13.55 — Dynamic styling is being automatically applied to show different icons depending on the value of the ‘Rating’ field. Line 19 says ‘if the record rating is ‘Hot’, then use the ‘icon-hot’ CSS styling else if the record rating is ‘Warm’, then use the ‘icon-warm’ CSS class. No additional JavaScript is required for this — it’s all Lightning expressions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*-5S4ml4qTEIN2FkFntb09A.png" /></figure><p>14. @15.00 — The use case in this example is that a custom object has been built which contains some fields of different data types. The salesperson is on the phone to the potential customer and is negotiating on the price and the discount. If the salesperson inputs some data into the ‘Discount Scratchpad’ component, then the commission that the salesperson would receive is displayed automatically with no re-rendering of the page (because the calculation is completed on the client).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*QH-vzKHlyE2onAZv8tuBCw.png" /></figure><p>15. @16.00 — In the below screenshot, you can see that the ‘Compute Discount’ button has been selected and so the commission value has been displayed ($1,400 commission from a $30,000 sale).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*j4UzY-DSJCXuJ2joIbckcw.png" /></figure><p>16. @16.10 — The code is below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*7mzDInplaHPuLtrYsqg0ag.png" /></figure><p>As per line 1, for all components that implement LDS, it implements force:hasRecordId. This is used to get the recordId of the currently viewed record (as per line 7) because you want to pre-populate the component with some of those values. As per line 6, the aura:id has to be defined because this component will need to be referenced in JavaScript this time because the record will be saved and saving has to happen with JavaScript.</p><p>As per line 8, the layoutType is ‘FULL’ to get all the fields and the mode type (line 9) is ‘EDIT’. Because the mode type is ‘EDIT’, if something changes on the component, then this won’t result in automatic re-rendering of the component that was the case in the previous component (the icon display cmp). However, you may still want to take some action when data changes. This can be handled using an event. As per line 10, when the record has been updated, run the {!c.resetDiscountForm} function. This is a client side controller (as per the ‘c’). Lastly, as per line 11, once the record has been loaded, it’ll be pushed into the targetFields attribute.</p><p>Official documentation on the force:recordData component can be found <a href="https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/aura_compref_force_recordData.htm">here</a>.</p><p>17. @27.40 — The roadmap is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*aJ3JNZ8CjuyiPtPwcF1vHA.png" /></figure><p>Bulk support will allow you to provide a list view Id and LDS will be able to fetch all the data from that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a89c0c4c649e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/simplify-lightning-component-development-with-lightning-data-service-a89c0c4c649e">Simplify Lightning Component Development with Lightning Data Service</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring the Salesforce REST API]]></title>
            <link>https://medium.com/salesforcesummaries/exploring-the-salesforce-rest-api-e649f010d23e?source=rss----e8042433ee57---4</link>
            <guid isPermaLink="false">https://medium.com/p/e649f010d23e</guid>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Andy Hitchings]]></dc:creator>
            <pubDate>Mon, 19 Feb 2018 18:02:07 GMT</pubDate>
            <atom:updated>2018-02-19T18:02:06.715Z</atom:updated>
            <content:encoded><![CDATA[<p><em>SalesforceSummaries is a publication that delivers the </em><strong><em>key</em></strong><em> insights from Salesforce YouTube videos. We aim to be the </em><a href="https://www.getabstract.com/en/"><em>getAbstract.com</em></a><em> of Salesforce tutorial videos. These publications will save you time as you keep up to date with the latest technological changes within the Salesforce ecosystem.</em></p><p><strong>Introduction:</strong></p><p>The Salesforce REST API is the most common way to integrate with third party services. This presentation discusses the Salesforce REST API and the different approaches to create more efficient REST API requests; which are especially helpful for mobile users.</p><p><strong>Details: ‘</strong><a href="https://www.youtube.com/watch?v=R6eVlc3Dwco">Exploring the Salesforce REST API</a>’</p><p><strong>Presenter</strong>: Jay Hurst</p><p><strong>Time: </strong>48 minutes</p><p><strong>Key Terms: </strong>Salesforce REST API, Composite API, Batching REST Resource</p><ol><li>@1.45 — Salesforce have done a lot of work to improve the Salesforce REST API to make it more efficient and less cumbersome to work with.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*lxs4peS_mqX2BCGiKyMzAA.png" /></figure><p>2. @2.40 — The integration layer (on the right) is the API. The Salesforce system has been built to be API first. The integration layer is the programmatic entry point if you are coming into the Salesforce system from outside of Salesforce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*H3Ur0GEyqOQS4qzNEfpPpQ.png" /></figure><p>3. @5.30 — About 9 years ago, Salesforce came out with the Salesforce REST API (api version 22.0). The Salesforce SOAP API was created before the Salesforce REST API. What Salesforce wanted was to take the existing functionality of the SOAP API which is proven to work very well and expose REST endpoints of top of it. So anytime you call the Salesforce SOAP or REST API to create an Account record, for example, you’re actually calling the same API inside of the Salesforce Java layer. So Salesforce are building just one API layer but with two different entry points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*kDOCarAMMM_BAeAfQg3AeA.png" /></figure><p>4. @6.20 — The Salesforce REST API is synchronous but there are RESTful Salesforce APIs which process asynchronously (for example, the BULK API). The <a href="https://developer.salesforce.com/page/Creating_REST_APIs_using_Apex_REST">Salesforce REST API</a> is best suited for browser or mobile apps which don’t need access to high amounts of records.</p><p>The Salesforce REST API supports both XML and JSON.</p><p>5. @11.40 — The anatomy of a REST API call is as per below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*aqoBXUi573Sr4yL3Y0gixw.png" /></figure><p><strong>/services/data</strong> is the Salesforce REST API. If you’re using /services/async, then that is the BULK API and /services/SOAP is the SOAP API.</p><p>Every time Salesforce do a new release (3 a year), then the API version will increase incrementally. If new functionality comes out in a particular Salesforce release, then that is tied to that version, and not to previous versions. But all your existing code that is running on an older version will keep running (backwards compatible). Salesforce traditionally do not retire API versions. It’s recommended to keep your API versions up to later API versions (try not be less than 6 API versions old).</p><p>6. @11.50 — With the REST API, from a single request you get a single response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*DigS3b1DV2pq9klRdCcZxA.png" /></figure><p>In this diagram, the user is doing a CREATE, DESCRIBE and a LIMITS call. The user sends the CREATE request, which goes to the Salesforce REST endpoint, which then returns a response from the Salesforce database back to the client. The user can then make a DESCRIBE call and then a LIMITs call. This is the traditional pattern with REST — you have a resource, you make the call, you get a response and then you do something with that response.</p><p>Salesforce are asking ‘<em>how can we make this REST process more efficient?</em>’.</p><p>7. @12.35 — A composite API is an API that is built by combing existing API functions. So instead of having 3 distinct calls (as per the above diagram which showed the CREATE, DESCRIBE and LIMITS call), perhaps that can be boiled down to two or even one call, and have the server run the logic that goes behind those calls. So instead of incurring the cost of going from client to server multiple times, you can have just one round trip from the client to server but have the server can do multiple processing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*jPY_Oy_8OCrxexCXYs8auQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*rDqWZmha6iNNTuECDQuK6Q.png" /></figure><p>If you wanted to create a contact, you would first need to have an account to be associated with that contact. And so you would need two calls: one to create the account, return the account.id, and then create the contact record against the account.id. This isn’t as efficient as it could be because ideally, a developer would use responses from one API method as inputs into another method. In this way, multiple APIs can be used in a single call to improve performance.</p><p><a href="https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm">Compositions</a> are increasingly important for designing efficient API for use in mobile development. Calls which push less data = more efficient.</p><p>8. @14.15 — One of the composite resources available is the <a href="https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_batch.htm">batching REST resource</a>. You can batch up to 25 request calls into a single JSON call which the Salesforce server processes serially. Salesforce will return a serialized response. This can reduce round trips. The request in a batch are called subrequests, and are all executed in the context of the same user. Subrequests are independent, and so you cannot pass information between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*nvlKidypuR3dmLIPGeo4Vw.png" /></figure><p>9. @15.20 — With the <a href="https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobject_tree.htm">TreeSave</a> REST resource, you can insert multiple records in a single call. For example, create one account, and then 3 contacts against that account.</p><p>10. @15.40 — You have the ability to define whatever you want and expose it as a REST endpoint. So you can build a composite for example to build multiple things, but it will be easier to leverage the already existing Salesforce composite resources.</p><p>11. @16.20 — The Batch REST resource is not suitable if you want to do transactional manipulation because it’s not an ‘all or nothing’ approach. Instead, if a sub request fails, it will move onto the next sub request and all successful sub requests before that do not get reverted.</p><p>There is an optional parameter — haltOnError — which would prevent the other serial calls from being executed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*M2FxDAtEA1p_JQC4crVU8g.png" /></figure><p>12. @17.50 — In the below example, if one wanted to create 2 accounts, 3 contacts, 2 cases and 2 tasks via the REST API, this would take 9 different API calls. This is what that would look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*WL76P20F9yA4HSR-rzUgnA.png" /></figure><p>However, using the batch REST API, one can bundle the requests into a single .json file (body) and then send that body to a single API call.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*f6HK7BeIsLIHurXXHBoa-Q.png" /></figure><p>The Salesforce server will process each of the sub requests serially and then pass the results back into .json format.</p><p>13. @18.00 — This is what an example batch request looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*8IPaYutuw6QRSIidi139pA.png" /></figure><p>14. @19.00 — <a href="https://workbench.developerforce.com/">Workbench</a> continues to be one of the most popular ways to explore the Salesforce REST API. If you navigate to the Rest Explorer in Workbench and make a GET request to /services/data/vXX.X (for example, v41.0) then you will return a list of all the API types that are available to you.</p><p>You will notice that different functionalities are only available in later API versions. For example, if you compare API version 41.0 (current, as of Spring ’18) against the earliest REST API version (22.0), you can see how the Salesforce REST offering has grown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*EASQ0hBDZlY5v_5pN8uBEQ.png" /></figure><p>You can click into one of the API types, and then you’ll see a sub-tree list of the different options to you. For example, if you click on the limits API type, you’ll be navigated to a page which looks like this. This page details all the limits to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*YWDONuj5hD59v3Riplo8Ew.png" /></figure><p>15. @20.00 — To do a batch request, input /services/data/v37.0/<strong>composite</strong>/batch, select ‘POST’ and input a request body like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*zXeyBK-qt2Z1lY9GubFG_A.png" /></figure><p>As per the request body, this is in JSON format and three independent calls are written. You’ll notice that you don’t need to bind to the same API version that the callout is coming from.</p><p>The first call is a POST (create) on the Account sObject. Two fields are being populated: Name and Industry. The second call is getting all the metadata from the Account sObject. The final call is a GET to the query resource and running a query for all accounts that are ordered by the createddate.</p><p>16. @22.10 — Upon executing this, the results are returned. You can select ‘Show Raw Response’, which returns the response in JSON, or you can use the sub-tree file structure instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*YX6xBzKaKsZzdUWJvAheSw.png" /></figure><p>17. @22.50 — You can see for the response from the third call that it was a success (200 Http response) and you can see the list of accounts that were selected in the query. You’ll notice that ‘NewName’ account has been pulled into the response as it was created at the time the query was run (as the account was created in the first call and the query was in the third call).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*BiAVqPCTrR7Xp-sC-wvXzg.png" /></figure><p>If you input an incorrect syntax for one of the API calls in the request body, you’ll note that the response will have errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*SVjQKPk3SBy3gCzR5P9Kcw.png" /></figure><p>18. @24.40 — The way the Salesforce REST API is designed at this moment is that it can only take a single URI per request and so you cannot pass in an array into the URI.</p><p>19. @24.45 — The TreeSave resource is a recursive data structure. A single request can contain up to 200 records across all trees. For example, you could create 1 account record and 199 contacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*j-Ofb2qJHf7gEAQDWM0abw.png" /></figure><p>20. @26.00 — The TreeSave API diagram looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*EsyIqD8MRxAcvSddLSAZqg.png" /></figure><p>To POST contacts under the account, the URI would be /services/data/v37.0/composite/tree/<strong>Account</strong></p><p>21. @26.30 — At this moment, only the INSERT DML operation is supported for TreeSave. Partial saves are not supported. The transaction is not completed until it is 100% successful. Everything will be rolled back if there was an error.</p><p>Separate governor limits are applied to each level of the tree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*u25_lIlmrqSCY7pKvxIPpA.png" /></figure><p>22. @32.00 — In this example, an array of accounts are being inserted and some contacts (children).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*bUngnPmyshGCY95ykA8mDg.png" /></figure><p>The top of each level has an attribute tag, which references the sObject type and reference Id. Afterwards, the field name — values are specified.</p><p>23. @34.00 — The response looks like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*1hcA-MgNaZSNYj-jEakNvg.png" /></figure><p>The top level sObject would return first in the response, but the processing of child records isn’t deterministic and you can’t write any logic to say ‘this child sObject should be created first’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*7rXhkUbPpJGiRMJKGtKNYQ.png" /></figure><p>24. @38.40 –</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*Uf4uP1sd3-21TlWDWljouQ.png" /></figure><p>@41.00 –</p><p>With a <a href="https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_composite.htm">Composite API,</a> you can take the benefits of the batch request and the TreeSave together. This results in web structure (not a Tree structure), in that you can do different REST API methods on related or unrelated data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*oat8JW0Bpbwu2i9dzhs0yw.png" /></figure><p>@42.15 — An example of a composite API request is below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*eue-H2qnrBQAWe1RqFz0xA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e649f010d23e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforcesummaries/exploring-the-salesforce-rest-api-e649f010d23e">Exploring the Salesforce REST API</a> was originally published in <a href="https://medium.com/salesforcesummaries">Salesforce Summaries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>