# US 11,442,952 B2 · User interface for commerce architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,442,952 B2
- Document ID: US11442952B2
- Status: Granted
- Kind: B2
- Application number: 16/264,391
- Filed: 2019-01-31
- Published: 2020-03-26
- Granted: 2022-09-13
- Earliest claimed: 2018-09-24
- Assignees: Salesforce, Inc.
- Applicants: salesforce.com, inc.
- Inventors: David Woodward; Abhinav Chadda; David Hacker; Steven Ness; Matt Lagrotte; Jason Moody; Christopher Bill; Kaustubh Barde; Lydia Lodovisi; Sarah Flamion; Jamin Hall
- Web page: https://patentgrep.com/patent/US11442952B2

## CPC

- G06F 16/252: {between a Database Management System and a front-end application}
- G06F 3/0484: for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F 16/211: {Schema design and management}
- G06F 16/212: {with details for data modelling support}
- G06F 16/2322: {using timestamps}
- G06F 16/288: {Entity relationship models}
- G06Q 10/08: Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Disclosed herein are method, system and device embodiments for setting up a graphical user interface (GUI) for a commerce architecture. An embodiment operates by providing a GUI that displays a first button for adding a first data source and a second button for adding a second data source, the second data source being related to the first data source, receiving a first response via the first button to add the first data source and a second response via the second button to add the second data source, providing a view of a first data schema and a second data schema, wherein the first data schema includes at least one object from the first or the second data source, and wherein the second data schema is a canonical data model, mapping the at least one object of the first data schema to at least one object of the second data schema, and providing a single entity view of the at least one object of the second data schema.

## Claims

### Claim 1

A method, comprising:
providing, by a computing device, a graphical user interface (GUI) comprising a first button for adding a first data source and a second button for adding a second data source, wherein the first and second data sources comprise customer records related to a common customer;
receiving, by the computing device, a first authentication permission from a user in response to adding the first data source via the first button and a second authentication permission from the user in response to adding the second data source via the second button;
providing, by the computing device, a view of a first data schema and a second data schema in the GUI, wherein the first data schema comprises at least one object displaying a first value indicating a first quantity of the customer records from the first or the second data source collapsed under the at least one object and wherein the second data schema is a canonical data model of the customer records;
mapping, by the computing device in the GUI with one or more visual logic connectors, the first quantity of the customer records in the first data schema to at least one object of the canonical data model of the customer records in the second data schema based on attribute definitions, wherein the one or more visual logic connectors display a mapping value indicating a second quantity of mapped customer records between the at least one object in the first data schema and the at least one object in the second data schema;
identifying, by the computing device in the GUI, an unmatched record in the first quantity of the customer records by a difference between the first value and the mapping value;
expanding, by the computing device in the GUI, the at least one object having the first quantity of the customer records to reveal the unmatched record; and
adding, by the computing device in the GUI, a new record corresponding to the unmatched record to the at least one object in the second data schema.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
displaying, by the computing device, a second value on the at least one object of the canonical data model to indicate a second quantity of the customer records in the at least one object.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
providing, by the computing device, a single entity view of the at least one object of the second data schema for the common customer, wherein the single entity view includes the customer records from the first and second data sources related to the common customer and the first and second data sources corresponding to the customer records.

### Claim 4 (depends on 3)

The method of claim 3, wherein providing the single entity view comprises:
transforming the at least one object of the first data schema based on a plurality of formatting rules;
determining a match between the at least one object of the customer records in the first data schema and the at least one object of the canonical data model of the customer records in the second data schema based on a plurality of matching rules; and
updating the at least one object of the canonical data model of the customer records in the second data schema as a master record of the at least one object of the first data schema based on a plurality of updating rules.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
managing, by the computing device in the GUI, the at least one object of the canonical data model of the customer records in the second data schema in response to a data management request.

### Claim 6 (depends on 5)

The method of claim 5, wherein the data management request is submitted by a requestor to manage privacy information of the common customer.

### Claim 7 (depends on 5)

The method of claim 5, wherein the data management request is submitted by a requestor to merge two customer records related to the common customer in the canonical data model into a single profile of the common customer.

### Claim 8 (depends on 1)

The method of claim 1, further comprising providing, by the computing device, a third button to add a third party data source related to the common customer.

### Claim 9 (depends on 8)

The method of claim 8, further comprising adding the third part data source through an application program interface (API).

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
displaying, by the computing device in the GUI, a mapping of a category of data sources to the common customer, wherein the category visually displaying a quantity of data sources in the category.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
displaying, by the computing device, a quantity of total customer records added from the first and the second data sources and a quantity of unique customer records for the canonical data model of the customer records.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
displaying, by the computing device, a plurality of records in response to a search request, wherein each of the plurality of records displays a corresponding data source.

### Claim 13

