Installing a report pack

Before you start

• Salesforce Professional Edition or higher.
• Log in as a user who can install packages. That's usually a System Administrator.
• Have the install link from your order email ready.
• If you have a sandbox, install there first and try it before installing in production.

Check your flows

Professional Edition allows 5 active flows of each type. The Leads & Top of Funnel pack adds 1 record-triggered flow. The other three packs add none. If your org doesn't have room, the flow will install but can't be activated.

To check, go to Setup, type Flows in Quick Find and open Flows. Look at the Process Type and Active columns and count the active flows whose type is record-triggered. Five minus that number is how many you have left.

If you don't have enough room, combining flows to fit is available as a custom project.

Install the package

Open the install link

Open the link from your order email and log in as your admin user. To install in a sandbox instead, change login.salesforce.com at the start of the link to test.salesforce.com.

Choose who to install for

Choose Install for Admins Only. You'll give everyone else access with the pack's permission set in the next section, which is easier to manage than profile-by-profile access.

Install

Click Install. Most packs finish in a minute or two. If Salesforce says the install is taking longer, you'll get an email when it's done.

Confirm it installed

Go to Setup › Installed Packages and check that the pack is listed.

Give your team access

Assign the permission set

Each pack includes a permission set that lets users see its fields. Go to Setup › Permission Sets, open the pack's permission set, click Manage Assignments, then Add Assignment. Select everyone who should see the pack's reports, click Next and then Assign.

Share the folders

Each pack installs its reports in one folder and its dashboard in another. In the Reports tab, open All Folders, click the arrow next to the pack's report folder and choose Share. Share it with the groups, roles or users who need it, with View access. Do the same for the dashboard folder in the Dashboards tab.

Rep-Level Personal reports

Each pack includes Rep-Level Personal reports. Their names start with “My,” such as My Open Pipeline, and they show only the records owned by whoever is viewing them. They live in the same folder as the team reports, so sharing the folder is all reps need.

Email subscriptions

Reps can have a report emailed to them on a schedule. Open the report, click Subscribe, set how often, and save. You can add a condition so the email only sends when the report has at least one record.

Each rep needs to subscribe themselves. When an admin subscribes someone else, the report runs as the admin, so the rep sees the admin's records, not their own. Salesforce allows each user 7 report subscriptions (15 on Unlimited Edition).

Dashboards

A dashboard shows data as one specific user sees it. Open the pack's dashboard, click Edit, then the gear icon for dashboard properties. Under View Dashboard As, choose a user who can see all of your team's records, such as a sales manager. Save, then click Done.

Adjust thresholds

A few reports and fields use thresholds you can change to fit your sales cycle.

Report filters

Stale Deals uses 14 days without activity and Stuck in Stage uses 30 days. Open the report, click Edit, change the number in the filter, and save. Change the matching Rep-Level Personal report too.

Customer status and renewals

Customer Status (RP) counts a customer as active for 365 days after a win. To change it, go to Setup › Object Manager › Account › Fields & Relationships, open Customer Status (RP), click Edit, change 365 in the formula and save. Renewal Date (RP) assumes annual contracts. If yours aren't annual, report on a date field you keep up yourself instead.

Loss reasons

Edit the values in the Loss Reason (RP) picklist on Opportunity to match the reasons your team actually hears.

Guardrails

Some packs install rules that keep key information filled in, and they're active from the start. To change one, go to Setup › Object Manager, open the object, then Validation Rules. Open the rule and click Edit. To switch it off, uncheck Active and save.

• Pipeline Health: open deals at 20% probability or higher need an Amount and a Next Step, and open deals can't be given a close date in the past. To move the 20% line, change 0.20 in the rule's formula.
• Win/Loss & Velocity: a loss reason is required before a deal can be closed lost.

Add Loss Reason to your opportunity page

Packages can't change your existing page layouts, so the Win/Loss & Velocity pack installs Loss Reason (RP) without putting it on any page. Add it before your team closes another deal as lost, or they'll get an error asking for a field they can't see.

Go to Setup › Object Manager › Opportunity › Page Layouts, open each layout your team uses, drag Loss Reason (RP) onto it and save. If you use Path on opportunities, also add Loss Reason (RP) as a key field on the Closed Lost step, so it's asked for at the moment a deal is lost.

Leads pack notes

Check the flow is active

Go to Setup › Flows and check that LNRP Leads Pack - First Activity Stamp shows as active. It records when each lead is first worked, and Speed to Lead depends on it. It only measures leads created after install.

Keep dead leads out of Lead Aging

Old leads that were never closed out make Lead Aging look worse than it is. Open Lead Aging by Status, click Edit, and add a filter on Lead Status that excludes your dead or recycled statuses. Save. The same filter works on My Open Leads.

About the (RP) labels

Every field a pack adds has a label ending in (RP), for “report pack.” Most orgs already have fields with ordinary names like “Customer Status,” and two fields with the same label make reports and filters confusing fast. The (RP) suffix keeps pack fields easy to spot. The API names all start with LNRP_ for the same reason.

Relabeling a field

If you'd rather not see (RP), you can change the label without breaking anything. The reports reference the API name, which doesn't change.

Go to Setup › Object Manager, open the object, then Fields & Relationships. Click the field, click Edit, change the Field Label, and save. Check that the new label doesn't match a field you already have.

Uninstalling

Go to Setup › Installed Packages and click Uninstall next to the pack. Uninstalling removes the pack's reports, dashboards, fields, rules and flows, and deletes any data stored in the pack's fields. Your own records and fields aren't touched.

Getting help

Email elijah@logicnerds.net with your org edition and a screenshot of whatever looks wrong.