Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define best practices for manual+declarative data generation #12

Open
samanthashain opened this issue Mar 31, 2020 · 1 comment
Open
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed Ready for Sprint Can easily be worked on during an SFDO Sprint

Comments

@samanthashain
Copy link
Contributor

samanthashain commented Mar 31, 2020

If you're creating data in CSVs to migrate through DataLoader OR another ETL or CumulusCI, how should you do it in the simplest and most effective way?

Google doc in progress: https://docs.google.com/document/d/1ofzF2MHs9orse2cbRBB4gVDams4rI5FLwOmJzBt6wOQ/edit#heading=h.q53g82k908vv

@samanthashain
Copy link
Contributor Author

@csupilow to avoid being passive aggressive, following up w a post: I just "assigned" this issue to you, since I think it relates to the docs project and I want community members who browse our repo to know who to contact. Let me know if that doesn't seem right and I'll course correct!

@samanthashain samanthashain added the help wanted Extra attention is needed label May 18, 2020
@acrosman acrosman added documentation Improvements or additions to documentation Ready for Sprint Can easily be worked on during an SFDO Sprint and removed use case labels Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed Ready for Sprint Can easily be worked on during an SFDO Sprint
Projects
None yet
Development

No branches or pull requests

3 participants