A system, comprising:
a memory; and
at least one processor coupled to the memory, wherein the at least one processor is configured to:
provide a graphical user interface (GUI) comprising a first button for adding a first data source and a second button for adding a second data source, wherein the first and second data sources comprise customer records related to a common customer;
receive a first authentication permission from a user in response to adding the first data source via the first button and a second authentication permission from the user in response to adding the second data source via the second button;
provide a view of a first data schema and a second data schema in the GUI, wherein the first data schema comprises at least one object displaying a first value indicating a first quantity of the customer records from the first or the second data source collapsed under the at least one object and wherein the second data schema is a canonical data model of the customer records;
map, in the GUI with one or more visual logic connectors, first quantity of the customer records in the first data schema to at least one object of the canonical data model of the customer records in the second data schema based on attribute definitions, wherein the one or more visual logic connectors display a mapping value indicating a second quantity of mapped customer records between the at least one object in the first data schema and the at least one object in the second data schema;
identify, in the GUI, an unmatched record in the first quantity of the customer records by a difference between the first value and the mapping value;
expand, in the GUI, the at least one object having the first quantity of the customer records to reveal the unmatched record; and
add, in the GUI, a new record corresponding to the unmatched record to the at least one object in the second data schema.

### Claim 14 (depends on 13)

The system of claim 13, wherein the at least one processor is further configured to:
provide a single entity view of the at least one object of the second data schema for the common customer, wherein the single entity view includes the customer records from the first and second data sources related to the common customer and the first and second data sources corresponding to the customer records.

### Claim 15 (depends on 14)

The system of claim 14, wherein to provide the single entity view, the at least one processor is configured to:
transform the at least one object of the first data schema based on a plurality of formatting rules;
determine a match between the at least one object of the customer records in the first data schema and the at least one object of the canonical data model of the customer records in the second data schema based on a plurality of matching rules; and
update the at least one object of the canonical data model of the customer records in the second data schema as a master record the at least one object of the first data schema based on a plurality of updating rules.

### Claim 16 (depends on 13)

The system of claim 13, wherein the at least one processor is further configured to:
manage, in the GUI, the at least one object of the canonical data model of the customer records in the second data schema in response to a data management request.

### Claim 17 (depends on 13)

The system of claim 13, wherein the at least one processor is further configured to provide a third button to add a third party data source related to the common customer.

### Claim 18 (depends on 17)

The system of claim 17, wherein the at least one processor is further configured to add the third party data source through an application program interface (API).

### Claim 19

A tangible non-transitory computer-readable device having instructions stored thereon that, when executed by a computing device, causes the computing device to perform operations comprising:
providing a graphical user interface (GUI) comprising a first button for adding a first data source and a second button for adding a second data source, wherein the first and second data sources comprise customer records related to a common customer;
receiving a first authentication permission from a user in response to adding the first data source via the first button and a second authentication permission from the user in response to adding the second data source via the second button;
providing a view of a first data schema and a second data schema in the GUI, wherein the first data schema comprises at least one object displaying a first value indicating a first quantity of the customer records from the first or the second data source collapsed under the at least one object, and wherein the second data schema is a canonical data model of the customer records;
mapping, in the GUI with one or more visual logic connector connectors, the first quantity of the customer records in the first data schema to at least one object of the canonical data model of the customer records in the second data schema based on attribute definitions, wherein the one or more visual logic connectors display a mapping value indicating a second quantity of mapped customer records between the at least one object in the first data schema and the at least one object in the second data schema;
identifying, in the GUI, an unmatched record in the first quantity of the customer records by a difference between the first value and the mapping value;
expanding, in the GUI, the at least one object having the first quantity of the customer records to reveal the unmatched record; and
adding, in the GUI, a new record corresponding to the unmatched record to the at least one object in the second data schema.

### Claim 20 (depends on 19)

The tangible non-transitory computer-readable device of claim 19, the operations further comprising:
providing a single entity view of the at least one object of the second data schema for the common customer, wherein the single entity view includes the customer records from the first and second data sources related to the common customer and the first and second data sources corresponding to the customer records.

### Claim 21 (depends on 19)

The tangible non-transitory computer-readable device of claim 19, wherein providing the single entity view comprises:
transforming the at least one object of the first data schema based on a plurality of formatting rules;
determining a match between the at least one object of the customer records in the first data schema and the at least one object of the canonical data model of the customer records in the second data schema based on a plurality of matching rules; and
updating the at least one object of the canonical data model of the customer records in the second data schema as a master record of the at least one object of the first data schema based on a plurality of updating rules.

### Claim 22 (depends on 19)

The tangible non-transitory computer-readable device of claim 19, the operations further comprising:
managing, in the GUI, the at least one object of the canonical data model of the customer records in the second data schema in response to a data management request.

### Claim 23 (depends on 19)

The tangible non-transitory computer-readable device of claim 19, the operations further comprising providing a third button to add a third party data source related to the common customer.