Snowfakery-Recipe-Templates
Snowfakery-Recipe-Templates copied to clipboard
SFDO-Community-Sprints
Sample Snowfakery Recipe to Generate Permutations of Contacts, related Household Accounts, and Opps.
As a project developer, I need to be able to generate series of objects that are permutations of various record types and field values, and all required related objects for that base object.
When building out a membership portal, developers of the portal need to be able to test the interface with members who have all the different membership types and statuses. To do this a data set must include all the permutations of the membership object (generally a custom object), the contacts that are required for each, accounts for those contacts, and potentially other required objects.
@mkolodner I feel like you would have specific ideas about this, given the complexity of the mentorship program data model that you've built. I'm not sure what the next step is here, but I'm going through Issues to see what's actionable and I'd love your thoughts!
I modified the title here to be more specific and reflect the tooling that's been created since I first created this issue. I still want to have a clear path to do this. I know Forceea has a command in its instructions to do permutations of a list. I'm not sure if Snowfakery does currently.
@acrosman I think we're close to being able to do this, but not quite there yet. Can you share your thoughts about where we are and the next step so that curious Sprinters can get involved? So far, I know how to create all of the records in the requirements but I haven't succeeded at creating all of the permutations yet.
Permutations are a challenge still (see this issue), but working on some options would be good.
Starting with a simpler version with clear directions to get us started would be a great base line. Another helpful step would be helpful would be feedback to Paul and/or I about if there are other people that want this feature and if the proposed solutions for it make sense to others. That may help Paul determine priorities or other people work on pull requests.
@acrosman I like the membership example. Maybe we can use the Membership Schema open source project as a use case?
We could refine/replace this issue with an ask to create a recipe for generating membership data that fits that schema. Makes sense to me.
Moved this one out of Sprint Ready for 2/2021 Sprint in favor of the clearer sample recipe issues.
The intent here is a bit different than the goal of #9. Memberships, via the schema project or not, are a useful example of when a team needs a recipe that generates permutations of all options – indeed it was the need to do that which triggered the conversations that led to this project. But it's not the only example. Really any object with a picklist can create the need to have one of each in the output. For example having an opportunity in each stage can be useful, as can having a campaign member in each status.
Do you know whether this functionality is available in snowfakery at this point? If you have more direction, we might be able to include it in the advanced recipe track at the minisprint.