Peeklogic’s Post

Good to know

Integrating Salesforce with External API using Named Credentials → Introduction → Key Features of Named Credentials → When to Use Named Credentials → How to Set Up Named Credentials → Basic Structure for Calling API with Named Credentials → Benefits of Named Credentials → Named Credentials and Apex → Named Credentials & API Callouts → Handling Authentication with Named Credentials Follow TrailheadIQ Venkat Sumanth Guduru Check out → https://trailheadiq.com/

🚀 Excited to Share a Game-Changing Feature from Salesforce Winter ’25 Release! The Object Access Summary is a fantastic addition to the Object Manager in Lightning Experience! 🎉 It gives a consolidated view of Permission Sets, Permission Set Groups, and Profiles that grant access to an object, along with the specific levels of access (Read, Create, Edit, Delete, View All, and Modify All). 🔍 Why is this a big deal? No more endless digging through multiple permission sets or profiles to troubleshoot or audit object access. This new read-only feature simplifies user access reviews, makes compliance checks easier, and significantly improves productivity. 📍 How to Access: Go to Setup > Object Manager. Select an object. Click Object Access in the sidebar. Have you tried this feature yet? Let me know your thoughts in the comments! 💬 #SalesforceWinter25 #ObjectAccessSummary #SalesforceAdmin #Efficiency

INACTIVE_OWNER_OR_USER As Salesforce pros, we've seen this error before, especially when doing a Data Load. Today I learned there's a solution: You can give users the ability to edit records owned by inactive users. 1. Go to 'Setup' > 'User Interface' > 'Enable "Set Audit Fields upon Record Creation" and "Update Records with Inactive Owners" User Permissions'. 2. Create a permission set. 3. Add 'System Permissions' > 'Update Records with Inactive Owners' to the permission set. 4. Grant it to the user. There's always something to learn in the ecosystem. Reference: https://lnkd.in/eK8KdGgU

Salesforce Apex Annotations with their code examples: https://lnkd.in/dspXruXs Table of Contents @AuraEnabled @TestSetup @isTest @Deprecated @Future @InvocableMethod @ReadOnly RESTful Service Annotations Benefits FAQs

This is GREAT! As a part of offboarding, I like to try to reassign records as much as possible, but too often there's a waiting period for a new hire. Thanks for sharing Tim! #salesforcetips #salesforcetricks

😎 Boost your Salesforce flow debugging with this tip ! Do you find it hard to debug flow created by another admin or developer ? It may be due to the bad naming conventions. It is really important to use best naming conventions while writing the flows in salesforce. It becomes really difficult to debug complex flows if it is created with bad practices. I've been using this naming convention for a long time. And I've found it on this wonderful blog. (Check blog link in comment). Since the flows becoming more and more powerful every realease. It is important that you practice these best practices religiously. Additional Tip : Alwasy use IN_ and OUT_ as variable prefix for input and output varibles in flows. Share the best practices that you follow in comment :) #SalesforceFlows #Standard #NamingConventions #CodeQuality #BestPractices #DeveloperTips #Trailblazer

🔍 Unlocking Salesforce Insights: Essential Postman Queries for Salesforce Org Information 🔑" Description: Discover the power of Postman queries in uncovering invaluable insights about your Salesforce organization. In this document, we delve into a comprehensive array of queries tailored to unveil crucial details about your Salesforce environment. From retrieving record counts and exploring object metadata to executing SOQL queries and managing limits, each query serves as a key to unlocking vital information. Whether you're a Salesforce admin, developer, or enthusiast, this document equips you with the tools to navigate and understand your Salesforce org efficiently. Harness the potential of Postman to gain deeper insights into your Salesforce instance and optimize your organization's performance. 🚀

I couldn't wait ;) Note: This limit applies only to email messages composed and sent through the API or Apex. This is not trackable currently in 'Setup.' However, there is a convenient way to track the limits and usage for the organization, using the Workbench tool. From time to time organizations may hit their SingleEmailMessage limit. When this happens, you will see the following email message:    'SINGLE_EMAIL_LIMIT_EXCEEDED, The daily limit for the org would be exceeded by this request'    Resolution Use Workbench to track organization limits and usage   1. Ensure you are logged into the organization where you want to verify your limits. 2. Navigate to: https://lnkd.in/ee3xpVGZ 3. Accept any oauth prompts to complete authentication 4. On the 'Jump to' picklist select REST Explorer. 5. Click Select. 6. Enter in the following, replacing "XX" with the current API version: /services/data/vXX.0/limits 7. Click Execute. 8. Select the SingleEmail area to view the daily maximum and remaining calls. Notes: SingleEmailMessage calls are calculated for a 24 hour period from 12 midnight UTC (00:00) - the limit will reset to zero at this time each day. Emails to each recipient are counted, such as addresses in the 'to' and 'cc' email fields. There is a default value for each organization. the limit is not related to license count. See also Single email daily limits for messages sent using API methods To learn more about the relevant governor limits, please review our Apex Developer Guide.

Did you know there are five different paths you can take to strategically manage Salesforce errors? If you’re on the hook for Salesforce at your company–or you’re a developer or architect–watch this Apex Hours video, “Managing Salesforce Errors: From Logging to Observability.” Originally a webinar for the Apex Hours community, the new assessment takes a hard look at your different options for staying on top of Salesforce issues–before they become critical business problems. There's also now an indexed transcription of the entire presentation, so you can skip right to the topics you’re most interested in and find links to the tools and platforms mentioned. Salesforce has become business-critical for many institutions, so there's a growing sense of urgency to put in place a true monitoring and troubleshooting strategy. The webinar's two expert hosts, Nikita Prokopev and Matt Kaufman, take a fresh look at what's available–from open-source logging frameworks to commercial observability strategies–and evaluate the pros and cons of each. The transcript can be found here, together with the video (free, of course): https://lnkd.in/eVBtEA36 Which paths are you considering? #salesforce #salesforcelogging #salesforcemonitoring #observability #salesforceadmin #salesforceadministrator #salesforcedevelopers