Category Salesforce Tips

Presenter showing two illustrative New Jersey solar solicitation records tied to one facility
Data Management, Salesforce Tips

How New Jersey Solar Developers Reconcile CSI Project IDs in Salesforce

by Ben

Why Can Two New Jersey CSI Project IDs Still Describe One Solar Facility?

In this anonymized composite scenario, a New Jersey solar developer imports Competitive Solar Incentive (CSI) submissions into Salesforce. A reapplication receives a new solicitation Project ID, and an integration creates a second custom Solar Project row for the same proposed facility. An illustrative 15,000-row review shows how the team separates physical-project identity from bid history, keeps genuine expansions distinct, and protects supported CRM corrections with preview, backup, bulk undo, and restore. This is not a named customer result.

Presenter showing two illustrative New Jersey solar solicitation records tied to one facility
Illustrative visual: two solicitation records can refer to one proposed solar facility.

Read More

Presenter showing an illustrative Texas service point with old and replacement electric meters
Data Management, Salesforce Tips

How Texas Electric Teams Reconcile Service Points and Meter Changes in Salesforce

by Ben

Why Does a Texas Meter Change Require Careful Salesforce Service-Point Cleanup?

In this anonymized composite scenario, a Texas electric team imports service-point and meter-exchange feeds into Salesforce. One electric service identifier (ESI ID) appears twice as a customer service location after a meter replacement, while the old and new physical meters must retain separate installation histories. An illustrative 15,000-row review shows how admins repair approved CRM links, validate reports, and protect supported bulk changes with preview, backup, bulk undo, and restore. This is not a named customer result.

Presenter showing an illustrative Texas service point with old and replacement electric meters
Illustrative visual: one Texas service point can have a meter change without becoming a new service point.

Read More

Presenter showing an illustrative California EV charging site and port map
Data Management, Salesforce Tips

How California EV Charging Teams Reconcile Station and Port Assets in Salesforce

by Ben

Why Must California EV Charging Teams Keep Station and Port Assets Distinct?

In this anonymized composite scenario, a California charging operator imports site, charger, port, and connector records into Salesforce. Two feeds create duplicate-looking port Assets, while a station-level service Case is attached to the wrong child Asset. An illustrative 15,000-row review shows how the team checks physical identifiers, repairs approved relationships, and protects supported field changes with preview, backup, bulk undo, and restore. This is not a named customer result.

Presenter showing an illustrative California EV charging site and port map
Illustrative visual: distinguish a charging site from its individual charging ports.

Read More

Presenter beside illustrative carrier and registry appointment feeds in a Pennsylvania office
Data Management, Salesforce Tips

How Pennsylvania Insurance Teams Reconcile Producer Appointments in Salesforce

by Ben

Why Do Pennsylvania Insurers Need Producer Appointment Rows to Match the Right Carrier and Event?

In this anonymized composite scenario, a Pennsylvania insurer imports producer appointments from a carrier operations file and a registry-status feed into Salesforce. Name variants and missing source keys create two CRM rows for one appointment, while a later reappointment for the same producer must remain separate. An illustrative 15,000-row review shows how the team verifies producer, insurer, and event identity, previews approved ZaapIT changes, and protects supported bulk updates with backup, bulk undo, and restore. This is not a named customer result.

Presenter beside illustrative carrier and registry appointment feeds in a Pennsylvania office
Illustrative visual: carrier and registry feeds need event-level appointment reconciliation.

Read More

Presenter beside illustrative branch and online mortgage intake streams in a Charlotte office
Data Management, Salesforce Tips

How North Carolina Mortgage Teams Resolve Duplicate Salesforce Application Intake

by Ben

Why Must North Carolina Mortgage Teams Separate Duplicate CRM Intake from Separate Applications?

In this anonymized composite scenario, a North Carolina mortgage team receives one application through an online portal and a branch handoff, creating two Salesforce intake records for the same submitted application. A second application from the same borrower must remain separate. An illustrative 15,000-record review shows how admins verify application identity with source IDs, preview approved corrections in ZaapIT, and protect supported bulk updates with backup, bulk undo, and restore. This is not a named bank result.

Presenter beside illustrative branch and online mortgage intake streams in a Charlotte office
Illustrative visual: verify whether branch and online intake refer to one application.

Read More

