<?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[Stories by Matt Pieper on Medium]]></title>
        <description><![CDATA[Stories by Matt Pieper on Medium]]></description>
        <link>https://medium.com/@piepermatt?source=rss-13ed0c581724------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*s5rFjpco56Jxw9oV</url>
            <title>Stories by Matt Pieper on Medium</title>
            <link>https://medium.com/@piepermatt?source=rss-13ed0c581724------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:44:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@piepermatt/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Make Software Purchasing Painless — Matt Pieper]]></title>
            <link>https://medium.com/@piepermatt/make-software-purchasing-painless-matt-pieper-a384ec884d21?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/a384ec884d21</guid>
            <category><![CDATA[vendor-management]]></category>
            <category><![CDATA[business-systems]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[purchasing]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Wed, 22 Feb 2023 10:00:23 GMT</pubDate>
            <atom:updated>2023-02-22T15:50:50.636Z</atom:updated>
            <content:encoded><![CDATA[<h3>Make Software Purchasing Painless</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SiiWBsx09EmXw-ZS.jpg" /></figure><p>I want to make software purchasing painless for anyone reading this post. When I first broke into Business Systems, I had to pick up various non-technical skills.</p><p>One of the top three was vendor management and procurement. I had yet to learn what I was doing and made every mistake in the book. It was excruciating.</p><p>Of the many things I love about my role is the ability to support every department. This means learning how they operate and what specialty software they use to get stuff done.</p><p>This has led me to sit in on countless sales cycles across multiple industries and verticals. I learned the rhythm of how these calls go and what I should be sharing but also listening for.</p><p>Combining these experiences with supporting sales organizations, you get to sit in a particular seat to understand what is happening in this weird dance called sales.</p><p>Often, buyers think it’s a complicated process. True, there are mechanisms in place to create asymmetry. But, I want to share with you how to make SaaS purchasing painless, and that first starts with knowing the process.</p><h3>The Sales Process</h3><p>There are tons of resources out there that go into deep detail about the sales process and what it is. <a href="https://www.gartner.com/en/articles/the-saas-buying-experience-mapping-how-businesses-buy-software">Gartner</a> provides overall guidance — I don’t buy into the Gartner Magic Quadrant, but they have other good content. <a href="https://zapier.com/blog/business-software-purchase-decisions/">Zapier</a> goes into great detail about the process.</p><p>But, for our purposes, I will distill it down and potentially use non-standard terminology. So, sales folks, yes, some liberty has been taken for readability.</p><p>Why? Because in order to make things painless, we need to know what to expect.</p><h3>Prospecting</h3><p>If you’ve ever received a quirky LinkedIn message, email, or even the dreaded cold call, you’re officially a prospect. Someone thinks you are in the market for what they want to sell. Congratulations!</p><p>How did they get this idea? From lists they bought, data they’ve collected to build a profile, and a bunch of other magic that may appear on this blog someday.</p><h3>Qualification</h3><p>This is where you talk to a Sales Development Representative (SDR) or equivalent.</p><p>Regardless if it’s a cold call or they’re responding to a lead form you’ve filled out, they are confirming information about you.</p><p>In addition to this confirmation, they determine if you are a fit for their product or service. They’ll ask you about your use case, the size of your company, and any other platforms you may have.</p><p>These determine what the next steps are.</p><h3>Discovery</h3><p>This call may be combined into the pitch meeting. But this is where you meet your Account Executive, who will guide you through the rest of the process.</p><p>They’re building onto the qualification meeting and asking more probative questions. Here they may share bits and pieces of the product to gauge your interest.</p><p>They’ll also ask four usual questions: do you have a budget? What is the buying process, and where are you in the process. Are you looking at competitors?</p><p>The discovery phase is to determine how large a lift the sales process will be and to understand how to craft a tailor-made demo for you.</p><h3>Pitch</h3><p>This is the core of the process. Here is where they share the product with you and the value their company brings.</p><p>You may see a sales manager on this call to lend extra support. Different faces may include an implementation manager or sales engineer.</p><p>The meeting cadence usually includes a few slides on the background of the product or company, a demo, questions, and the next steps.</p><p>Bring everyone who you think is vital to attend. They can ask questions here, and they <em>should</em>. It would be best if you also prepared them beforehand for the meeting on what to listen for and why you’re looking to purchase.</p><h3>Commercials/Pricing</h3><p>Where you’re presented with how much it’s going to cost you.</p><p>Honestly, this is the most adrenaline-pumping part of the process. But, hold on, you don’t get to pricing first.</p><p>You will be sold on the product again for a few slides and then get the pricing. Then you’ll discuss your feelings about the pricing and the next steps.</p><h3>Contract Execution</h3><p>The fun part. DocuSign or something similar (always different to keep your boss on their toes) is sent and signed.</p><p>Yay! You bought something.</p><p>Enough said.</p><h3>How To Make Purchasing Painless</h3><p>How do you make the purchasing process painless? I have some good news and bad news.</p><p>The biggest thing you can do requires no additional work. It just means knowing this is a cooperative process.</p><p>The bad news is that you will have to do some work ahead of time to ensure everything runs smoothly.</p><h3>Don’t Be A Jerk</h3><p>These tips aren’t in any particular order, with the exception of this one.</p><p>Just be nice. The sales process is really a win-win for everyone when done correctly. It’s okay to be cordial.</p><p>Understand there are rhythms to meetings. It involves some small talk before business. It may mean repeated concepts or multiple meetings.</p><p>You don’t have to be a shrewd negotiator or start questioning everything from the beginning.</p><p>There’s a process for a reason. It makes everything have a rhythm.</p><p>When you are cordial, it reduces pressure and increases the likelihood the seller will work with you on pricing.</p><p>Remember your relationship with the company exists post-sale. You want to avoid being flagged in their CRM as a demanding or difficult customer.</p><p>Also, you may work with your AE again to buy additional SKUs or upgrade. They’ll remember.</p><p>Further, they can assist you in raising any support requests.</p><h3>Know What You Are Wanting To Buy</h3><p>This seems common sense. But you’d be surprised at how many folks make their discovery during the sales demo.</p><p>They leverage the salesperson to tell them what they should be looking for and what they need. This is a seller’s favorite. They can craft a narrative. If the seller is good enough and the first, they’ve set a benchmark you can’t move from.</p><p>You’ll hear me scream requirements in order to understand what you want to buy, but this doesn’t mean a complicated process with many spreadsheets.</p><p>Know what problem you’re looking to solve.</p><p>What is the problem, and why will software fix it. What features are around that you need?</p><p>What is a deal breaker, a nice to have, and a that would be cool if? Please stick to your deal breakers. There’s a reason that they are that.</p><p>Also, do a bit of research in the space before you start talking to vendors. Know the competitors, and understand what the landscape looks like.</p><p>When you come to the table with knowledge about the landscape and product, you can ask deeper questions.</p><h3>Know Your Procurement Process</h3><p>Getting to the dotted line and being blocked by other departments will frustrate you.</p><p>So, before taking a spin around the block with vendors, do a little internal discovery. Figure out who is on your procurement team and what the process is.</p><p>Typically this team comprises Finance, IT, Legal, Security, and sometimes a project management office. They are your partners and can make the process painless.</p><p>They will have guidance for things they are looking for if the product is on a restricted list or maybe your organization has a product in place already.</p><p>This is a good time to determine if you need to submit formal requests, budget addendums, or what documents you need during the process. They will also give you an idea of how long the process takes.</p><p>I recommend engaging early, before any meetings with vendors. This will keep the process flexible, and you don’t have to worry about delays later.</p><p>This also helps you with the vendor. Let them know at the beginning if there will be heavy redlines or if they need security documents that need extra work, or if your procurement process takes a long time.</p><h3>Know How Much You Can Afford</h3><p>Nothing is worse than getting to the end of the process and then negotiating internally.</p><p>It’s frustrating for everyone.</p><p>Your email is blowing up from the rep following up, and you want an excellent product that will solve all your problems.</p><p>This is why knowing your procurement process is essential.</p><p>Knowing what you can afford is vital to the entire process. There isn’t much point in investing time into demos and research if there won’t be a budget for the product.</p><p>Before engaging finance (or your leadership), it would be best to do some competitive research to determine what the price may be first.</p><p>This does two things: it lets you prepare for what the price may be and gets a baseline for your finance team ahead of time.</p><p>How do you do this?</p><p>Surf their site for pricing, try to find clients, look at postings on forums, or hint around it with an SDR or AE. Also, ask internally, someone may have purchased the product at a prior company.</p><p>The more you know ahead of time helps you level set. But keep in mind that pricing on a website may be the max price. There may be negotiation room.</p><h3>It’s okay to negotiate.</h3><p>Don’t accept the first offer. It’s like paying sticker on the car lot.</p><p>Companies will never want to make the lowest amount that’s possible.</p><p>Most often, this is the best guess based on your company size, past deals they’ve had that look like you, and a bit of intel about your budget.</p><p>If it seems wildly out of line with what you’re expecting, take the time to discuss it with your team. Let the seller know that “it’s a bit higher than I thought, and we’ll need to debrief internally.”</p><p>Chat with your team, figure out what your counter is, and pitch it back. This is where you see your sales rep work between their management and operations teams.</p><p>Don’t be unrealistic here. Use your best judgment based on your research and use that as a benchmark. Don’t want this pressure? Consider a company like <a href="https://www.vendr.com/">Vendr</a> to provide all of these details for you.</p><p>Don’t be a jerk and try to renegotiate if they meet you at your number. Yes, you probably had more room to go down, but it’s called good faith.</p><p>Having someone else to defer to on this is excellent. Usually, the CFO or other executive will advise if they think the price is reasonable and can inform budget.</p><p>Sales teams are incentive driven and have pressure to meet quotas.</p><p>This is where being flexible comes into play. You’ll see better discounts if you have time to buy at the end of a month, quarter, or fiscal year.</p><p>If you’re briefing your procurement team ahead of time and can move quickly, you can get a discount for closing fast. You may get pressure to commit to a date, but know the seller wants this deal. You can usually extend this date.</p><p>Multiyear sales will also garner discounts. A caution here, as you will want to have the ability to negotiate an opt-out after the first year or truly know this is the platform for you. Nothing is worse than picking a bad product and still paying for it.</p><p>You should have set a baseline price discovered on competitive research before. This is what you’re willing to accept. Don’t go above this. Knowing what you’re ready to accept will make life easier. It also sets your benchmark ahead of time.</p><p><strong>A caveat:</strong> If a company tells you they don’t negotiate, trust, and then verify it. Companies like Slack will sell you the price on the website, no different. Differences here are if you’re in the nonprofit or government sectors.</p><h3>It’s okay to share</h3><p>You don’t have to keep all the information to yourself. Please share it with the vendor.</p><p>Are you working with competitors, or are you switching from one? Do you have this approved in your budget?</p><p>Let them know if you’re stuck internally or have to punt a project. This rapport builds over time.</p><p>You never know if your sales contact goes to another company; they’ll remember how it was working with you.</p><p>I’ve worked with some of the same sellers at multiple companies and sometimes bought different products from them. Your network really does help.</p><h3>Make Software Purchasing Painless Conclusion</h3><p>There is a ton more that I can share with you on the process of procuring software, but I hope this is a good primer on how to make it easier.</p><p>The more you engage in these discussions, the easier they are. But you’re also not alone in the process.</p><p>There are communities out there to support you in your journey, and there are probably great resources internally at your organization as well.</p><p>The best advice I have is: we’re all people at the end of the day. Don’t feel intimidated.</p><p>Do you have any tips on making the buying process easier? I would love to hear them.</p><p><em>Originally published at </em><a href="https://mattpieper.com/make-software-purchasing-painless/"><em>https://mattpieper.com</em></a><em> on February 22, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a384ec884d21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started With Gearset — Matt Pieper]]></title>
            <link>https://medium.com/@piepermatt/getting-started-with-gearset-matt-pieper-751b876a1305?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/751b876a1305</guid>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-devops]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Wed, 15 Feb 2023 13:02:22 GMT</pubDate>
            <atom:updated>2023-02-15T15:54:33.058Z</atom:updated>
            <content:encoded><![CDATA[<h3>Getting Started With Gearset — Matt Pieper</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxMH6jY1kLlxj_43rzds1A.png" /></figure><p>Unless you’ve been living under a rock, you’re aware of the buzz that Salesforce DevOps is receiving.</p><p>Salesforce DevOps Center went Generally Available (GA) in December of 2022, driving focus through the roof for a new way of working.</p><p>Have you or your company decided to move past change sets and start using a DevOps process? Or are you researching a new solution?</p><p>I understand <a href="https://mattpieper.com/our-journey-to-salesforce-ci-cd/">how difficult it is to navigate</a> the different options on the market is difficult whether you decide on Salesforce DevOps Center, Copado, or Gearset.</p><p>So for this article, we’ll dive into the basics of Gearset to go from zero to hero in under an hour. Seeing a product in action and comparing it to others will help differentiate the options available.</p><h3>What Is Gearset</h3><p>Gearset was founded in 2017, focusing on making changes to Salesforce environments easier. They not only focus on DevOps but Data Backup and Seeding as well. Adding these services to allow for fail-safe environments within your pipeline.</p><p>Gearset themselves market as:</p><blockquote><strong><em>The only platform you need for unparalleled deployment success, continuous delivery, automated testing and backups.</em></strong></blockquote><p>The company has been around for a while and has excelled in making DevOps easy for all your team members.</p><p>Their focus on making the compare and deploy experience easy to navigate is top-notch.</p><p>Gearset differs from Salesforce DevOps Center in a few different ways. This comes from their time in the market and focuses on being a standalone application.</p><p>DevOps Center cannot compare your organization in a side-by-side metadata view. This is a fantastic feature available in Gearset. Since metadata is XML, it is hard to manage within source control. Gearset’s semantic engine makes comparing metadata a breeze.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BtDZrpMR2BaDVznzOrnnqQ.png" /></figure><p>You can also automate your pipelines and build backpropagated pipelines, keeping your orgs in sync. Gearset can run automated monitoring jobs on your environments, warning you in advance if you have testing or coverage issues.</p><p>Back Propagation is a lifesaver, with changes in a hotfix branch to production automatically triggering those PRs to merge into lower environments.</p><p>Due to being source control based, changes can be pushed through the UI and via source control, aka GitHub and terminal changes.</p><h3>Gearset Pros</h3><p>I love the <a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">dog food approach</a> that Gearset follows. They release frequently, and you can always see what was pushed. Should we do the same within Salesforce? Letting our users know what has been released or changed so they can explore more?</p><p>The product allows you to get up and running fast. It just makes sense and is purpose built for agility and speed.</p><p>The support is top-notch. I don’t think I have ever had to wait for an answer for more than 5 minutes. Plus, if support doesn’t know something, they’ll contact the product team directly.</p><h3>Gearset Cons</h3><p>The product was originally designed for more individual workflows. As such, we don’t quite have the enterprise controls that we expect.</p><p>For instance, the pipelines are built around a single user. This has caused a few workarounds for us with our protected branches.</p><p>User provisioning is geared towards OAuth amongst Google and Salesforce. There’s currently no Single Sign On or <a href="https://www.okta.com/blog/2017/01/what-is-scim/">SCIM provisioning</a>.</p><p>Pipelines are still a new product for Gearset so there are a few bugs to work out.</p><p>That being said, Gearset is actively striving towards remedying all of the above and is responsive to user feedback.</p><h3>Getting Started</h3><p>Signing up for an account is easy. Gearset makes it relatively simple to signup for an account with your Salesforce account, LinkedIn, or Google.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZAFEpqLL5quyGKISIXETQ.png" /></figure><p>These are the same methods for authentication into your account — although I wish they had support for SAML and SCIM to allow for more enterprise user management.</p><p>Regardless of the method, you get free access through the trial for 30 days and receive no high-pressure sales cadences.</p><h3>Getting Around</h3><p>Once signed up, you’ll land on the homepage, a relatively streamlined experience with the ability to deploy changes front and center. I like this view because I can quickly start my deployment process. However, I sometimes wish it defaulted to my pipeline view, as I use it heavily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxMH6jY1kLlxj_43rzds1A.png" /></figure><p>Across the side panel, it’s broken into functional areas:</p><ul><li>Deployment (probably why you’re here).</li><li>Automation (CI/CD).</li><li>Data (excellent for seeding sandboxes).</li><li>Backup (pretty strong product).</li></ul><p>For this article, we’ll focus on the Deployment and Automation sections.</p><p>If you’re looking for user management, it’s hidden under the Gearset logo under My Account. This placement is a little odd, but you get used to it.</p><h3>Connect Salesforce Organization(s)</h3><p>What is DevOps without having Sandbox instances to connect to?</p><p>On the left side, click Salesforce Orgs, which brings you to a listing of all the Salesforce instances you have set up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDaJd6Nyg1bF9un1hS6vSg.png" /></figure><p>It’s important to note that these only display your individual accounts, not the entire enterprise. This is one area I’m hoping will improve this year. I would like to know what instances are set up, especially if changes leave my company to a personal developer account.</p><p>Connecting a Salesforce org is easy. Click Add New Organization, and you’ll be presented with a modal asking what type of account you want to add and its username.</p><p>Your username here is essential. If you change it in the next step, authentication will fail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2klT5cVKKnFh2MQVavKnkw.png" /></figure><p>You’ll be redirected to a Salesforce OAuth flow and accept the scopes.</p><p>Next, you can create a nickname for this org, so it’s easy to remember.</p><p>I turn on the monitoring for my production org and run unit tests. I also turn on unit tests for my staging environment, so I’m aware of any potential breaking changes well in advance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZpfEc30L5-aY7oNIPdemw.png" /></figure><p>We love the unit test monitoring as it has pointed out breaking changes in the past that may block future deployments.</p><p>Rinse and repeat for as many orgs as you need in your pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ca4T4PnHnq8RcS7e7gEOIQ.png" /></figure><h3>Connect Source Control</h3><p>Next, we’ll add source control. This is where all your metadata lives and acts as a repository for changes. As part of our DevOps process, we’ll push changes to source control, and then our Salesforce orgs will look to that repo to determine what to change.</p><p>Click Source control and services where you’ll land on a page with all the potential version control platforms you can connect to.</p><p>Me, I use GitHub. Clicking on GitHub, I’m redirected through an OAuth workflow and am done.</p><h3>Setup CI job(s)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FL_e67Uwyv10E5AgIHteQ.png" /></figure><p>Now we’re getting to the fun stuff! A CI job or Continuous Integration is where we tell Salesforce how to connect and listen to our source control repository.</p><p>We will use these CI Jobs as part of our pipeline later — you can create a CI job as part of the pipeline creation process. Still, for the sake of this post, we’ll keep them separate to highlight differences and if you still need to buy the pipelines feature.</p><p>To create a CI Job, we navigate to Continuous Integration and, for now, click on the grid or table icon.</p><p>Click Add new Deployment Job, which brings up a modal for a few crucial selections.</p><p>We have two approaches here. First, we choose the Source environment. If we need to build a source control-driven process, we can select a Salesforce org to act as the source. Since we are going with a source control process, for our example, we’ll choose Github as our source with the branch of UAT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtEB-wxjU6rQBN3gIhAgAw.png" /></figure><p>Next, we choose our target, which is our Salesforce org that we use for our UAT environment.</p><p>This does: for any changes that enter our UAT branch (through a Pull Request), sync these changes to our Salesforce UAT org. This starts a pattern of a branch per org pattern, allowing us to move changes in an automated fashion.</p><p>A few other necessary settings for calling out in the CI job.</p><p>One is the differences in deploying. If you’re just getting started and don’t want to make any significant destructive changes, leave off Deleted Items; you can always change this later.</p><p>Depending on your environment, you may leave running tests off on specific environments for speed of deployment. But I definitely recommend leaving running tests on in your staging environment. This ensures you don’t run into nasty surprises when you release to production.</p><p>Include User Permissions is something I would only enable if you’re comfortable with Salesforce metadata. Custom field permissions, permission sets, and profiles are some of the most detailed metadata to deploy. And, from personal experience, you can remove everyone’s FLS with one deployment, rendering your org useless. Best to leave this off as you’re getting used to DevOps.</p><h3>Notification Settings</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4u6TOn3CdgfA3wnRD3TGIQ.png" /></figure><p>These are personal preferences. I leave these off in my lower environments and only turn them on for production or staging. I want to know if things fail and have a digest every time something changes in my org for visibility.</p><p>This helps with troubleshooting because we have an RSS feed in the form of a Slack channel called #salesforce-deployments.</p><p>If something bonkers comes up during the day, I can scroll through Slack and click on a deployment to see if something in the environment recently changed.</p><p>I won’t go into setting these settings, but you can click on each blue help bubble to learn more.</p><h3>Metadata Filter</h3><p>This is one area we whiffed about when setting up our jobs initially.</p><p>During a compare and deploy, you can choose what metadata you want to move between orgs and what you want to commit to source control.</p><p>However, there’s a secondary approach when deploying as part of a CI job: the metadata filter in the CI job itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvNSVjoZ3SUxSNbROO6tbA.png" /></figure><p>Simply put, if you don’t select a metadata type here, your deployment will ignore it. I recommend choosing what is most common to your environment here. Setting more will slow down your jobs, and selecting less may leave out metadata when you release.</p><p>Once you’re comfortable with your settings, click save.</p><p>Congrats! You’ve set up your first CI job.</p><p>Rinse and repeat for the other environments you want as part of your DevOps process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ymE5NRp7p7cSY8wI4f8yhg.png" /></figure><h3>Build The Pipeline</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLkc6-5fZxnI40EH99XLuA.png" /></figure><p>We get a blank canvas if we click the pipeline button on the Continuous Integration tab.</p><p>This is where we draw our pipeline and set up individual components as part of the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGN8XnWCsdhuq7ThIqSMrQ.png" /></figure><p>For instance, reading from left to right, changes move from Integration to UAT to Staging to Production.</p><p>To start, we click on Add environment and then Add static environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3BRqdYo7ld6qM_uS1WTg8A.png" /></figure><p>Since we set up our CI Jobs in the last step, we will select Choose from an existing one. This will add the job to our canvas.</p><p>Here, I add my UAT and Production environments for this post. Still, you will have more in your experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_fXUt47jpGTg1q-sO2egfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Cq1B-mE7xqDxFX2RsiPyw.png" /></figure><p>From here, we click Edit environments to connect CI jobs, building our pipeline.</p><p>That’s it, we’re finished with the setup, and now we can push a change through. Easy, right?</p><h3>Make a commit and Pull Request</h3><p>I’m going to perform a bit of movie magic for the sake of this post, but let’s assume I’ve made a change in my developer sandbox or scratch org and want to push a change through to production using my newly created DevOps process.</p><p>To start, I click Compare and Deploy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxMH6jY1kLlxj_43rzds1A.png" /></figure><p>On my left, I choose my source org (my scratch org or dev sandbox); on the right, I select my source control, choosing to create a new branch off main.</p><p>Selecting main ensures we don’t push overwriting changes. This means we have a copy of what production looks like to compare against.</p><p>If you are working with someone on a feature or release, you may have to rebase off of another branch — which is outside the purview of this post.</p><p>When we click Compare Now, it will log in to both our source and target, comparing the metadata filters we selected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uIMmWwmnQcpjDc_QiplJJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MW_y2vAO_0yWPbpf5NNP5Q.png" /></figure><p>On the next screen, we see what is new, what has changed, and what has been deleted. This allows us to select what we want to push through our pipeline.</p><p>Gearset does a great job of parsing our metadata, highlighting green vs. red for what has been deleted or added between the environments.</p><p>Here, I select my change and advance to the next screen.</p><p>This review section warns me about what I want to remove or include for a successful deployment. This is where knowing your changes and how Salesforce metadata works come into play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SL5h1hn09ZZCtUQfnKREmg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8XI-Hh_UEluCeqsDVfu9sw.png" /></figure><p>These are best guesses, and sometimes you may need to override them based on your use case. Don’t worry. You’ll get the hang of this over time.</p><p>In the next screen, we can add our commit message and link to a Jira ticket if part of our process. I highly recommend a descriptive commit message so you have a running tally of changes and why. Better yet, use your ALM’s source linking features to ensure you have a running history of all changes in your org.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QNm4_81acwCtOfVCbYZk7w.png" /></figure><p>Gearset will push the commit to your remote branch.</p><p>From here, we’ll create our Pull Request to merge into our UAT branch, allowing us to kick off the process.</p><p>I like to include a description of what the PR does and the metadata in a list to make things easier during code reviews.</p><p>Once a PR is created, we see it staged in the pipeline. Gearset does some magic behind the scenes, creating a branch for each environment which does wonders for merge conflicts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxfoLkGgx2oDbjPzwJUEiA.png" /></figure><p>From here, we’ll merge into UAT, and the deployment process begins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O1ra5hHk-ZGk0cbKGYetnA.png" /></figure><p>Our change is successful, and we now see a new PR for our main (production) branch. From here, we can merge our PR once again, and we’ve pushed our change straight through.</p><p>Easy enough, right?</p><h3>Getting Started With Gearset Conclusion</h3><p>There are more features available in Gearset than we can mention in one article alone. But I hope this has been helpful to you in getting started.</p><p>Gearset releases changes on a rolling basis and has a helpful What’s new box to inform you that a new feature has shipped.</p><p>I look forward to hearing about your experiences with the product and any tips you have to share.</p><p><em>Originally published at </em><a href="https://mattpieper.com/getting-started-with-gearset/"><em>https://mattpieper.com</em></a><em> on February 15, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=751b876a1305" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero to Hero With Salesforce Scratch Orgs]]></title>
            <link>https://medium.com/@piepermatt/zero-to-hero-with-salesforce-scratch-orgs-532a85e13b8a?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/532a85e13b8a</guid>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce-devops]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 15:41:27 GMT</pubDate>
            <atom:updated>2023-01-19T03:49:46.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kuQVtxd3H2ar5-_M.png" /></figure><p>Salesforce <a href="https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs.htm">Scratch Orgs</a> have been part of the platform since they announced <a href="https://bluecanvas.io/2016/10/13/thoughts-on-salesforce-developer-experience.html">Salesforce DX</a> at Dreamforce in 2016.</p><p>But, we have yet to see the level of excitement that we do for other releases, such as the CLI. As a matter of fact, there’s no standalone Trailhead Module for them (although it is included in other modules).</p><p>As part of my interviews with prospective Salesforce Developers, I ask them about their experience with Scratch Orgs. The level of involvement varies, but I typically see ISVs use them more than embedded developers.</p><p>If we were to run a poll amongst most Admins and ask them if they use Scratch Orgs as part of their development process, we’d receive a resounding no.</p><p>Why is this the case? We’ll explore this question throughout this article and also walk through how to get started with Scratch Orgs as part of your development (to include declarative) process.</p><h3>What Are Scratch Orgs</h3><p><a href="https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs.htm">Scratch Orgs</a> are source control-driven temporary environments that can exist between 1–30 days.</p><p>What does this mean? For simplicity, we can consider Scratch Orgs as streamlined throwaway sandboxes.</p><p>They were built with the idea that they could be used within a DevOps process. Set up and torn down when needed for a specific purpose.</p><p>This helps us keep our environments fresh and avoid any dependency issues.</p><p>They can be set up and torn down automatically as part of your pipeline. You can set them up as each feature branch, keeping your content fresh.</p><p>Unlike traditional sandboxes, you can create and tear them down multiple times daily. Although, it is essential to know that there are still limits on how many Scratch Orgs are allocated.</p><h3>Differences Between Scratch Orgs and Sandboxes</h3><p>Both Scratch Orgs and Sandboxes are considered temporary environments.</p><p>They are used for developing and testing features before being released to production.</p><p>One of the best features of Scratch Orgs is the fact that we can push and pull code changes directly from the CLI through commands like `force:source:retrieve`</p><p>However, recently Salesforce introduced a Beta feature called Source Tracking. This allows us to use the same commands with Sandboxes as Scratch or Developer Orgs.</p><p>We can choose what we want to include in a Scratch Org. This dramatically improves the speed at which we can start a new org. This behavior is ideal when we want to spin up a new test environment after a major release for testing.</p><p>The most significant difference between the two is the ability to create/refresh your scratch org multiple times a day. You are limited to refreshing a Developer sandbox once a day.</p><p>True, you could make numerous Developer sandboxes to work around this. Still, you will eventually reach your limits for the number of used sandboxes.</p><h3>Why Use Scratch Orgs</h3><p>Scratch Orgs are used heavily in the ISV space, where packages are the primary development method. We see development akin to traditional software teams.</p><p>But, as Salesforce DevOps continues along its maturity path, we will see Scratch Orgs grow in popularity.</p><p>Within traditional software development, we utilize the engineer’s local device (or perhaps a virtual machine somewhere else) to develop and test before pushing to a different environment.</p><p>For Salesforce, these local devices are Sandboxes managed within Salesforce’s platform. One developer/admin affects another’s work if we run out of Sandboxes. This causes coordination issues and the potential for merge conflicts.</p><p>Since we have more latitude in the number of Scratch Orgs, we can create, this allows us more room to work independently. Engineers and Admins working on a feature branch together can cluster naturally.</p><p>Using Scratch Orgs as our development environment and our Sandboxes as our pipeline, we unlock some magic. Scratch Orgs for local work and our Sandboxes for integration, User Acceptance Testing, and staging.</p><h3>Why Are Scratch Orgs Not Being Used?</h3><p>We’ve explored the many benefits of Scratch orgs which may lead to a natural question: if they are so helpful, why are they not prolific?</p><h4>Difficult to Stay in Sync With Production</h4><p>The most prominent reason is that until recently, they were an enigma. There were multiple ways to create and design them, leading to frustration and exhaustion.</p><p>As changes occurred in production, we would have to ensure these changes were pushed to the Scratch Org. This is relatively easy if you’re using a source-controlled development process but nearly impossible otherwise.</p><p>Luckily, <a href="https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_shape_enable_org_shape.htm">Org Shapes</a> were introduced in the Winter ’21 release. This allows us to create a template that mimics production and keep our orgs in sync.</p><h4>No Major Reason For Smaller Organizations</h4><p>Smaller companies often do not run against their sandbox allocations. With few admins or engineers, there is no real need to share sandboxes, and the pain isn’t felt as much.</p><p>The work is also more easily visualized. While a small team may work on multiple projects at once — we should talk about the perils of WIP another time — they understand what is in their org end to end.</p><p>These smaller organizations also tend to focus on non-package-based deployments. Releasing through change sets as features are released. Advanced teams may adopt source control, but this is usually seen as a need for enterprise teams.</p><p>Over the past few years, a lot of time and energy has been focused on Salesforce DevOps. Salesforce itself just released its own DevOps Center to manage pipelines.</p><p>This has drawn attention to how we develop locally and push work through environments — even in smaller organizations. Yes, even as a Solo Admin, we can utilize DevOps.</p><p>As such, we should begin to change our development paradigm. Smaller organizations can begin to use the same development patterns as larger organizations. This <a href="https://mattpieper.com/leveling-up-salesforce-administrators">leveling up</a> starts to become a focus.</p><h4>They Can Be Confusing</h4><p>One of the significant advantages of Salesforce, and why it draws any career switchers, is its ability to manage the platform primarily through clicks, not code.</p><p>As Scratch Orgs were designed with engineers in mind, those who embrace the CLI and can visualize those same clicks as metadata, this breaks from the standard design pattern.</p><p>The CLI can be intimidating. It lives locally, not in the cloud. It is text and keyboard-driven, not UI driven. We have to remember a lot of commands to navigate.</p><p>Who wants to use Scratch Orgs and get past that learning curve if we’re presented with a significant learning curve with the CLI?</p><p>I totally get it.</p><p>I’m excited to see more declarative tools introduce ways to manage Scratch Orgs. This allows teams to work the way they work best.</p><p>Two of my favorite implementations of this are <a href="https://knowledgebase.autorabit.com/docs/create-a-scratch-org">AutoRabit</a> and <a href="https://docs.gearset.com/en/articles/1376520-configuring-sfdx-scratch-orgs-with-gearset">Gearset</a>. Both platforms have implemented Scratch Org management that is friendly to all team members.</p><p>UI-minded team members can use these tools, while CLI-minded team members can use the CLI. These teams can use both if they so choose! What’s better than that?</p><h3>Set Up a Scratch Org</h3><p>There are a couple different ways of setting up a Scratch Org, from using an Org Shape to a manifest. We will cover Org Shapes in a later article, so for the purposes here, we will use a simple manifest.</p><p>More about manifests can be found in this <a href="https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm">article from Salesforce</a>.</p><h4>Enable Dev Hub</h4><p>If you’re not aware yet, a good majority of posts on this site will start with enabling Dev Hub. There are a few dependencies to be resolved, which are outside of the scope of this post, but suffice it to say it’s a good thing to have turned on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n8mmZOaLvv3EGzMJCZvRrg.png" /></figure><h3>Create a Definition File</h3><p>Definition files allow us to get creative with how we want our org to look. For this walkthrough, we will utilize the sample file from Salesforce.</p><pre>{<br>  &quot;orgName&quot;: &quot;Acme&quot;,<br>  &quot;edition&quot;: &quot;Enterprise&quot;,<br>  &quot;features&quot;: [&quot;Communities&quot;, &quot;ServiceCloud&quot;, &quot;Chatbot&quot;],<br>  &quot;settings&quot;: {<br>      &quot;communitiesSettings&quot;: {<br>          &quot;enableNetworksEnabled&quot;: true<br>      },<br>      &quot;mobileSettings&quot;: {<br>          &quot;enableS1EncryptedStoragePref2&quot;: true<br>      },<br>      &quot;omniChannelSettings&quot;: {<br>          &quot;enableOmniChannel&quot;: true<br>      },<br>      &quot;caseSettings&quot;: {<br>          &quot;systemUserEmail&quot;: &quot;support@acme.com&quot;<br>      }<br>  }<br>}</pre><p>The definition file sets the settings we want within our scratch org.</p><p>You may name the file whatever makes sense for you and your team; for our purposes, we will name it project-scratch-def.json</p><h3>Create the Scratch Org</h3><p>The next few steps involve using the terminal, which can be intimidating. I recommend <a href="https://www.codecademy.com/learn/learn-the-command-line">Codecademy’s lessons</a> on using the command line if you’re not familiar with it.</p><p>Fire up a terminal/CLI session and run the following command:</p><p>sfdx force:org:create -f project-scratch-def.json -a MyScratchOrg --setdefaultusername</p><p>The following is displayed:</p><pre>Successfully created scratch org: 00D3D0000000PE5UAM, <br>    username: test-b4agup43oxmu@example.com</pre><p>The values for scratch org (a Salesforce ID) and username will vary for each scratch org that you create.</p><p>So what did we just do here?</p><p>sfdx force:org:create this is the base command to create a Sandbox or Scratch Org via the CLI</p><p>-f project-scratch-def-.json this parameter indicates that a definition file should be used; we specify the name of the definition file we created earlier.</p><p>-a MyScratchOrg here we create an alias for our Org, specifically MyScratchOrg, that we can use to indicate what orgs we want to open</p><p>--setdefaultusername is a handy parameter that we use to indicate this is the default org we want to use with our project. It keeps us from having to specify an org name each time.</p><p>Congratulations, you have created your first scratch org. Don’t believe me? Type the following command:</p><p>sfdx force:org:open -u &lt;username/alias&gt;</p><p>where &lt;username/alias&gt; is the username displayed in your Sandbox Org creation confirmation above.</p><p>If all goes well, your new scratch org will open in a new browser window and authenticate automatically.</p><h3>My Favorite Tips</h3><p>These all require the CLI, but there are a few handy lines:</p><p>sfdx force:user:password:generate</p><p>generates a random password for the scratch org user</p><p>sfdx force:org:display</p><p>will display the password if you use the -u &lt;your username here&gt; flag</p><p>sfdx force:org:open</p><p>opens the org you have set up within your project</p><p>sfdx force:org:delete</p><p>deletes a designated scratch org (or sandbox)</p><p>sfdx force:org:shape:create</p><p>creates a scratch org from an org shape</p><h3>Conclusion</h3><p>While I don’t see Scratch Orgs gaining massive popularity overnight, I believe that we will continue to see their use increase.</p><p>The value of being able to spin up a scratch org with the details that you want, open it, begin development, and sync to your source control cannot be measured.</p><p>If we combine this with automated test suites and data seeding, we can harness great productivity gains.</p><p>It is my belief that Admins and Developers who understand Scratch Orgs will have an advantage over those who are unfamiliar with the concepts as we continue to mature in DevOps within the Salesforce ecosystem.</p><p>This is why I continue to post about the power of Salesforce DevOps and how we can continue gaining knowledge.</p><p>What’s been your favorite use of Scratch Orgs that you’ve seen?</p><p><em>Originally published at </em><a href="https://mattpieper.com/zero-to-hero-with-salesforce-scratch-orgs/"><em>https://mattpieper.com</em></a><em> on January 18, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532a85e13b8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started With Salesforce DevOps Center — Part 1 — Matt Pieper]]></title>
            <link>https://medium.com/@piepermatt/getting-started-with-salesforce-devops-center-part-1-matt-pieper-b2d6c6908f07?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2d6c6908f07</guid>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Wed, 11 Jan 2023 04:30:29 GMT</pubDate>
            <atom:updated>2023-01-18T23:35:08.589Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hGiHNRqz8sWs2fvvFE1hMg.png" /></figure><h3>Getting Started With Salesforce DevOps Center — Part 1</h3><p>We’ve reached 2023, and DevOps in the Salesforce ecosystem has gained full momentum. <a href="https://help.salesforce.com/s/articleView?id=sf.devops_center_overview.htm&amp;type=5">Salesforce DevOps Center</a> entered GA in December 2022 as the answer to replace change sets for deploying changes between Salesforce environments.</p><p>I’ll admit that previously, I didn’t have <a href="https://mattpieper.com/devops-center-a-swing-and-a-miss/">much confidence </a>in the product. But I’m always willing to give a feature a fair try. Join me as I set up DevOps Center and learn what it’s about.</p><h3>What is Salesforce DevOps</h3><p>DevOps (or Development Operations) combines people, processes, and technology to provide value to customers. DevOps is considered a staple in an agile development team as it allows changes to be pushed rapidly and continuously.</p><p>DevOps has been around for the greater part of the last decade but only recently has been a focal point in Salesforce in the past couple of years. This focus was added as we look to deliver value quicker.</p><p>Traditionally (or at least since the early 201x), we have used change sets to push changes between Salesforce environments. But, change sets are wrought with challenges and have become a four-letter word amongst some Salesforce professionals.</p><p>Companies such as AutoRabbit, Copado, or Gearset entered the space to make changes more manageable and have built successful businesses doing so.</p><p>But, a Salesforce native solution was missing. In 2022, Salesforce fixed that by releasing Salesforce DevOps Center as a Beta. Now, it is Generally Available (GA) as of December.</p><p>DevOps Center uses a release management approach, bundling components together. It utilizes Source/Version Control through GitHub to track metadata changes and bundle releases along the pipeline.</p><p>This allows us to track changes and follow the history of our organization as it grows over time. Since Source Control automatically tracks these changes.</p><h3>Salesforce DevOps Center Drawbacks</h3><ul><li>Currently only supports GitHub as source control. GitHub Enterprise is not supported.</li><li>A bit tedious to set up. Not the worst, but certainly not the quickest.</li><li>No rollback features at this time. If we deploy a feature or release and need to revert, we have to create our own manual exclusion Pull Request.</li><li>Changes in metadata are represented by name only. No quick comparison of metadata changes to determine if we want to deploy a change.</li><li>No ability to back-propagate items from a hotfix branch.</li></ul><h3>Salesforce DevOps Center Advantages</h3><ul><li>Still an early product with plenty of room to grow. This is only the first iteration, and it’s solid. The learning curve is high, but we should see improvements as the Salesforce Product team receives feedback.</li><li>Will receive the most attention for changes in how Salesforce handles branch management.</li><li>Salesforce native. No need to manage another platform. Your security models will work directly with the center.</li><li>No additional cost. That alone is worth an exploration of the platform.</li></ul><h3>Getting Started With Salesforce DevOps Center</h3><p>Salesforce DevOps Center is available with Enterprise, Performance, Professional, Unlimited, and Developer editions.</p><p>You may install it in your Production or Developer edition orgs. DevOps Center is unavailable to install in a Sandbox or Scratch Org; however, you may utilize them as part of your pipeline.</p><h3>Enable DevOps Center</h3><p>Salesforce has recently moved towards a managed package approach to extend the platform. We have seen this with Code Builder, and DevOps Center is no different. There are a few small steps to complete within your organization.</p><p>To get started, navigate to Setup and type DevOps within the quick search bar.</p><p>Selective DevOps Center will bring the main screen with a toggle. There’s not much to see at the moment, but enabling the toggle brings up the acceptance modal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-x7mpj17PmW3jR7lns-Zg.png" /></figure><p>Clicking Accept activates the Install Package button. I won’t cover the following screens as it’s the same as installing any other package from the AppExchange. However, you should install it for Admins Only.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TKUMEgUCED0lJL0Ogbr8_w.png" /></figure><p>Once the package is installed — it takes a while. Feel free to get a cup of coffee — there are some additional steps before you can get into DevOps Center.</p><h3>Create a Connected App</h3><p>DevOps is powerful behind the scenes, connecting different orgs, and fully leverages the DevHub. We must set up a connected app to bridge the gaps.</p><p>Type App Manager into the Quick Find bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91g1Ju43Bw_ynNJqZExZcQ.png" /></figure><p>Click New Connected App to bring up the connected app screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rlvpMVwjfQm5dztEY_YtFg.png" /></figure><p>The exact name of the app doesn’t have to match, but for simplicity, I recommend matching the following fields:</p><ul><li><strong>Connected App Name:</strong> DevOps Center</li><li><strong>API Name:</strong> DevOps_Center</li><li><strong>Contact Email: </strong><a href="/service/mailto:support@salesforce.com"><strong>support@salesforce.com</strong></a></li><li><strong>Logo Image URL</strong>: <a href="https://tinyurl.com/doc-icon********************************">https://tinyurl.com/doc-icon</a></li><li><strong>Description:</strong> Manage your development and release processes</li><li><strong>Start URL:</strong> /sf_devops/DevOpsCenter.app</li></ul><p>Click Save, which will create the Managed App itself. Now we need to assign the app some permissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iRlS2lk85e4-3BtMnhEfog.png" /></figure><p>Clicking Manage will allow us to edit the policies assigned to the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EN_0wKc6836N0EKZQ2ad-Q.png" /></figure><p>We want to assign a permission set to the app to allow it to perform some actions on our behalf. This permission set came as part of the managed package we installed earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iFotu3XvH9ZlYgMKllnX7A.png" /></figure><p>See, no trickery here! The specific permission set we’re looking for is sf_devops_NamedCredentials. As the name suggests, it provides access to the Named Credentials for DevOps Center.</p><p>There are several other Permission Sets here if you look closely. I won’t go into deep detail here. Still, I suggest looking at the grants they give to familiarize yourself with the security model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J2q6Dl9oPI41iKLaPQpjzw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G33e2b-E4rB6o_NhW0Di-A.png" /></figure><p>Remember, we shouldn’t assign these to everyone, as least privileged access should apply.</p><p>For us to access DevOps Center, there are a few permission sets we need to assign to our DevOps Center users.</p><p>The following table comes directly from <a href="https://help.salesforce.com/s/articleView?id=sf.devops_center_assign_permsets.htm&amp;type=5&amp;language=en_US">Salesforce’s Help Center</a> and is a great reference:</p><h3>DevOps Center Permission Sets</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dldtNxCIECixk_NYYTUYCA.png" /></figure><p>Once permissions are assigned, you can launch DevOps Center from the App Launcher. It doesn’t look like much yet, but the magic is about to happen.</p><h3>Wrap Up</h3><p>That completes the initial installation of the Salesforce DevOps Center. This is where the real fun begins with setting up our pipelines and connecting to our version control system.</p><p>In the next part of this series, we’ll set up our pipelines which include connecting to GitHub and any sandboxes we want as part of our process.</p><p>So, get your logins ready; you’ll want at least two sandboxes, a production org, and your GitHub login credentials.</p><p><em>Originally published at </em><a href="https://mattpieper.com/getting-started-with-salesforce-devops-center-part-1/"><em>https://mattpieper.com</em></a><em> on January 11, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2d6c6908f07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveling Up Salesforce Administrators]]></title>
            <link>https://medium.com/@piepermatt/leveling-up-salesforce-administrators-3452f6e4db50?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/3452f6e4db50</guid>
            <category><![CDATA[salesforce-administrator]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Fri, 16 Dec 2022 05:59:07 GMT</pubDate>
            <atom:updated>2022-12-17T19:40:40.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*gsk-PDSWuSFwsYiq.png" /></figure><p>As we approach 2023, it’s time to think differently about our most powerful and robust professionals in the Salesforce ecosystem: Administrators.</p><p>Admins are the Swiss Army Knife within the platform: acting as Business Analyst, Data Analyst, Configurator, and in many smaller organizations, Architect.</p><p>The power of Salesforce is that it doesn’t take a solid technical background to set up — at least on the surface. It is easy to take some Trailhead lessons and be off and running, often landing a job as a Solo Admin in an organization.</p><p>We mainly learn what we have encountered in our travels. A Solo Admin knows to fail fast and learn fast. The most successful are like a mechanic, tinkering, adjusting, and learning how their org runs. But they don’t know what they don’t know.</p><p>They don’t get the privilege of code reviews. Others question the changes they’re making and suggest an alternative way of approaching a solution.</p><p>The rookie Solo Admin makes configuration changes tentatively at first. A talented Admin (Engineer, Analyst, Architect) reviews their prior work and realizes what they may have done differently.</p><h3>Challenges</h3><p>Admins that work in silos or do not gain exposure to other technical areas may face a few challenges in their journey. Specifically, if we toss an apprentice Admin into a complex business without support, we face the following challenges:</p><ol><li>Design and Architecture that may not scale</li><li>Do we miss better technical solutions (Opportunity Costs)</li><li>How do we know we’re building correctly (It worked, but why?)</li></ol><p>When I started with Salesforce, an Admin’s focus was relatively small. We leveraged our Developers for Triggers and Automation as we had only Workflow Rules to use. The design was pretty simple as we had page layouts, not the robust Lightning Record Pages we do today. Our data model was relatively simple, and we didn’t have easy, out-of-the-box solutions to move data from point to point. Event-Based Architecture, don’t even think about it!</p><p>I have come behind several organizations that have been a mess. You know the ones I’m talking about: everyone is an Admin, workflow rules galore, tons of custom fields, public reports that are duplicative, custom objects that are duplicated where a record type should have been, and more profiles than users even.</p><p>These organizations usually come from an overworked Admin or an Admin who lacks a solid technical design foundation.</p><p>Worse are those Admins who get pressured by others in the business who may have had some Salesforce Admin experience but did not receive exposure to best practices. They are pressured to build something that may not be best practice or doesn’t leverage modern design principles, such as Flow or Lightning Record Pages.</p><p>Disclaimer: I love Accidental Admins; they are great for the community. We should celebrate that we shipped a working feature. Still, we perform retros to understand why we should have designed it differently.</p><h3>The Technical Challenges</h3><p>Salesforce is a fast-moving ecosystem and is an open platform. Unless we take our time to learn about changes and new features, we are doing ourselves a disservice.</p><p>Admins need to understand that Lightning Web Components can display data that would typically take 3 or 4 custom objects in the data model.</p><p>Admins must know about OAuth tokens and Connected Applications. Admins need to understand security practices: that managed package that the business wants to install, oh, it wants Modify All despite only reading records from your organization, what is that about?</p><p>As Salesforce becomes increasingly the hub of a connected ecosystem, Admins will need to know more about how APIs work and error handling. What’s the order of operations? How do they investigate API failures from a connected application or event bus?</p><p>When we build Flows, we need to understand sound design principles and how DML works. Typically something that is left for Developers. This is a lot to take in.</p><p>DevOps is the new buzzword. But have we empowered our Admins to be able to read metadata? Our Admins know what it looks like in Setup, but what does the XML tree look like? Do they know how to look at a delta diff when they do a code review? Is it really a change or just the way git handles XML?</p><p>How do our Admins handle VCS? Are we empowering them to understand how VCS works and concepts such as commits, Pull Requests, Rebasing, etc.? These are concepts typically left in the hands of developers.</p><p>DevOps Center does a fine job abstracting these concepts. Still, for proper troubleshooting, our Admins must know the basic concepts to succeed.</p><p>Trailhead does have introductions to Git and VCS, but we need to dive in deeper. We should present our Admins as technical resources and leverage them as such.</p><h3>The Path Forward</h3><p>From a corporate strategy perspective, we must admit that Salesforce is robust but requires attention to harness its full potential. We should treat it with the respect that we do our bespoke products.</p><h3>Team Structure</h3><p>Salesforce teams should work technically and enforce their boundaries. Working with these boundaries will allow our teams to work creatively and design for the long term.</p><p>When every project is a fire, we tend to build ourselves into a corner, reacting to what’s put directly in front of us. If we allow our teams to breathe, we receive better results and foster creativity.</p><p>We should work to improve our intake processes, ensuring that incoming work is appropriately sized and specced. This allows us to bundle work and not be so reactive. This empowers our teams to think larger and see the big picture versus working on tickets verbatim without seeing the impact.</p><h3>Skillset</h3><p>As the platform scales, knowing each area of Salesforce becomes difficult, and we must specialize. Business Analysts, Developers, Administrators, and Architects are individual roles for a reason. They each require a particular skill set.</p><p>Business Leaders should realize that we wouldn’t have our engineers close our ledgers, so we shouldn’t expect accountants to code (but don’t stop them if they want to!). Dedicate room in your budget to hire dedicated expertise to support a vital tool within your business.</p><p>Salesforce is easy to learn the basics and start configuring. But, as the saying goes, it’s enough to be dangerous. Designing the most efficient way is a learned skill. We should provide training, resources, and mentorship to our team members. Hence, they gain exposure and develop best practices. Splitting time between your regular job function and administering a SaaS platform can lead to burnout and not provide the opportunity to grow as a technical professional.</p><p>We should provide our Admins with experience outside of Declarative. Yes, that’s a hot take. But, our Admins should understand how to integrate two platforms through standard design patterns. This teaches our teams to not force custom objects to store data that can be retrieved at runtime. Reducing our footprint and staying DRY.</p><h3>Feedback Loop</h3><p>We must provide a feedback loop to our teams and build the documentation around our projects. These ceremonies and artifacts help everyone involved learn and provide snapshots into our thought patterns.</p><p>We can reflect upon our prior decisions and understand their context as we continue to iterate.</p><p>Additionally, we should empower our Admins to think like Architects and Developers. Just as we should have our Developers think like Admins, etc. This breaks our standard thought patterns and allows us to devise alternative solutions.</p><p>As our Admins stretch their Architect wings, we should then provide feedback. Coaching what went well and opportunities to approach a solution differently. This does reduce the number of features shipped within a release in the short term but increases velocity in the long term as our team knowledge grows.</p><p>Salesforce continues to be a phenomenal ecosystem to be a part of. Seeing folks switch careers or learn new skills they never dreamed possible is fantastic. However, we shouldn’t shortchange them or our community by not providing support and resources to them.</p><p>We shouldn’t put Junior Administrators in a position where they are Solo Administrators that feel pressure from sides of the business that stunt their growth.</p><p>Conversely, we shouldn’t spec our stories so much that our Junior Admins can’t learn how to design solutions. If we always give our teams the answer, they’ll never know how to ask the right questions.</p><p>I look forward to seeing the ecosystem grow in size and knowledge. I will keep my inbox open for folks to bounce ideas off of.</p><p><em>Originally published at </em><a href="https://mattpieper.com/2022/12/leveling-up-salesforce-administrators/"><em>https://mattpieper.com</em></a><em> on December 16, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3452f6e4db50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connecting to Confluent Kafka from Mulesoft 4]]></title>
            <link>https://medium.com/@piepermatt/connecting-to-confluent-kafka-from-mulesoft-4-6715648360a7?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/6715648360a7</guid>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[mulesoft]]></category>
            <category><![CDATA[mulesoft-training]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Mon, 14 Nov 2022 04:23:21 GMT</pubDate>
            <atom:updated>2022-11-14T04:24:35.868Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*2kBintNxvFy-klcG.jpg" /></figure><p>Recently, I was working on a project connecting Mulesoft to a Confluent Kafka cluster while migrating from Heroku Kafka Connect.</p><p>Heroku Kafka Connect in a Private Space requires mTLS and IP allowlisting to connect to the producer. This method utilizes Consumer Plaintext within the Kafka connector in Mulesoft.</p><p>Contrast this to Confluent, which connects through a keyed connection over public HTTPS. Since I don&#39;t particularly appreciate recreating the wheel, I looked for configuration settings in the usual places. I found a helpful article on connecting <a href="https://dejim.com/connect-to-confluent-cloud-with-the-mulesoft-kafka-connector-mule-4/">Confluent with Mulesoft</a>, but it utilizes a deprecated Kafka connector (3.5).</p><p>Since the above article does a great job with the description except for the connector, this article will focus on the connector only.</p><p>We’ll utilize the Apache Kafka Connector to set up our configuration files. In the screenshots below, I’m editing inline for ease of display. However, in your environment, you should leverage environment variables.</p><h3>Connection</h3><p>Digging through the Confluent documentation, we notice that connections are over SASL_SSL. If we look in Mulesoft, there&#39;s no option for this particular setting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PjDZLIDXG1MmePTo.png" /></figure><p>According to <a href="https://mulesoftprm.force.com/s/article/How-to-Configure-Kafka-Connector-to-Use-SASL-SSL-Security-Protocol-With-PLAIN-Mechanism">Mulesoft Documentation</a>, SASL_SSL is the protocol used when at least a Keystore is set for a TLS context.</p><p>This leads us to select Consumer SASL/Plain Connection for our Configuration and ensure we have a valid TLS Context.</p><h3>General</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*BMcZLqFyASwW8mnp.png" /></figure><ol><li>Set the Connection to Consumer SASL/PLAIN Connection as described above</li><li>This is the server set in your environment in Confluent. It is also the server provided in the TXT file provided when you set your API Key.</li><li>Set the topic names that you are looking to subscribe to. These topic names can be found in your Confluent producer.</li><li>The username and password fields are for the API Key and API Secret set within the Confluent environment</li></ol><h3>Security</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/0*eTZVIk38xQr3Kub9.png" /></figure><p>As described above, Mulesoft will utilize a SASL_SSL connection when at least a keystore setting is set. Creating a keystore certificate is outside the scope of this article.</p><p>Important to note that in a production environment, you should probably set a global TLS Context for easier maintenance.</p><p>And that’s it, setting Mulesoft to connect to Confluent is rather easy once you determine what is working behind the scenes.</p><p>The new connectors are easier to work with, although I wish the documentation would be clearer. Since Confluent has a few connectors with Mulesoft for schema registry, I was shocked that there wasn’t much clear documentation on how to use Confluent as a producer.</p><p><em>Originally published at </em><a href="https://mattpieper.com/2022/11/connecting-to-confluent-kafka-from-mulesoft-4/"><em>https://mattpieper.com</em></a><em> on November 14, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6715648360a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hands-On With Salesforce Code Builder]]></title>
            <link>https://medium.com/@piepermatt/hands-on-with-salesforce-code-builder-795d6663c23f?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/795d6663c23f</guid>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Sun, 17 Jul 2022 03:15:53 GMT</pubDate>
            <atom:updated>2022-07-17T03:23:19.174Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQK4Um5aTYxfsTznfkO_yA.png" /></figure><p>After a long wait, Code Builder is finally here! Well, in beta, with a monthly usage cap. But, I’m excited to kick the tires and see how this will change our development flow.</p><p>Code Builder leverages VS Code for the Web, extending customized plugins through a managed package to embed VS Code within your Salesforce org.</p><p>I have customized my editor and terminal over the years, so it’s hard for me to shift to an online workflow. But, after tinkering with Code Builder, I can say definitively that this is a paradigm shift in how we will interact with our environment.</p><h3>Installation</h3><p>Code Builder allows us to edit our environment within Salesforce and work on any device, regardless if we’ve set up our local environment.</p><p>Code Builder comes as a managed package and will need to be installed into your Salesforce org. As always, it’s recommended to install in a Sandbox first to test and ensure there’s no interference with your production org.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k4G5gX3YSUjxhznj7F9NHw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JFtenjeIBeUkxLS0gL-gQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CHLqVXKsYXx2Rmz-xK6hQQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7fd37P3jI4wVjFD3ew6tFw.png" /></figure><p>Be sure to check with your security team to ensure they’re okay with third-party access to your environment. Although, it is access to Microsoft’s services.</p><h3>Permission Set</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x7d-6wihEb1AigH1MV-xvA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XaiJqLzUrSuKvB-wg6CzeQ.png" /></figure><p>Code Builder comes with its own Permission Set as part of the managed package. The Permission Set provides access to the Code Builder App and two Apex Classes.</p><p>Assign to your users and launch the app.</p><h3>Configuration</h3><p>Code Builder will walk you through the steps needed to configure. You have the option to create a new project or import from Github.</p><p>Since my org is under source control, I imported our repo to see what it looks like in browser as compared to my local repo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4SNSQgZ-bQO5q7FeFzkphQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibn78YSCsPD8lkE40lBfvQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h1R5A-b8C953yy-OW9M43g.png" /></figure><p>It’s recommended to connect to a Dev Hub, but since I’m testing I decided to connect only to a sandbox to ensure it’s loosely coupled to my orgs.</p><h3>We Wait</h3><p>The environment takes some a few minutes to setup and import your project.</p><p>It’s important to note here that your time limit decrements anytime that you’re in the Code Builder application. So I recommend navigating to another application while it is finishing its setup.</p><p>I learned the hard way when I saw that I lost six minutes of eligible time.</p><p>I am not sure if it’s a bug or not — it’s still a beta — but I had to connect to my DevHub in order to get an environment to launch. When I attempted to create an environment connected to a Sandbox, it seemed to timeout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-YvLrbJFj984TS0x1_zlQ.png" /></figure><h3>Use</h3><p>I have to say, having VS Code’s online developer experience directly within Salesforce is a game changer. Most often I resort to the Developer Console when I’m “in app” to test or make small tweaks.</p><p>Yes I know, VS Code and my trusty terminal are on my second virtual desktop. But, there’s something that seems so easy about being able to launch the Dev Console from within the UI.</p><p>With Code Builder, I see my reliance on Dev Console waning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJeeSe_N8ze23QdnzCT64g.png" /></figure><h3>Experience</h3><p>Code Builder launches with a blinding white screen, reminding me how much I have customized my VS Code theme over the years.</p><p>I quickly dive into the tour to see what is possible within the UI.</p><p>I learn that all of my VS Code shortcuts and the pallet are the same, there’s no learning curve here.</p><p>But, I do learn that it’s not full customizable. I am limited by what themes I can use (default only), and only Salesforce Extensions. None of my favorite JavaScript extensions are allowed.</p><p>I have a feeling this will relax over time as we get out of Beta.</p><h3>Developer Tools</h3><p>I fired up a blank project and create a scaffolded Trigger. The experience is the same as the desktop.</p><p>I can use the pallet or right click on the file to deploy to my org.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqmZTTrbZjN6QBjd--SzNA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwDrlcF2hMVgxQNIWPLc1Q.png" /></figure><p>The same experience for writing SOQL queries is present. This will definitely be a game changer for testing queries or running quick analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYr1VmyGWtI2MVbJo5zzIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8GCliW55onKGSXZeFdVBQ.png" /></figure><h3>Conclusion</h3><p>Code Builder is worth the wait. I am hoping that Salesforce will decide to not make this a paid SKU and release it from Beta soon.</p><p>Code Builder will change the way my team works, and I can see Admins being less intimidated by VS Code. This plus the focus on DevOps will introduce more Admins to how metadata is structured in Salesforce and allow them to pair with Developers more frequently.</p><p>My other hope is that we will see customizations enter the forefront and synchronize our settings with Github (or another profile service), to allow us to work across different organizations.</p><p>I hope that Code Builder will continue to grow, especially in the realm of Debug Logs. Having VS Code’s power to parse Debug Logs will make Code Builder the number one tool. This has the potential to replace Workbench and the Developer Console.</p><p><em>Originally published at </em><a href="https://mattpieper.com/2022/07/hands-on-with-salesforce-code-builder/"><em>https://mattpieper.com</em></a><em> on July 17, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=795d6663c23f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps Center: A Swing and A Miss]]></title>
            <link>https://medium.com/@piepermatt/devops-center-a-swing-and-a-miss-a4fd6a9619bd?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4fd6a9619bd</guid>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[salesforce-admin]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Sat, 18 Jun 2022 20:25:38 GMT</pubDate>
            <atom:updated>2022-06-25T15:24:18.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I_Od6XR9zxLVwGJVTWgmUQ.jpeg" /></figure><p>After much runup and hype, Salesforce debuted DevOps Center at TDX ’22. It is incredible to release new software, especially with a behemoth of a platform like Salesforce, and even more so when reinventing a deployment tool such as change sets.</p><p>While this is an excellent option for those who want a free tool to replace change sets, it is far from ready for enterprise use. Since its release, blogs have touted its value. But few, if any, have shed constructive feedback or room for improvement.</p><p>The release will be in Public Beta this month with GA this fall. Salesforce declared that it will finish what it starts during the True to the Core at TDX, and let’s hope that is the case with DevOps Center because we cannot call it DevOps.</p><p>This release reminds me of the Workflow to Flow converter. The messaging is lacking; the converter was designed to easily translate your Workflows to Flows with the intent that you use Salesforce best practices to create larger flows where it makes sense. Many an Admin has used this converter as gospel, polluting their orgs with countless flows.</p><p>I am disappointed that the Salesforce Ecosystem hasn’t surfaced more about this product and the potential harm it can cause. DevOps is a tried and trued practice, and haphazardly introducing this product will cause friction between Admins and Engineering teams.</p><h3>The Good</h3><p>First, let’s focus on what DevOps Center got correct. The typical Salesforce design elements make a product relatively easy to use for less technical Admins.</p><h4>User Interface</h4><p>Those of us used to Salesforce’s interface will feel comfortable with the UI and Kanban view of DevOps Center.</p><p>It includes the familiar Path element, easily indicating where a feature or release is on its journey. This view reduces friction for Admins transitioning to a new way of thinking as a user can find elements easily.</p><h4>Simplicity</h4><p>Unlike some other release products that attempt to reinvent git within Salesforce, DOC steers clear of that concept. Leveraging source control to do what source control does best while displaying data and interacting with VCS through the Salesforce UI.</p><h4>A focus and investment in ridding of Change Sets</h4><p>This is a huge step forward. After so many years of Change Sets and a lack of a pipeline view for declarative — and, to an extent, programmatic — changes, the ecosystem has a new way of deploying changes. As this is just the beginning of the shift, we can hopefully see change sets be a thing of the past.</p><h4>It’s Free</h4><p>That’s right, as of the time of publication, DevOps Center will be a free SKU when it goes to General Availability. Those who have been in the ecosystem for a while know all too well the disappointment of getting hyped for a new feature, only to learn we have to carve out a section of our budget if we want it. We can now use this feature without needing to convince our CFO to hand over cash.</p><h3>The Bad</h3><p>Ultimately, the product leads to bad design patterns and, in a shocking twist, less automation. I’m concerned that this feature will lead to anti-patterns and a generation of Admins that don’t fully understand Version Control or what DevOps means to the rest of the industry.</p><h4>Duplication of Effort</h4><p>DOC is far from DRY. Work items (stories) highlight work but need to be manually created and are isolated from the cycles. For those using Jira or other ALMs to track their work, this is a duplication of effort.</p><p>We must go into our ticketing system of choice, manually move or update the elements, and, even worse, create the items in DevOps Center.</p><p>A true DevOps or CI/CD pipeline creates a unified ecosystem where work advances seamlessly without manual intervention. Disclaimer: there are partner apps that will do this for you with DevOps Center — but these contradict the free SKU.</p><h4>GitHub Only</h4><p>At the time of publication, DevOps Center only works with GitHub as a VCS, alienating those who use GitLab, Azure, or BitBucket.</p><p>In fairness, GitHub represents a large portion of the market share for VCS, and I am sure that Salesforce did its research here. But, its competitors currently can connect to the most popular VCS on the market to include all the above.</p><h4>No Git Hooks</h4><p>From what I can tell, there’s no ability to connect webhooks or git hooks to trigger different events in our pipeline.</p><p>The inability to introduce static code analyzers, trigger more extensive unit tests in another repo, or even notifications are something that shocks me.</p><p>In 2022, our VCS should be able to interact seamlessly with our pipeline.</p><h4>Merge Conflicts Galore</h4><p>There is no built-in mechanism to determine merge conflicts in the UI, resulting in multiple failures and overwriting metadata.</p><p>To resolve any potential merge conflicts, we must rely on the semantic layer of GitHub. XML can be challenging to read and a foreign concept to most Business Salesforce Admins. This will introduce complexity and frustration — especially if they do not have a Developer to call for help.</p><p>Secondarily, it does not appear that we can ignore reordering. This is critical as metadata can be randomized due to how Salesforce structures it.</p><h4>No Back Promoting/Back Propagation</h4><p>It’s a one-way street here, folks. We assume that everyone follows the development process and nothing unexpected happens. Promote something out of cycle? Congratulations, you have a lot of synchronization work ahead of you to get your branches in parity.</p><p>The lack of Back Propagation may have a tendency for Admins and Developers to skirt the process and cause quite a bit of drift between environments.</p><p>It’s best practice to have an escape hatch or a hotfix branch for emergencies that need to be introduced directly to Production (we never have bugs, right?).</p><p>Without back propagation, we are guaranteed to raise drift and eliminate the advantages of DevOps.</p><h4>Easy to mess up GitHub Branches</h4><p>If you don’t know what you’re doing, this can set a bad experience with GitHub. I envision the scenario where Admins get frustrated with DevOps due to merge conflicts and not to understand what is happening under the hood with their Pull Requests.</p><p>Due to the Merge Conflicts mentioned above, and no autodeletion of branches, I imagine repos that will become unmanageable over time.</p><h4>Pay More Money Through Partners</h4><p>Salesforce has left out some functionality such as integrations with ALMs — think Jira. Product Managers make tough decisions on what features to ship and ALM integration did not make the rough cut.</p><p>This is a bit disappointing, but partners have stepped in to fill this space, at an additional cost to the consumer.</p><p>We all appreciate the AppExchange. This is not a completely bad thing. Bringing partners into the ecosystem has made Salesforce great over the past 20 years.</p><p>However, core functionality that we expect in a tool called “DevOps Center” should be available at Day 0, not on the roadmap. DevOps instills a concept of more automation, not additional manual effort.</p><p>This product clearly has potential, but Salesforce arrived far short of expectations. Salesforce has been pounding the DevOps drum through press lately, but this product needed to bake further.</p><p>I am disappointed that Salesforce didn’t attempt to acquihire in this space and build their own product.</p><p>I hope that Salesforce continues to invest in the product and pushes more through the next release, as this sets a bad precedent for those new to DevOps. This can develop bad habits for solo admins or admins without DevOps or CI/CD experience.</p><p>Perhaps if Salesforce wasn’t chasing trends such as NFT, we would see a better core product that affects all clouds.</p><p><em>Originally published at </em><a href="https://mattpieper.com/2022/06/devops-center-a-swing-and-a-miss/"><em>https://mattpieper.com</em></a><em> on June 18, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4fd6a9619bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Reasons Admins Should Learn SOQL]]></title>
            <link>https://medium.com/@piepermatt/five-reasons-admins-should-learn-soql-d50b5b1e2834?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/d50b5b1e2834</guid>
            <category><![CDATA[soql]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-admin]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Sat, 16 Apr 2022 22:17:27 GMT</pubDate>
            <atom:updated>2022-04-16T22:21:09.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/719/0*vbnaxN7cmyxAjOiA" /></figure><p>There is a powerful yet underused tool in the Salesforce ecosystem. That tool is SOQL. It is an asset that has been typically wielded by Developers, usually within Apex. This tool gets records and allows us to then manipulate them easily.</p><p>We are querying Salesforce Objects, sounds easy so far, right? SOQL (pronounced closely to Sock Well or So Quell) stands for Salesforce Object Query Language. SOQL is similar to SQL (pronounced sequel), Structured Query Language, and is used ubiquitously across almost every RMDBS on the market.</p><p>Salesforce isn’t the only company that adapted SQL in its product; quite famously, we have JQL, Jira Query Language.</p><p>While Developers use SOQL, it is typically reserved for DML operations, simply used as a vessel to carry out other tasks.</p><p>What if Admins could leverage SOQL to carry out other tasks? What if I told you that there’s a way to level up your day-to-day with just a little investment in learning a “language.” What does that even look like?</p><h3>Efficiency</h3><p>Who doesn’t want to be more efficient in their day-to-day duties? A few lines of SOQL can do wonders. My engineering habits haven’t faded as I have transitioned into leadership roles, so I always have a terminal window open.</p><p>Thanks to the SFDX or Salesforce CLI, I can perform many functions directly from my terminal without having to worry about firing up a browser window and logging in.</p><p>I don’t have to create a report to ask a question about my data. I am sure most of the seasoned Admins out there have their canned reports written and can adapt them in seconds to see what is happening in their organizations.</p><p>But what if you just want to see if a user has logged in recently? Maybe you want to check to see if a particular integration is running. Do you need to check on it periodically throughout the day? SOQL is your friend!</p><p>You can use SOQL in various places: Terminal, VS Code, Workbench, Developer Console, and even third-party tools such as Jetstream App.</p><p>So which users have logged on in the past day? I could run a logins report, or I can use the following line:</p><pre>SELECT Username FROM User WHERE LastLoginDate = TODAY</pre><p>What if you wanted to know the number of users logged in today? With one quick change, I can grab that answer:</p><pre>SELECT COUNT(Username) FROM User WHERE LastLoginDate = TODAY</pre><p>One last example, from the command line, we can grab a list of all users who logged in today and export that directly to a CSV:</p><pre>sfdx force:data:soql:query -q &quot;SELECT Username FROM User WHERE LastLoginDate = TODAY&quot; -u &quot;<a href="https://mattpieper.com/cdn-cgi/l/email-protection">[email protected]</a>&quot; -r csv &gt; user_logins.csv</pre><p>These are simple examples, but it highlights the power of SOQL to quickly gather data without sledging through the report writer.</p><h3>Automation</h3><p>We can leverage the command line and SOQL to automate uploads. Or we can use it to purge records or mass update records. Who doesn’t want to make their lives easier?</p><p>We all have those jobs that we have to do repeatedly, and SOQL enables us to shave time off them. Wrapping SOQL in a quick shell script can help us ingest data, transform it, and then insert it directly back into our instance. All without the need to use our friend XLOOKUP.</p><p>While a bit advanced we can write a couple lines of Apex with SOQL to automate so many things.</p><h3>Career Development</h3><p>Since SOQL is aligned with SQL, it opens up avenues for career advancement. Once you start thinking in a query format, you can apply it to SQL and other databases throughout your company.</p><p>If your company is relatively tech-forward, you probably have a data democratization approach, where employees have access to other datasets. Access to these datasets allows you to stretch your SQL muscle. Next, you can start combining Salesforce data with other company data. This opens up avenues to build robust dashboards for your stakeholders.</p><p>You can find yourself on different career paths, such as a data analyst. After a while, you may find out that you like working with SQL and data. Pulling data from other sources can also help you validate source data coming into Salesforce.</p><h3>Understand Your Schema</h3><p>When we traverse our schema, we learn more about it. We have to know what our schema is and which object to start from by writing queries.</p><p>Choose an object too high in a schema, and we’re not going to get the fields we want. Start too low, and our query may be inefficient.</p><p>It also requires us to grasp which fields are in which object. Without the benefit of the drag and drop report writer, we rely more on our brains, committing things to a logical path.</p><p>The last and most crucial piece forces us to pay attention to API names. It makes us become better partners to our developer counterparts. I have often heard an Admin say: we’ll just change the field label and leave the API name. Or, don’t worry about the API name.</p><p>When we write SOQL, the API name is critical for us. We use it to determine which fields to grab. When we have to type horribly named API names, we start to understand the importance of having data parity.</p><h3>Improve Your Flows</h3><p>We know that the Get Records operation in Flows is valuable, especially when we need to perform a DML operation. But, we often don’t ask what that operation is doing underneath the hood. How is my process performing? Could it be optimized?</p><p>At its core, you can compare the Get Records operation to running a SOQL query in the background to get the records you want.</p><p>( In actuality, this is abstracted to other languages and through Salesforce’s own ORM, but for simplification, we’ll use SOQL as the concept is similar)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fhPNbGmZQHMkb6ah" /></figure><p>How would we get those same records through SOQL? What would that look like?</p><pre>SELECT Id, StageName, Amount FROM Opportunity WHERE IsWon = True ORDER BY Name ASC LIMIT 1</pre><p>The above query grabs the fields we want to return — to use later in our Flow — filters by the IsWon field, and then sorts by Name in an ascending manner. Notice the keyword LIMIT, this makes our query return only one record. This query isn&#39;t too complex since we&#39;re only traversing one object, but more complex queries will need to be written for performance.</p><p>We are just scratching the surface of what SOQL can do for you. If we use SOQL in conjunction with learning a shell language or maybe wrapping a bit of Apex around it, we can accomplish many wonders.</p><p>You don’t need to invest much time learning SOQL to reap results. You can be up in the running in less than an hour, especially if you have a solid grasp of your data model.</p><p>Stay tuned for an introduction to SOQL and how you can get started!</p><p><em>Originally published at </em><a href="https://mattpieper.com/2022/04/five-reasons-admins-should-learn-soql/"><em>https://mattpieper.com</em></a><em> on April 16, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d50b5b1e2834" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce Renaming Extravaganza]]></title>
            <link>https://medium.com/@piepermatt/salesforce-renaming-extravaganza-75982e6b6d4c?source=rss-13ed0c581724------2</link>
            <guid isPermaLink="false">https://medium.com/p/75982e6b6d4c</guid>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Matt Pieper]]></dc:creator>
            <pubDate>Thu, 14 Apr 2022 02:48:22 GMT</pubDate>
            <atom:updated>2022-04-14T02:50:07.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*8Tzzqc4M6KJ1tboQ" /></figure><p>It’s time again to figure out which Salesforce products I own and if I know their new names. Luckily, I can rest assured that my Mulesoft, Slack, and Heroku products will retain their original branding. However, I have seen a few lightning bolts that may hint at something in various places across the platform.</p><p>Now, I’m not faulting Salesforce for changing product names or shifting other add-ons to add clarity around offerings. A rebranding exercise is no small undertaking. The number of hours spent across the enterprise add up, not to mention the capital spent for new signage and other assets.</p><p>For some reasons, such as through acquisition, it makes sense to rebrand. You don’t want to rename a product immediately after acquisition. Some customers may not want to be part of the Salesforce umbrella, so it’s an easy way to ease those clients and maintain brand loyalty.</p><p>Salesforce wants to have a cohesive market strategy and brand identity like any brand. But those names don’t last forever. So, there comes a time when products get renamed; sometimes for the better, sometimes for the worst.</p><p>This is without its side effects, though. It can lead to confusion for long-term customers. Do I own this product, or is it new? Administrators and others in the Salesforce support ecosystem may get random questions from their users.</p><h3>Tableau CRM</h3><p>It is no surprise that Tableau CRM is being renamed again to CRM Analytics. The attempt to bring Tableau’s brand into Salesforce backfired with mass confusion around naming. Admins everywhere had to clarify to their business partners that they did not own Tableau, that Tableau CRM is a product within Salesforce.</p><p>What is shocking is that we haven’t entirely locked down the name of this product. We have run the gamut from Wave Analytics to Einstein Analytics.</p><p>I am shocked to see the tie to CRM when clients use the platform for much more than CRM-related tasks. Why not open up the brand to more?</p><h3>Marketing Cloud</h3><p>Marketing Cloud has always been a challenge because it has been a jumble of acquired products. The team has done an excellent job weaving disparate products under one umbrella. In my opinion, it’s one of the most challenging clouds to navigate, from both a technical and naming perspective.</p><p>For a product designed for marketers, it’s understandable that they want to attempt and create a cohesive image for the marketing persona.</p><h4>New product names:</h4><ul><li>Pardot: Marketing Cloud Account Engagement</li><li>Salesforce CDP: Marketing Cloud Customer Data Platform</li><li>Advertising Studio: Marketing Cloud Advertising</li><li>Interaction Studio: Marketing Cloud Personalization</li><li>Messaging/Journeys: Marketing Cloud Engagement</li></ul><p>It’s easy to pick up the pattern of Engagement and unification under Marketing Cloud. This renaming highlights they want to use the strength of the Marketing Cloud identity.</p><p>Most of these names are easy iterations, but the transition from Pardot to Marketing Cloud Account Engagement is intriguing. I know we have all grimaced when someone asks about Pardough, so it’s nice to have a different name to look forward to. But is it truly an Account-based marketing tool? So many customers utilize it for B2C messaging; it’s easy to do. It even has built-in transactional messaging, which is perfect.</p><p>It’s still early in 2022. These names are being released right before TDX2022, so we may see some new features released in the coming weeks. Since TDX is usually a trailer for Dreamforce. We could be seeing a significant focus on Marketing Cloud and Analytics this year.</p><p><em>Originally published at </em><a href="https://mattpieper.com/2022/04/salesforce-renaming-extravaganza/"><em>https://mattpieper.com</em></a><em> on April 14, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75982e6b6d4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>