Using Salesforce Inspector Reloaded in Practifi

Learning Team

Overview

Salesforce Inspector Reloaded is an open-source browser extension that helps you manage data in Practifi more efficiently. While Salesforce does not officially support this tool, it's maintained by an active development team. It provides powerful capabilities for data inspection, editing, bulk processing, and integration monitoring that go beyond what's available in the standard Practifi interface.

This extension is particularly valuable for System Administrators who need to troubleshoot issues, perform bulk data updates, inspect field-level details, monitor integration health, or quickly query specific information without navigating through multiple screens. By learning to use Salesforce Inspector Reloaded effectively, you can significantly reduce the time spent on data management tasks and gain deeper visibility into your Practifi organization's data and integrations.

This guide walks you through installation, key features, and best practices for using Salesforce Inspector Reloaded to work with data in Practifi.

Before You Begin
Installation and Setup
- Microsoft Edge Installation
- Google Chrome Installation
Using Key Features
Best Practices
Troubleshooting

Before You Begin

Before using Salesforce Inspector Reloaded, ensure you have the following:

Salesforce Inspector Reloaded installed
System Administrator permissions in Practifi (required to access and modify data)
A supported browser, either Google Chrome or Microsoft Edge

Understanding your permissions is critical because Salesforce Inspector Reloaded operates within the same permission framework as your Practifi user profile. If you cannot edit a field or view certain records in the standard interface, you will encounter the same limitations when using this extension.

Installation and Setup

To use Salesforce Inspector Reloaded, you must first install the extension in your browser. The installation process varies slightly depending on whether you use Microsoft Edge or Google Chrome. Instructions for both browsers are provided in the following sections.

Microsoft Edge Installation

In Microsoft Edge, click the Extensions icon, located to the right of your browser address bar.
- Please note: If you do not see the Extensions icon to the right of your browser address bar, select Settings and more > Extensions.
Select Get Extensions for Microsoft Edge from the drop-down menu.
In Microsoft Edge Add-ons, search for and open the listing page for Salesforce Inspector Reloaded.
Click the Get button on the listing page.
When prompted to grant permissions by the extension, carefully review the permissions, then click Add extension if you'd like to proceed.
You'll see a final prompt confirming the extension has been added, and a new tab will open displaying information about Salesforce Inspector Reloaded.
Open Practifi in your browser. Once you are logged into your organization, use the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I) to open the Salesforce Inspector Reloaded menu.

Google Chrome Installation

Open the Chrome Web Store in Google Chrome.
Search for and open the listing page for Salesforce Inspector Reloaded.
Click Add to Chrome.
When prompted to grant permissions by the extension, carefully review the permissions, then click Add extension if you'd like to proceed.
You'll see a final prompt confirming the extension has been added, and a new tab will open displaying information about Salesforce Inspector Reloaded.
Open Practifi in your browser. Once you are logged into your organization, use the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I) to open the Salesforce Inspector Reloaded menu.

Using Key Features

Salesforce Inspector Reloaded provides several powerful features for working with data in Practifi. The following sections explain how to use each key feature to accomplish common data management tasks.

Inspect Records

The inspect feature lets you view all fields and their values for any record in Practifi, including system fields and hidden fields that may not be visible in the standard interface. This complete field-level visibility is especially useful when troubleshooting issues, verifying data accuracy, or understanding how records are configured at a technical level.

To inspect a record:

Navigate to a record in your organization that you would like to inspect (e.g., Contact, Account, Task).
Use the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I) to open the Salesforce Inspector Reloaded menu.
You'll be able to view general information about the record within the menu, including the date it was created and the last time it was edited. Select the Show all data option to open a page displaying all fields and the values entered for the record.

Editing Records

The editing feature provides a quick way to modify field values directly without navigating through the standard Practifi interface. This is especially useful when you need to update system fields or make quick corrections to multiple fields on a single record, saving time that would otherwise be spent navigating screen by screen.

To edit a record:

Navigate to a record in your organization that you would like to edit (e.g., Contact, Account, Task).
Use the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I) to open the Salesforce Inspector Reloaded menu.
Select the Show all data option to open a page displaying all fields and the values entered for the record.
Double-click into the Value field for the field you would like to edit and enter or modify the information.
Click Save at the bottom of the page to finalize your changes.

Exporting Data

Exporting data through Salesforce Inspector Reloaded provides greater flexibility than standard Practifi list views. You can write custom SOQL (Salesforce Object Query Language) queries to extract exactly the data you need, including fields from related objects, and export the results in multiple formats, giving you precise control over what gets exported and how.

Please note: For simple exports from list views in Practifi, use the Export as CSV option available on record tables. For additional information about this option, consult our Using Pages article. Use Salesforce Inspector Reloaded when you need more control over which fields to export or when querying across related objects.

