SFDO-Tooling/Snowfakery

Join tables that do not have duplicates

prescod opened this issue · 2 comments

For example, avoid assigning the same Contact to the same Campaign through Campaign Member.

Avoid assigning the same Contact to the same Program multiple times through ProgramEngagement.

Simple cases could probably implement by materializing a randomized set for the parent object and then pulling items from the set. If the set would be too big, that's a challenge. E.g. a random contact out of millions. Maybe a hard upper limit will satisfy 90% of all cases with limited coding complexity.

Solved by #684