Sunday, 27 August 2023

Selective Sandbox Access

 With Selective Sandbox Access, you can limit access to a sandbox to only the required users during the refreshing or creation process.

No more worrying about unauthorized users accessing sensitive sandbox data!


By default, all active users in the source org have access to the sandbox.


However, now you have the power to grant access to specific users through a public group.


This means you can choose who gets access and maintain control over your sandboxes.


One fantastic benefit of Selective Sandbox Access is that the email addresses for the users included in the public group will remain in their original format.


No need to modify or append ".invalid" to their email addresses.


This makes the process streamlined and hassle-free.


But what about users who are not part of the public group?


Well, they can still gain access, but there's an additional step.


They will need to be unfrozen in the sandbox. This ensures that only authorized users can access the sandbox and guarantees a secure environment for your testing and development needs.


Selective Sandbox Access will be available in production orgs starting mid-October 2023 with the Winter '24 release.


If you have the Manage Sandbox user permission, you'll have the opportunity to leverage this feature.



Note :

With selective sandbox access, grant access only to required users. It also removes the additional step for a Salesforce admin to change the user email address back to the original format. If you don’t want to match the access currently defined in the source org, you can create a public group to grant access to a subset of users.


If you don’t see the option “Sandbox Access User Group”, while creating the sandbox in your production org, please log a case with Salesforce.


DataRaptors in OmniStudio

 A DataRaptor is a mapping tool that enables you to read, transform and write Salesforce data.


DataRaptors supply data to OmniScripts and OmniStudio FlexCards from Salesforce, and write updates from OmniScripts and Flexcards back to Salesforce.


Types of DataRaptors :


1.Turbo Extract  : Get data from a single Salesforce object (sObject).

2.Extract : Gets data from one or more Salesforce sObjects.

3.Load : Saves data to one or more Salesforce sObjects by 


—>Updating Salesforce records

—>Creating Salesforce records

—>Migrating CSV data into Salesforce records.


4.Transform : Manipulates any data that comes from inside or outside Salesforce.


Data Raptor Designer :


Extract tab

Formulas tab

Output tab

Options tab

Preview tab


Note : Tabs are subject to data raptor type.


In the DataRaptor designer (Extract) , we get the above tabs to work with.Some of these tabs are common in all the DataRaptors.

Sunday, 9 July 2023

Salesforce Integrations

 



Salesforce Integration Levels 

1.UI Integration

2.Process Integration

3.Data Integration


UI Integrations :


        1.Force.com Canvas SDK

        2.LWC/Aura + Apex Callout

        3.Javascript Fetch API


Process Integration:


  1.Platform Events

  2.Salesforce REST API

  3.Apex SOAP service

  4.Trigger+ Apex Callout

  5.Enhanced External Service

  6.Salesforce SOAP API

  7.APEX REST Service

  8.APEX Email Service


Data Integration :

  

1.Salesforce Connect

2.Change Data capture

3.Bulk API 2.0

Monday, 3 July 2023

Handling Large Data in Salesforce

 Managing large data volumes in Salesforce necessitates employing effective strategies and optimization techniques. Below are some recommended approaches to handle this situation efficiently:


1. Data Archiving and Purging: Identify historical or redundant data and archive or delete it from the Salesforce instance. This practice helps reduce the overall size of your database and enhances performance.


2. Data Model Optimization: Design your Salesforce data model in a manner that minimizes the number of records and maximizes data reuse. Use appropriate relationships, such as lookup or master-detail relationships, to avoid data duplication.


3. Indexing: Index critical fields used in search filters or report criteria. Indexing can significantly enhance query and search performance on large data sets.


4. Bulk API: Utilize the Salesforce Bulk API for operations involving large data volumes, such as data imports, updates, or deletions. The Bulk API enables processing large data sets in batches, leading to improved performance.


5. Asynchronous Processing: Consider leveraging Salesforce Asynchronous Apex or Queueable Apex for resource-intensive operations. These mechanisms enable the management of long-running processes without adversely affecting the user experience.


6. Data Loader and External Tools: Take advantage of tools like the Salesforce Data Loader or third-party ETL (Extract, Transform, Load) tools to handle large data volumes efficiently. These tools facilitate data migration, synchronization, and manipulation tasks at scale.


7. Governor Limits and Limits Management: Ensure that your processes operate within the Salesforce governor limits. Monitor system usage and implement measures to gracefully handle limit exceptions.


8. Data Partitioning: If feasible, partition your data into smaller logical units to enhance manageability. For instance, consider partitioning data based on geographical regions or business units.


9. Data Archiving Services: Salesforce provides data archiving solutions like "Big Objects" that can handle large historical data volumes that are infrequently accessed. Utilize these features to offload older data from your primary tables.


10. Performance Tuning: Regularly monitor your Salesforce instance's performance and optimize slow-performing queries or processes. This may involve creating custom indexes, optimizing code, or reevaluating data access patterns.

Sunday, 2 July 2023

Salesforce Connect

 What is Salesforce Connect? 


Salesforce Connect provides seamless integration of data across system boundaries by letting your users view, search, and modify data that’s stored outside your Salesforce organization, without actually copying the data into Salesforce. Salesforce Connect is a point-and-click solution to your other databases, and it makes earlier integration scenarios seem archaic.


Data from external systems are available as External Objects in Salesforce that are similar to Standard and Custom Objects so things like Tabs, Page Layouts, Custom Fields exist.


Salesforce Connect is used most Commonly


1.Searching External Data

2.List Views

3.Record Views

4.Related Lists



Note :

We can’t create formula fields, validation rules, and workflows on External Objects.



Salesforce Connect Cross Org :


Salesforce Connect Cross Org is one of the adapter types available in Salesforce Connect. When you define an external data source in your organization, you specify the Salesforce Connect Cross Org adapter in the Type field, and this will allow you to connect your org to another org, and access the records of this other org in your current Salesforce org.


(OR)


With the extension of Salesforce Connect Cross Org Adapter in the external data source, the users can create, edit, delete the records in/from the external system with support of writable interface.

Friday, 30 June 2023

Get Salesforce System users using SOQL - Tip

 Salesforce doesn't let you access the Automated Process and System User from the Salesforce UI. However, you can use SOQL to get the information on these two Users.


SELECT Id,ProfileId,Name,Profile.Name,Alias,Email,Createddate,IsActive FROM User WHERE Name =’System’ OR Name=‘Automated Process’

Monday, 26 June 2023

Salesforce non-deterministic formula fields

 Here are examples of common non-deterministic formulas. Force.com cannot index fields that:

  • Reference other entities (i.e., fields accessible through lookup fields)
  • Include other formula fields that span over other entities
  • Use dynamic date and time functions (e.g., TODAY, NOW)

A formula is also considered non-deterministic when it includes:

  • Owner, autonumber, divisions, or audit fields (except for CreatedDate and CreatedByID fields)
  • References to fields that Force.com cannot index
    • Multi-select picklists
    • Currency fields in a multicurrency organization
    • Long text area fields
    • Binary fields (blob, file, or encrypted text)
  • Standard fields with special functionalities
    • Opportunity: Amount, TotalOpportunityQuantity, ExpectedRevenue, IsClosed, IsWon
    • Case: ClosedDate, IsClosed
    • Product: Product Family, IsActive, IsArchived
    • Solution: Status
    • Lead: Status
    • Activity: Subject, TaskStatus, TaskPriority