To export data using Salesforce Inspector Reloaded:

In Practifi, open Salesforce Inspector Reloaded using the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I).
Click the Data Export option.
Create your SOQL query in the Export Query box. For example, SELECT Id, Name FROM Account.
Click Run Export.
The results will display in the Export Result box below. You can then either copy and paste the information into Excel or select the download option to download the information as a CSV file locally.

Viewing Integration Logs

Integration logs provide critical visibility into communication between Practifi and external systems such as Envestnet, Black Diamond, or custom integrations. Monitoring these logs helps you troubleshoot integration issues, verify that data is syncing correctly, and understand when and why errors occur, so you can resolve problems before they affect your team's work.

Salesforce Inspector Reloaded makes it easy to query and review integration logs. You can save commonly used log queries and run them quickly whenever you need to check integration health or diagnose issues.

To view integration logs using Salesforce Inspector Reloaded:

In Practifi, open Salesforce Inspector Reloaded using the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I).
Click the Data Export option.
In the Export Query box, enter the following query to retrieve all integration logs:
```
SELECT Id, practifi__External_System__c, practifi__Response_Body__c, practifi__Response_Code__c, practifi__Direction__c, practifi__Error_Message__c, CreatedDate FROM practifi__Integration_Log__c ORDER BY CreatedDate DESC
```
This query retrieves integration log records with key fields:
- practifi__External_System__c: Identifies which external system the log relates to (such as Microsoft 365, Envestnet, or Black Diamond)
- practifi__Response_Body__c: Contains the detailed response received from the external system (often empty for error records but may contain XML, JSON, or HTML responses for certain integration types)
- practifi__Response_Code__c: Shows the HTTP status code when available (200 for success, 500 for server errors; frequently empty for many error types)
- practifi__Direction__c: Indicates whether the integration was sending data to (Outbound) or receiving data from (Inbound) the external system
- practifi__Error_Message__c: Displays error messages when the integration encounters issues (this is the primary field for troubleshooting)
- CreatedDate: Shows when the log entry was created, helping you identify recent issues

You can also add a line to the query to filter by a specific integration source (replace 'Black Diamond' with your integration name):

SELECT Id, practifi__External_System__c, practifi__Error_Message__c, practifi__Response_Code__c, CreatedDate 
FROM practifi__Integration_Log__c 
WHERE practifi__External_System__c = 'Black Diamond' 
ORDER BY CreatedDate DESC

Please note: For many error records, the practifi__Response_Code__c and practifi__Response_Body__c fields are often empty. The practifi__Error_Message__c field is your primary source of information when diagnosing integration failures. Error message formats vary by integration type and may include JSON objects, exception strings, or detailed error descriptions.

Click Run Export.
Review the results in the Export Result box. Focus on the practifi__Error_Message__c column to identify issues.

Pro tip: Click the Save Query button after entering your query. This allows you to quickly access it later without having to retype it. Name your saved query descriptively, such as "All Integration Logs" or "Black Diamond Errors Only."

Understanding Common Error Message Patterns

Integration log error messages appear in different formats depending on the integration type and the error. Recognizing these patterns helps you diagnose issues more quickly:

Configuration errors: Messages like "The callout couldn't access the endpoint. You might not have the required permissions, or the named credential might not exist" indicate that the integration's authentication or connection settings need attention. Check your named credentials in Setup.
Data sync errors: Messages containing "Entity does not exist" or "Client id not found" mean the integration is trying to sync a record that doesn't exist in the external system. This often occurs after records are deleted in one system but not the other.
Duplicate value errors: Messages starting with "System.DmlException: Insert failed" and mentioning "DUPLICATE_VALUE" indicate the integration is attempting to create a record that already exists. Review your External ID field mappings to resolve these conflicts.
Calendar sync errors: Messages like "No linked calendars" or "RecallCalendarSyncException" indicate issues with calendar integration settings. Verify that users have properly connected their calendars in Practifi.
Deployment errors: Integration logs with External_System__c set to DEPLOYMENT contain XML SOAP fault messages related to metadata deployments or configuration updates. These typically appear in both the Response_Body__c and Error_Message__c fields and require administrator attention.

Benefits of Monitoring Integration Logs

Proactive issue detection: Identify integration failures before users report problems by regularly reviewing error logs.
Faster troubleshooting: Access detailed error messages that explain exactly what went wrong, reducing time spent diagnosing issues.
Integration health monitoring: Establish a weekly routine to check logs or review integration configuration changes to ensure ongoing sync reliability.
Support documentation: Export log data to share with Practifi Support or integration vendors when requesting assistance, including specific error details and timestamps.
Pattern recognition: Reviewing logs over time helps you identify recurring issues that may indicate broader configuration problems requiring systematic fixes.

