A client wants to use Heroku Connect to sync data from a Heroku Postgres table toa Salesforce org. The client only needs to sync a specific subset of the rows in the table.
How should this be performed?
Suggested Answer: B, C, D
Get Premium Salesforce Certified Heroku Architect (Plat-Arch-206) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
40 comments · newest first
EM
Emilio
11 months ago
Just to clarify, Heroku Connect does support filtering on syncs.
HE
Herschel
11 months ago
Wait, can D really restrict visibility like that? Seems odd.
LY
Lyla
12 months ago
C sounds right, using the Mapping Query Editor is super flexible.
SA
Sang
12 months ago
I think B could work too, but it seems more complicated.
RO
Rosann
1 year ago
A is the way to go for mapping filters!
GW
Gwenn
1 year ago
Sharing Rules seem more related to Salesforce permissions, so I doubt option D is the right approach for syncing data.
EN
Ena
1 year ago
I think the Mapping Query Editor is a feature we covered, so option C sounds familiar, but I’m a bit confused about the specifics.
LA
Laurene
1 year ago
I'm not entirely sure, but I feel like filtering the data in the database, like in option B, might also work.
FE
Felicitas
1 year ago
I remember we discussed using mapping filters in class, so I think option A could be the right choice.
KA
Kate
1 year ago
Ah, I see. This is all about controlling what data gets synced to Salesforce. I think option A is the cleanest solution - just set up the mapping filter and let Heroku Connect handle the rest.
JO
Jose
1 year ago
Okay, I've got this. The key here is that we only need to sync a subset of the rows, so filtering the data is the way to go. I'd go with option B and provide an alternative table or view for the sync.
AL
Alfred
1 year ago
Hmm, I'm a bit unsure about this one. I'm not super familiar with Heroku Connect, so I'll have to think it through carefully. Maybe option C with the Mapping Query Editor could work, but I'm not sure.
MA
Maryann
1 year ago
This looks like a straightforward Heroku Connect question. I think option A is the way to go - adding a mapping filter to the table sync seems like the easiest solution.
LA
Laine
1 year ago
This is an interesting question. I'll need to draw on my knowledge of JD Edwards EnterpriseOne and database middleware to figure out the correct answers.
EL
Elenora
1 year ago
I kind of want to say it's option C because that seems familiar. It would make sense that if you're trying to delete something not there, you'd get an error.
MU
Murray
1 year ago
I've got this! The key is to identify which segments meet the 10% threshold for both revenue and assets. That will tell us which ones are reportable.
ED
Edelmira
1 year ago
I'm a bit confused on this one. I'll have to think it through carefully and review the different techniques before deciding.
DA
Darrin
1 year ago
Option E: Hire a team of trained squirrels to manually sync the data. It's the most organic solution, if you ask me.
AH
Ahmed
1 year ago
Option E: Hire a team of trained squirrels to manually sync the data. It's the most organic solution, if you ask me.
HO
Hoa
1 year ago
C) Use the Heroku Connect Mapping Query Editor, and add filters to the query.
NG
Nguyet
1 year ago
A) Add a mapping filter to the table when setting up the sync, and select appropriate criteria from the list.
BE
Bernardine
1 year ago
A is the obvious choice. Heroku Connect is designed for this kind of use case, why reinvent the wheel?
DO
Dolores
1 year ago
D, really? Sharing rules for this use case? That's like using a bazooka to kill a fly. Let's keep it simple and go with B.
DA
Dacia
1 year ago
D, really? Sharing rules for this use case? That's like using a bazooka to kill a fly. Let's keep it simple and go with B.
RE
Reid
1 year ago
D) Place Sharing Rules on the records, and restrict visibility to only those rows that are needed.
AV
Avery
1 year ago
B) Filter the data in the database, and provide an alternative table or view for use in the sync.
LE
Lewis
1 year ago
B is the way to go. Filtering the data at the database level is more robust and efficient than relying on Heroku Connect's mapping features.
JU
Julianna
1 year ago
C) Use the Heroku Connect Mapping Query Editor, and add filters to the query.
JU
Junita
1 year ago
That's a good point. Filtering at the database level gives more control over the data.
JE
Jesus
1 year ago
B) Filter the data in the database, and provide an alternative table or view for use in the sync.
AL
Alease
2 years ago
Option C looks good, but I'm not sure if the Mapping Query Editor is meant for filtering data. Seems a bit hacky to me.
JO
Joesph
1 year ago
B) Filter the data in the database, and provide an alternative table or view for use in the sync.
GE
Georgene
1 year ago
I think option C is the way to go. It allows for more flexibility in filtering the data.
BO
Bobbye
1 year ago
C) Use the Heroku Connect Mapping Query Editor, and add filters to the query.
TY
Ty
1 year ago
A) Add a mapping filter to the table when setting up the sync, and select appropriate criteria from the list.
BE
Bernadine
1 year ago
C) Use the Heroku Connect Mapping Query Editor, and add filters to the query.
KI
Kimi
2 years ago
A) Add a mapping filter to the table when setting up the sync, and select appropriate criteria from the list.
DO
Dottie
2 years ago
I agree with Dottie, option C makes the most sense because it allows for specific filtering of the data being synced.
WI
Willis
2 years ago
I disagree, I believe the correct answer is A) Add a mapping filter to the table when setting up the sync, and select appropriate criteria from the list.
DO
Dottie
2 years ago
I think the answer is C) Use the Heroku Connect Mapping Query Editor, and add filters to the query.