Uninstalling Sliick Forms

Read this before you click Uninstall, because Salesforce will not let you until four things are undone. Every step here reverses something the setup asked you to do, and Salesforce reports each blocker by naming a package internal rather than the setup step behind it.

Uninstalling deletes your data

Uninstalling deletes every form, every published version, every staged response, and every saved set of partial answers. They are records on the package’s own objects, and removing a package takes its objects with it. Nothing survives that you can re-import later unless you export it first.

Salesforce offers to keep a copy of the package’s data for 48 hours afterwards. Take it, but do not rely on it: it expires, and it is a raw export rather than something you can feed back in.

Export first

Form structure: one blueprint per form. Open each form, open the Share tab with nothing selected on the canvas, and click Download blueprint. Keep the files outside the org. See Blueprints and moving forms between orgs.

Responses: CSV from the console. Open Sliick Responses, clear the filters, tick Include test if you want test rows, and click Export CSV. The export stops at 2000 rows without saying so, while the count above the table keeps showing the true total, so if those disagree, narrow the date range and export in slices.

Uploaded files stay. Files a respondent uploaded are ordinary Salesforce files and are not removed. What goes is the marker that records which form each file arrived through, so export that alongside the files if the provenance matters to you.

Three things a blueprint does not carry, because they describe where this org placed the form rather than the form itself: whether Allow on your public Sliick Edge address was ticked, any per-form Share URL, and the form’s folder. Record them by hand. A note in a spreadsheet is enough, and nothing else will reconstruct them.

Reconnecting Sliick Edge after a reinstall is a full reconnection, not a toggle, and your public address may not come back the same. Treat any published link or printed QR code pointing at it as at risk across an uninstall and reinstall, not merely paused.

The four things to reverse, in order

1. Remove the form component from every Experience page, and publish the site. Delete every Sliick Experience Form component from every page, including template regions and pages you do not think of as form pages. The publish is a required part of this step, not housekeeping: a site keeps a live version and a builder version of every page, and removing the component updates only the builder one. That is why Salesforce reports the component twice, once for each. If the site is going away too, deleting it removes both references at once.

2. Delete the guest sharing rule. Setup, Sharing Settings, Form Definition, and delete the criteria-based guest rule. While it exists, Salesforce refuses the uninstall with a separate error for each field the rule names. Editing the rule to drop one criterion is not enough: delete the rule.

3. Unassign Sliick Forms Submitter from the site’s guest user. This is the assignment that blocks, reported as the permission set being assigned to one or more users. Remove it from any authenticated submitters and integration users holding it as well.

4. Unassign the remaining packaged permission sets. Sliick Forms Admin, Sliick Forms User and Sliick Forms Integration, the same way. This is a precaution rather than a measured blocker, and it clears a whole class of error before it can appear. If you are also removing a dedicated integration user, deactivate it after unassigning, not before.

Then uninstall: Setup, Installed Packages, Sliick Forms, Uninstall. Choose whether to keep the 48-hour data copy, confirm, and wait for Salesforce to email you.

If it still refuses, the error list names what is left. Anything not above is a customisation of your own: a report, list view, flow, validation rule, formula field or code that references a packaged object or field. Remove the reference, not the package’s component.

Disconnect Sliick Edge first if you ever connected it. It has not been seen to block an uninstall, but the Disconnect button lives in the package and is gone once the package is.

Reading the refusal

What Salesforce reports	What caused it	Reversed by
Is Active and Was Published on Form Definition, in use in a criteria-based sharing rule	The guest sharing rule	Step 2
Sliick Forms Submitter, assigned to one or more users	The Submitter assignment on the site’s guest user	Step 3
Sliick Experience Form, used elsewhere, publish the community before uninstalling, reported twice	The component on an Experience page	Step 1

Uninstall checklist

• A blueprint downloaded for every form and saved outside the org
• Responses exported to CSV, with the row count matching the console’s total
• Placement recorded by hand: which forms were on your public address, any per-form Share URLs, and each form’s folder
• Sliick Edge disconnected, if it was ever connected
• Sliick Experience Form removed from every Experience page, and the site published
• The guest sharing rule on Form Definition deleted
• Sliick Forms Submitter unassigned from the site’s guest user and from any other holder
• The other packaged permission sets unassigned
• Your own reports, list views, flows and code no longer reference the package
• Uninstalled, with the 48-hour data copy taken if you want it