Presenter beside an illustrative product, lot and source to shipment diagram in a cheese plant office
Data Management, Salesforce Tips

How Wisconsin Cheese Makers Verify Shipment-Lot Links in Salesforce

by Ben

Why Does a Shipment’s Cheese Lot Need More Than a Lot-Code Match in Wisconsin?

In this anonymized composite scenario, a Wisconsin soft-cheese manufacturer imports ERP shipment lines into Salesforce. Two production sources use the same short local lot-code string for different cheese shipments, and a lot-only lookup links some distributor lines to the wrong traceability lot. An illustrative 15,000-line review shows how the team can verify product, lot, and source together, preview approved ZaapIT corrections, and retain backup, bulk undo, and restore for supported updates. This is not a named customer result.

Presenter beside an illustrative product, lot and source to shipment diagram in a cheese plant office
Illustrative visual: a shipment-lot link needs verified product, lot and source context.

Read More

Presenter beside an illustrative clinical-trial facility and study relationship diagram
Data Management, Salesforce Tips

How Massachusetts Biotech Teams Reconcile Clinical-Trial Site Accounts in Salesforce

by Ben

Why Do Trial-Site Name Variants Matter to Massachusetts Biotech Teams?

In this anonymized composite scenario, a Massachusetts biotech sponsor imports clinical-trial facility records from a registry and two CRO feeds into Salesforce. Variant names create duplicate Site Accounts, while a broad name match risks collapsing separate campuses. An illustrative 15,000-row review shows how the team can verify each physical facility, preserve separate study-site relationships, preview approved ZaapIT corrections, and retain backup, bulk undo, and restore for supported updates. This is not a named customer result.

Presenter beside an illustrative clinical-trial facility and study relationship diagram
Illustrative visual: one verified physical facility can participate in several distinct studies.

Read More

Presenter beside an illustrative New Jersey port shipment and container milestone display
Data Management, Salesforce Tips

How New Jersey Port Teams Reconcile Shipment and Container Milestones in Salesforce

by Ben

Why Do Duplicate Gate-In Events Matter at New Jersey Ports?

In this anonymized composite scenario, a New Jersey freight-forwarding team receives the same container gate-in milestone from a terminal and a carrier feed. A Salesforce import stores both messages as separate operational events and sometimes attaches one to the wrong shipment. An illustrative 15,000-row review shows how an admin can preserve both source messages, verify one real gate-in, preview approved corrections in ZaapIT, and retain backup, bulk undo, and restore for supported updates. This is not a named customer result.

Presenter beside an illustrative New Jersey port shipment and container milestone display
Illustrative visual: the shipment, container, and gate-in event have distinct identities.

Read More

ZaapIT presenter illustrating one customer request separated into repair and billing cases
Product Features, Salesforce Tips

Split Salesforce Cases with ZaapIT: Give Each Support Issue Its Own Case

by Ben

When should a support agent split a Salesforce case?

Split a case when one customer conversation contains distinct issues that need their own owner, priority, or resolution. A generator that will not start and a disputed service invoice may arrive in the same phone call, but fixing the equipment does not settle the bill. ZaapIT’s new Split Case feature lets agents prepare a separate case, choose field values and select related records to copy or move, and optionally link the new case as a child of the original. After a successful split, agents can split the original case again for another issue or use Restore split to undo the indicated split. Here is an illustrative support scenario and a practical walkthrough using the new feature.

ZaapIT presenter illustrating one customer request separated into repair and billing cases
Illustration: give each support issue a clear case and next step.

Read More

Presenter beside an illustrative wafer lot, individual device, and quality Case diagram
Data Management, Salesforce Tips

How Arizona Chip Suppliers Reconcile Device and Lot IDs in Salesforce Quality Cases

by Ben

Why Must Arizona Chip Teams Separate Lot and Device IDs?

In this anonymized composite scenario, an Arizona semiconductor supplier receives customer quality reports through Salesforce. One import places a wafer-lot code in a device-ID field, making separate device complaints look identical while a second feed uses a device alias. An illustrative 15,000-Case review shows how the team can preserve each incident, verify the lot-to-device crosswalk, preview approved corrections in ZaapIT, and retain backup, bulk undo, and restore for supported updates.

Presenter beside an illustrative wafer lot, individual device, and quality Case diagram
Illustrative visual: a lot and an individual device have different identifiers.

Read More