Back To Documentation

Troubleshooting

Problems by symptom. If yours is not here, contact support@getfirmworks.com and see how to grant support access.

• Enhanced Upload hangs on “Awaiting Registration”
• “API is disabled for this User”
• “FirmWorks Notes License Was Not Found”
• “FirmWorks File Events Is Not Enabled”
• Download Files opens several tabs or nothing downloads
• “Unable to parse the URL parameters correctly”
• “Dynamic Field Values: Invalid Fields Detected”
• A saved configuration does not appear on components
• Users cannot see files they expect
• Previews are blurry or missing
• Picklist values are missing for a record type
• “Contents too large to display”
• The Select Files to… button is missing
• Dashboard says page dependency data is unavailable or did not answer
• Component Tools shows “Access required”
• A flow fails after Component Tools replaced its screen components
• Upgrading from a version before 0.15

Enhanced Upload hangs on “Awaiting Registration”

Symptom. Choosing Enhanced Upload shows “Awaiting Registration” indefinitely.

Cause. Clickjack protection for Visualforce pages is enabled. Enhanced Upload embeds a Visualforce page from your org’s Visualforce domain inside the Lightning page, and clickjack protection blocks that unless the Lightning domain is trusted.

Fix. Add your Lightning domain as a trusted domain for inline frames.

1. Setup > Session Settings > Trusted Domains for Inline Frames > Add Domain.

   

2. Enter your Lightning domain, for example https://yourdomain.lightning.force.com, and choose Visualforce pages as the frame type. To find the exact value, run this in the Developer Console’s Execute Anonymous window:

   System.debug('https://' + DomainCreator.getLightningHostname());
   

   

3. Repeat for each Experience Cloud site domain where Enhanced Upload is used.

“API is disabled for this User”

Symptom. The Browser Viewer or Enhanced Upload shows an error containing API_CURRENTLY_DISABLED or “API is disabled for this User”.

Cause. Both features call Salesforce APIs from the browser and need the user to have API Enabled.

Fix. Grant API Enabled on the user’s profile or a permission set. For Experience Cloud users, weigh this against your security policy; standard upload and Salesforce’s own previews work without it.

“FirmWorks Notes License Was Not Found”

Symptom. The Note Manager tab or FirmWorks Notes component shows this message instead of the notes explorer.

Cause. The FirmWorks Notes license feature is not enabled for your org, or the user has no package license.

Fix. Check the user has a license under Installed Packages > FirmWorks Files > Manage Licenses. If licensed users still see the message, contact support@getfirmworks.com to enable FirmWorks Notes. See Permissions and Licensing.

“FirmWorks File Events Is Not Enabled”

Symptom. The Configurator’s File Events tab shows “FirmWorks File Events Is Not Enabled! Please Contact FirmWorks to Enable this Feature”, or flows on the file events never fire.

Cause. Either the File Platform Events license feature is off for the org, or the events are off. All events are off after installation.

Fix. Contact support@getfirmworks.com if the tab shows the message. Otherwise open the File Events tab, turn on the events you need and click Save on each card. See File Events.

Download Files opens several tabs or nothing downloads

Symptom. Download Files opens more than one browser tab, or a dialog of links appears, or nothing happens.

Cause. Files are requested in batches of 800 and each batch is a separate download in a new tab. Browsers often block more than one pop-up.

Fix. Use the links in the dialog to start any download the browser blocked, or allow pop-ups for your Salesforce domain. On phones and tablets, Salesforce may ask you to log in again in the browser before the download starts.

“Unable to parse the URL parameters correctly”

Symptom. Opening a File Manager link shows this message and File Manager loads without the intended files or search.

Cause. A c__contentIds, c__search or c__reportBuilder parameter is malformed. Content Ids must be 15 or 18 characters and start with 068 or 069. The other two parameters are encoded by File Manager and should not be edited by hand.

Fix. Regenerate the link with File Manager’s Launch Last Search link or fix the Ids. See URL parameters.

“Dynamic Field Values: Invalid Fields Detected”

Symptom. File Tagger or File Tagger Button shows this error on a flow screen.

Cause. The JSON passed to Dynamic Field Values is malformed or names a field that does not exist on Content Version.

Fix. See the Dynamic Field Values troubleshooting section, which includes a script to check your JSON.

A saved configuration does not appear on components