Bulk Editing with CSV Import

Bulk editing via CSV import lets you efficiently make mass changes to records in your organization. This is valuable when you need to update dozens or hundreds of records at once, such as correcting data after a migration, updating fields across multiple accounts, or making batch corrections, without opening each record individually.

Salesforce Inspector Reloaded supports importing a CSV file to create new records, update existing records, or delete records in bulk. Understanding the different import actions and following best practices will help ensure successful bulk operations.

To perform an import through Salesforce Inspector Reloaded:

Prepare a CSV file or use a CSV template available in our Using Data Upload Templates article. Ensure that your CSV includes all required fields and information (e.g., ID for updates).
In Practifi, open Salesforce Inspector Reloaded using the keyboard shortcut (Ctrl + Shift + I) or (Cmd + Shift + I).
Scroll down and click the Data Import option.
In the new window that appears, click the radio button labeled CSV in the Format options.
Select the action you would like to perform from the Action drop-down menu. The options are as follows:
- Insert (create new records): Used to create new records in your organization. You will need to provide the data for the new record. If successful, a new record is created with a unique ID.
- Update (modify existing records): Used to modify existing records in your organization. You will need to specify the ID of the record you want to update and provide new values for the fields you want to change.
- Upsert (insert or update based on a key): A combination of insert and update. This action checks whether a record exists based on a specified key (ID or External ID). If a matching record exists, it updates the record. If no match is found, it inserts a new record. This action is useful when you are unsure whether a record exists and want to prevent duplicates.
- Delete (remove records): Used to remove records from your organization. You need to specify the ID of the records you wish to delete. Deleted records are moved to the Recycle Bin, where they can be temporarily recovered, depending on how many records are sent at a time. We recommend using extreme caution with this action and performing a data backup before deleting to minimize risk.
- Undelete (recover deleted records): Recovers records that were deleted, provided they are still available in the Recycle Bin. Records that have been permanently deleted from the Recycle Bin cannot be recovered through this action.
From your formatted CSV file, copy your information and paste it into the Data field.
- Please note: We recommend adding a batch record ID to your information. Adding a batch record ID will enable easy identification and removal of potential errors. For additional details about batch record IDs, consult our Understanding and Using Batches article.
Complete field mapping in the Field Mapping window to ensure that each column in your CSV is correctly assigned to the corresponding field in Practifi.
Once your information is ready, select the Run button to perform your action. You will be able to see the action in progress, with the system indicating how many records have succeeded or failed.

Please note: Large import operations may take several minutes to complete. Do not close the browser window or navigate away from the page while the import is processing, as this may interrupt the operation.

Best Practices

When using Salesforce Inspector Reloaded, there are several best practices to keep in mind that will help you work more efficiently and avoid common mistakes:

Use keyboard shortcuts
- To access Salesforce Inspector Reloaded quickly, use either (Ctrl + Shift + I) or (Cmd + Shift + I).
Use Excel for editing
- Export your data and then edit it in Excel. After you make your edits, save the changes and re-import the file using Salesforce Inspector Reloaded. This approach supports efficient bulk updates and makes it easier to manage formatting and catch errors before importing.
Include batch record ID
- When importing information into your organization, add a batch record ID. Adding a batch record ID to your information will allow for easy removal of potential mistakes. For additional details about batch record IDs, consult our Understanding and Using Batches article.
Verify field permissions
- To perform a successful query using Salesforce Inspector Reloaded, you must have permission to the fields included in the query. Confirm field access before running a query, or use it to diagnose access issues after a failure.
Test with small batches
- Before performing large imports, test with a small batch first. A successful small batch confirms your formatting and field mapping are correct before you commit to the full import. If it fails, it's easier to identify and correct errors at a smaller scale.

Troubleshooting

The following guidance addresses common issues you may encounter when using Salesforce Inspector Reloaded.

If the extension is not loading:
- Ensure the browser extension settings are configured correctly and that you are working within a supported browser, either Google Chrome or Microsoft Edge. If the extension continues to load improperly, uninstalling and reinstalling it may resolve the issue.
If you are encountering permission errors:
- Confirm that your Practifi profile has edit access within your organization and that the sharing rules within your organization do not restrict edit access. Salesforce Inspector Reloaded operates within your existing permission framework, so any field or record you cannot edit in Practifi will also be inaccessible through the extension.
If you are encountering import failures:
- Validate the formatting of your CSV file and ensure that all required fields are present. Incorrect formatting is one of the most common causes of import failures.
If you are encountering query failures:
- Verify field permissions within your organization. If your profile does not have access to a field included in your query, the query will fail. Grant the necessary permissions or remove the inaccessible field from your query to proceed.