LinkedIn

Integration Using Salesforce Connect - Part 3 - Considerations

-

 In the previous 2 posts, we saw how we can use different adaptors to access and display data from an external system using Salesforce connect. Let us see some additional considerations on, when we can select Salesforce Connect as an integration Option.

Usually when we need to frequently display or modify data from an external system in Salesforce, but you don't want to store that in Salesforce, Salesforce connect is a good Integration option. But consider the below factors before you make your Integration option as Salesforce Connect.


1. Salesforce Connect - License Considerations

Salesforce Connect is an Add-on license. Based on the Salesforce documentation, if we purchase 1 license the usage is like below:


That means:

  • You can use one license in 1 org only
  • If you want to connect to a different non-salesforce data source, you need to purchase an additional license
  • You can connect up to 5 different Salesforce org using a single license

2. Salesforce Connect - Rate Limits


3. Handling High Data Volume

If we need to skip the rate limits mentioned above for large data volumes, we can choose high data volume option while creating External Data Source.

But when we enable High Data Volume option - Some Salesforce Connect features will not be working as mentioned below:

  • Access via Lightning Experience
  • Access via Mobile experience
  • Reports and Dashboards
  • Writable External Objects
  • Recent Items availability
  • Record Feeds
  • Salesforce Classic console
That means you can use External objects in Classic view only if High Data volume is enabled.

4. Controlling Record Visibility

Cross Org Adaptor - Subscriber org fetches all data from the source org, where the user used for setting up authentication has access. We cannot control record visibility through OWD or through sharing.

OData Adaptor - At profile level we will be giving Read/Edit/Delete permission and if a user has Read permission to an External object, he will be able to see all records as part of External Object. We will not be able to control record visibility.

If we want to restrict record visibility on specific criteria - Then Salesforce connect is not a good option.

5. Customization Feasibility on External Objects

There are many features/customizations which are not supported for External Objects. Let us see those list below:


6. SOSL and SOQL Limits

  • External object search displays only the top 25 records
  • Search is supported only in Text, Text area fields
  • External Objects don't support the below operators:
    • INCLUDES
    • LIKE
    • EXCLUDES
    • toLabel()
  • External Objects don't support below in SOQL
    • AVG
    • COUNT()
    • HAVING
    • GROUP BY
    • MAX()
    • MIN()
    • SUM()
7. Sync Considerations

When we perform sync and validate on an already synched external object, it will override all fields. So if you have performed some label changes or some other changes, on synched fields, you will lose those. To avoid this, better we create our own external object referring the actual external object, so that changes will not get overrided.

References
https://help.salesforce.com/articleView?id=odata_general_limits.htm&type=5
https://help.salesforce.com/articleView?id=platform_connect_considerations.htm&type=5

Comments

Post a Comment

Popular posts from this blog

Subscribing to Salesforce Platform Events using External Java Client - CometD

-
Image
Platform Events follow event based Architecture, where multiple subscribers can subscribe to a published event in real time manner.  Below diagram shows the basic Architecture of the event-based communication Model: Event - This is a change in state for a business process Event Message - Data about the event Producer - Publisher of the event Event Bus - A communication and storage service for published events Event Consumer - A subscriber to the channel Platform events can be subscribed internally and also externally Platfrom events  - Internal Subscription Below are some scenarios in which you can consume platform events internally: 1. When we need to execute functionalities asynchronously to save govornor limits 2. To build a proper exception logging framework - You can find more details here  How to subscribe Internally? we can see more details about this in a different blogpost. Platfrom events  - External Consumption Many Organizations are moving to event-based integration appr
Read more

Salesforce Security - Restriction Rules and Scoping Rules

-
Image
1. Overview Salesforce provides a very effective security model where we always start with the most restrictive access and then open up access using additional mechanisms like sharing rules, and manual sharing based on the requirements.   But there might be scenarios where we need to restrict access based on specific criteria. Salesforce recently introduced 2 approaches to support this requirement. Those are restriction rules and scoping rules. Let us see this in detail. 2. Restriction Rules - Overview Using restriction rules we can apply an additional level of filter on top of records to which a specific user is having access. 3. Scoping Rules - Overview Scoping rules help to filter the default records visible for a user based on specific criteria. But it is not preventing access to other records. 4. Compare Restriction Rules and Scoping Rules 5. Restriction Rule - Example Company ABC is having Job Applications getting created through their company portal and synched to Salesforce. T
Read more

How to develop reusable Invocable Apex methods for Flows

-
Image
 Salesforce is adding many new features and capabilities to Flows. But there are still some scenarios where you need to call apex methods from Flows to execute complex operations - when Flow is not capable of doing that or the performance will be low when you implement that using flows. Let us see how we can build reusable apex methods for Flows. For this let us consider 2 sample scenarios: Scenario 1 - Quick Create Account/Contact I want to build a screen, where the user can select the object needs to be created, and then create a record of that object by entering the required details. Also if the record creation is getting failed, I want to create an exception record with details. Solution Let us see how we can utilize Apex action for this. For this first let us create an Apex Invocable method, which can accept a list of wrapper class as shown below: You can see, this invocable method is accepting a List of wrapper class variables and also returning a list of wrapper class variables.
Read more