The wizard is delivered as a guided Setup flow that takes between fifteen and forty-five minutes to run depending on data volume. Execute it in a sandbox first, validate the dashboards with the business, and then re-run in production. Below are the steps from a clean sandbox through to a deployed, validated app. The wizard expects a working Manufacturing Cloud configuration on top of CRM Analytics Plus; running it before either of those is in place creates dashboards that load but show nothing useful. The right order is licensing, permission sets, sample data, then the wizard itself, then a customization pass with the business.
- Verify prerequisites in the sandbox
Confirm Manufacturing Cloud is licensed and the running admin user has the Manufacturing Cloud Admin permission set and the CRM Analytics Plus permission. Confirm Sales Agreements, Account Forecasts, and Orders exist with realistic data. Run a sample report on Sales Agreement Products to confirm the data is queryable. If anything is missing, load test data first using the standard Data Loader or create records manually before launching the wizard.
- Launch the wizard from Setup
Navigate to Setup, search for CRM Analytics, and select Set Up CRM Analytics for Manufacturing. The wizard presents a single screen with an explanation of what will be deployed, the prerequisites it checks for, and a Start button. Click Start. The wizard begins by inspecting the org and may prompt for permission assignments if it detects missing pieces. Follow the inline prompts; the wizard logs every action it takes for later review.
- Configure dataset filters and naming
The wizard prompts for an app name, a description, and optional date or product filters that scope the deployed dashboards. For most rollouts, accept the defaults and rename only the app to match the org's naming convention. Choose whether to schedule the dataflow immediately or defer to the next day. Click Deploy and wait. The deployment usually completes in five to fifteen minutes depending on data volume; the first dataflow run after deployment is what populates the dashboards with actual numbers.
- Validate, customize, and promote to production
Once deployment finishes, open the Analytics Studio and navigate to the Manufacturing Analytics app. Walk through each dashboard with at least one sales operations stakeholder, taking notes on missing filters or columns. Clone any dashboard that needs customization and edit the clone, leaving the wizard output untouched as a baseline. After sandbox sign-off, re-run the wizard in production. The wizard is idempotent for the dataset and dataflow creation but will overwrite any wizard-named dashboards, which is why clones are the right pattern for production customization.
- The wizard does not check that source data exists. Running it against an empty Manufacturing Cloud setup produces dashboards that load successfully but show zero everywhere.
- Re-running the wizard overwrites the wizard-named dashboards. Always clone before customizing so the next run does not erase your edits.
- Default dataflow schedule is nightly. Stakeholders expecting real-time numbers need to be set straight before the first demo or expectations will not match reality.
- Row-level security is inherited from the underlying object permissions, but only if the dataflow uses the security predicate. Customized dataflows that drop the predicate accidentally expose data.
- The wizard requires CRM Analytics Plus, not the base CRM Analytics license. Orgs on the base SKU see the wizard but cannot complete deployment.