PDF Export
Print Print
Expand All
  • Stemmons Central User Manual
    • Overview
    • Stemmons Central User Interface
    • Home
    • Cases
    • Departments
    • Entities
      • Entities System Overview
      • Entities Stemmons Application Architecture
      • Entities System Data Architecture
      • Entities System Configuration
      • Entities System Best Practices
      • HTML Template for Entities
      • HTML Tag Body Template for Entities
      • Tag Control for view control in Entities
      • Entities Calculation Field
      • Entities - Entity Role to Employee Association
      • Entity to Entity Role Relationship
      • Entities Cases Relationship through External Datasource
      • Entities Quest Relationship via External Datasource
      • Extensible Grid in Entities
      • Subscription to Hopper-Entities
      • System Code for Entities Publishing Purpose
      • Kanban View for Entities
      • Recipe Builder
      • External Entities
      • Security Scenarios for Diffrent Users in Entities Application
      • Field Level Security for Entities
      • Entities - Entity to Entity Role Association
      • Entities Dynamic Template
      • Entities Job Aid
      • Entities Portal
      • Email to Entities
      • Entity Overlay
      • Entity Merging
      • Entity Copy
      • Entities Hopper
      • Unassign Item button in Entities
      • Entity Conversion
      • Entities Custom Query
    • Facts
    • Standards
    • Quest
    • Cast (Central Automation System)
    • Common Language Gateway (CLG) /Common Data Resource
    • External User
    • Import Tools
    • Stemmons Web API
    • Migration Tool
    • ULS (Unified Logging System) Log Viewer
    • BlockChain-Trigger
    • Blockchain Trigger API Matrix Table
    • Custom Branding
    • Stemmons Search
    • Appendices
    • Updoc
    • Passive Trigger
    • Stemmons Central Mobile Application Login Process
    • How to Configure SSO with a SAML 2.0 in Stemmons Cloud Authentication Handler
    • Stemmons Cloud Authentication Handler
    • Web Form to Cases
Entity Merging

?Entity Merging allows merging of duplicate entity items.

Entity Merging allows merging of duplicate entity items. When one entity (ie. Entity A) is merged into another entity (ie. Entity B), the related entity items (role associations and related entities) of Entity A will be moved over to the merged entity (Entity B) and Entity A will be deleted. The user will have option to update the meta data from Entity A into Entity B or just transfer the related entity item into the merged entity. Note: since this process will require Update (to merged entity B) and Delete (Entity A), the user will need Read, Update, and Delete Access to merge.

If the user has Update and Delete access to the Entity Item, Merge button will be visible on the Ribbon.

Below demonstration show there are multiple "Polo" company were set up in Entities and the user would like to merge duplicate Entity 1553 - Polo into Entity 1551 - Polo Corp.

From Entity 1553 View Page, Merge will be available on Ribbon:

Once Merge is clicked, the system will take user to the Merge screen with the following options:

1. Original Entity (in this illustration Entity 1553 - Polo) and it's meta data.
2. Option Merge and Update Info: this option will update all meta data values from Original Entity (Entity 1553) into the selected Entity on #4 in screenshot (Entity 1551 - Polo Corp.). The merge also moves all related items from 1553 to 1551.
3. Option Merge: this option will not update meta data fields in Entity 1551 but will move all related items from 1553 to 1551.
4. This grid display possible matches (potential duplicates) where Title field in original Entity (1553) is liked other Title fields within the same Entity Type. Allows the user to select the entity to merged into.

In this illustration, Merge was selected, noted, Meta data values from 1551 remains as is, however, the contact under Company 1553 - Polo was transferred over to Company 1551 - Polo Corp.

Note: After the merge, Entity 1553 is deleted.