A recipe is quick to start and easy to leave half-finished in a way that quietly produces wrong numbers. Get the inputs and the schedule right first.
- Open Data Manager
From Analytics Studio, open Data Manager. Synced data, recipes and datasets all live here, including recipes a templated app created for you.
- Add your Input nodes
Add an Input node per source: a synced Salesforce object, connected external data, or a dataset an earlier recipe produced.
- Chain the transforms
Drop join, filter, aggregate and formula nodes between input and output. Watch the preview row count after each one. A join that silently multiplies rows shows up here first.
- Point the Output node somewhere
Choose a new or existing dataset, or send the result on to Data Cloud. Name it something a dashboard builder will recognize in six months.
- Run once, then schedule
Run it manually and check the row count against the source. Then schedule it to start after data sync finishes.
One Input node per source: synced object, connected data, or an existing dataset.
A new or existing CRM Analytics dataset, or Data Cloud.
Manual, a recurring schedule, or a start from the Salesforce CLI.
Templated apps only. CreateOnly, CreateExecute, or CreateSyncExecute (the default).
- Nothing in the product is labeled Preparation Recipe. Data Manager and the docs say recipe, and the metadata type is WaveRecipe. Search for those instead.
- Deleting a WaveRecipe through destructiveChanges.xml also removes the related WaveDataflow components, so do not declare both.
- R2 and R3 are not the same editing experience. If a documented node option is missing, check the format field before opening a support case.