Symptom. You saved a configuration but it is not in a component’s Configuration: Name picklist, or a component still shows the old settings.

Causes and fixes.

• The deployment has not finished. Check the status badge in the Configurator footer, or Setup > Deployment Status.
• The configuration is inactive. Turn the Active toggle on and save.
• Lightning App Builder caches the picklist. Reload the builder.
• A default-by-name configuration is not matching. Names are case sensitive: Account for record pages, account for Experience Cloud. See Configuration naming.

Users cannot see files they expect

Symptom. A search returns fewer files than the user believes exist.

Causes and fixes.

• File Manager only returns files the user can see. Check the file’s Content Document Links and their share type and visibility. See File Sharing and Access Explained.
• The configuration has a Default Filter or Exclude File Types setting. A warning icon in the search panel indicates a fixed filter.
• Administrators who need to see every file in the org need the Query All Files permission. See Permission Set to Query All Files.

Previews are blurry or missing

Symptom. A PDF or document preview is low quality or does not render.

Fix. Use Show In Browser’s Viewer from the file’s menu, which renders the actual file rather than Salesforce’s generated image. Or ask an administrator to regenerate the preview. See Salesforce Images Low Quality Render.

Picklist values are missing for a record type

Symptom. A picklist on the upload or tagging screen shows no values, or the wrong values, for files with a record type.

Cause. Record-type-specific picklist values are not readable by Apex. The package caches them and the cache is out of date.

Fix. A user with the Configurator permission set opens /apex/firmworks__RecordTypeFetcher and clicks Query Values And Save To Custom Metadata. See Record types on Content Version.

“Contents too large to display”

Symptom. A text file, note or Outlook message shows this message instead of its content.

Cause. Text and message previews are read into the browser and are limited to 2 MB.

Fix. Download the file. See Supported File Types.

The Select Files to… button is missing

Symptom. File Manager has no Select Files to… button, or the Bulk actions pane says “No bulk actions are enabled for this configuration.”

Cause. No bulk action is enabled in the configuration the component uses. The button appears only when at least one of Download Files, Download Data, Create Public Links, Delete Public Links or the four Allow Bulk settings is on.

Fix. Open the configuration in the Configurator, go to Step 11: Actions, and turn on the actions you want. See Enabling bulk actions.

Dashboard says page dependency data is unavailable or did not answer

Symptom. The Lightning Pages With FirmWorks Components tile shows “Page dependency data is unavailable in this org” or “The page dependency query did not answer”. Other tiles load.

Cause. The tile reads page metadata through the Tooling API and Salesforce’s Dependency API, which is a beta feature that may be off in the org, and the query is given 30 seconds. The user also needs API Enabled.

Fix. Click Refresh. If the message persists, the rest of the dashboard is still accurate; only the page inventory is affected. Component Tools falls back to scanning pages one by one when the Dependency API is unavailable.

Component Tools shows “Access required”

Symptom. The Component Tools tab lists missing permissions instead of the inventory, or the dashboard’s Migrate Aura Component Tools tile will not open.

Cause. The user lacks one of: the FirmWorks Files Component Tools permission set, View Setup and Configuration, Customize Application, or API Enabled.

Fix. Assign what is listed. A permission set assigned during the current session takes effect at the next login. See Prerequisites.

A flow fails after Component Tools replaced its screen components

Symptom. A flow replaced by Component Tools shows a new draft version but a screen does not render, or a later element cannot find an output.

Cause. Component Tools creates a new flow version rather than editing the active one. The new version is a draft unless Activate new flow versions was ticked, and a placement marked Needs review had a typed value that the LWC does not accept.

Fix. Open the flow in Flow Builder, check the screen components’ settings against the Component Reference, and activate the version. Use the row’s Undo in Component Tools if you are still on the page, or activate the previous version in Setup. See Component Tools.

Upgrading from a version before 0.15

The June 2022 release (0.15) changed the File Tagger component. If the upgrade fails with the error below, remove the component uses it names, install, then recreate them.

1. Remove the Aura File Tagger Button For Upload from page layouts and Experience Cloud pages. Republish any sites you changed.
2. Remove the Aura File Tagger from page layouts. Keep a note of the settings so you can recreate them.
3. Remove and delete any custom actions that reference the FileTaxonomy component.
4. Install the new version, then recreate what you removed.