Which of these is a supported use case for Heroku Connect?

Connectors for Data Integration -Archive and Consolidate Salesforce Data

Learning Objectives 

In the wake of finishing this unit, you’ll have the option to:

Perceive which apparatuses are useful to help to combine organizations.

Pinpoint when a filing technique is important.

Retaining, Archiving, and Accessing Data

Regardless of whether you’re utilizing Sales Cloud, Service Cloud, Marketing Cloud, or you’ve constructed associated applications, a significant measure of data is probably going to be produced and driven into your organization at some random time. This presents a few difficulties. Data is gold, and erasing it very well may be impossible because of its worth. In the event that you’ve at any point experienced cases like these, executing a filing system might be advantageous.

The measure of data in your organization is causing horrible showing, moderate detailing, or record locking.

Data maintenance approaches aren’t being met.

Worldwide development requests for detailing and new element organizations aren’t being met.

Data stockpiling is a worry because records that are put away yet are not effectively being used.

There are a few different ways data the board on the Salesforce Platform can be controlled. An extraordinary method to archive your data is to use Heroku Connect. We should take a gander at a use case to give you a superior comprehension of how to use Heroku Connect when you’re prepared to archive data inside your own solution design.

Use Case: Retaining, Tracking, and Managing Data

An enormous retail client needs to archive old data to let loose space in their organization, and still have the option to hold that data with the choice to unarchive it for as long as 7 years. To determine these business challenges, Robert Bullard, from getting Cloudy Consulting, suggests utilizing Heroku Connect, Postgres, and Salesforce Connect.

Solution design for data chronicling utilizing Heroku Connect, Salesforce Connect, and Postgres.

Inside this design, there are three sections that are completely prepared inside Heroku. The first is web administration. The web administration gives endpoints to Salesforce to call for documenting and unarchiving records. These web benefits additionally uncover tasks that can be performed on the Heroku Connect Tables. The data is then added to a line so it turns into an async interaction.

The subsequent segment is the Postgres database. A laborer running behind the scenes considers a bunch of put-away methodologies that interact all the administration of records between the archive tables and the Heroku Connect tables that are life.


Moving the data between the archive tables and the interface tables is just about as straightforward as utilizing INSERT and DELETE. Yet, in case you’re keen on adding your own rationale, you can use DML tasks.

The third part is overseen by the Heroku add-on, Heroku Connect. In this segment, there are two sections, the outside objects, and the sync motor. The outer articles help to uncover data in the archive table by an OData endpoint which can be devoured by Salesforce Connect and thusly uncovered the data back to Salesforce as an outside object. The subsequent part, the Heroku Connect sync motor, does the bidirectional synchronizes between the live Heroku Connect tables inside Postgres and the Salesforce organization.

A) Which of these is a supported use case for Heroku Connect?

  • I) Setting up bidirectional sync between multiple Salesforce orgs and Heroku Postgres
  • II) Updating data in Salesforce Account object when a new record is created in an associated account table in Postgres
  • III) Getting pricing and product information in real time from an external system where product details are stored
  • IV) A and B
  • V) B and C

B) Which scenario would benefit from implementing an archive strategy?

check answers

Related Posts:

This article is taken with the help of Trailhead Salesforce 

Recommended Programming Language

Leave a Comment

Your email address will not be published. Required fields are marked *