Explore Aurelia sales leads

The fictional Aurelia Utilities 1.0.0 sample in Trazadera Golden installs a second entity, sample-lead-entity, alongside the customer master. Its 108 synthetic leads come from a marketing JSON file. The website, partner tablet, and call centre capture different fields, so a missing value often means that channel never asked for it. Complete Install Aurelia first, then use an administrator account to inspect the unmodified sample.

1. Compare the source and stored records

In Administration → Settings → Sample projects, select Download files and open data/marketing-leads.json in the archive. Then open the lead entity’s Records page. Its cleaning pipeline normalizes values it can recognize before storage, including phone numbers, URLs, and coordinates.

Inspect a lead’s name, address, country, and phone in both places. The name and address columns declare Catalan, Spanish, and Galician as source languages. The country column stores Spanish common names: for example, the incoming Spain becomes España. A national phone can use the record’s country to obtain its international form. The pipeline cannot invent an absent field or repair an unrecognizable language or malformed URL.

2. Read the leads’ quality picture

Open Quality in the lead entity and select its installation picture. A clean installation measures 108 records at an average of 60.7, with four error findings and 1,231 warning findings. These are occurrences, not counts of distinct affected leads. The customer entity’s average, 96.91, is not a target for leads: each lead channel supplies only part of the lead dataset.

Inspect LEAD-0010, whose incoming language is castellano, and LEAD-0011, whose landing page has no URL scheme. Those values remain errors after cleaning. Compare the record’s findings with the source JSON before deciding whether to repair the source or change a rule.

3. Inspect candidate groups

Open Duplicates for the lead entity. The initial installation has 15 candidate groups: five found by by-email, ten by by-full-name, and none by the exact by-tax-id mapping. The email mapping permits one typo; the full name mapping permits two, including names entered in a different word order.

Open a group and compare its individual records. Approximate matching can intentionally put two different people together for review. A group does not authorize a merge; read the classification and field evidence first. The sample deliberately includes two different leads named Ana Gil and Eva Gil whose names are close enough to form a candidate group, but who must not be merged automatically.

4. Understand access across the two entities

An administrator can inspect both entities. A new STEWARD or VIEWER has no Aurelia access until an administrator grants it. The customer entity uses province as its scope column; the lead entity uses salesZone.

A steward granted northern provinces and the NORTE sales zone sees only those rows. A candidate group can include another member outside the grant: Golden identifies that member as out of scope, and a merge returns 409. Escalate the case for an administrator instead. A viewer granted the lead entity but not the customer entity can inspect leads without gaining customer access.

Before applying grants in any environment, read each entity’s current access list. Saving an entity’s access list replaces that complete list. See Roles and permissions for the grant model, and Review duplicates for the customer exercise.

Verify the result

You should now see 108 lead records, an installation quality picture averaging 60.7, and 15 candidate groups in the lead entity. You should also be able to distinguish its salesZone access scope from the customer entity’s province scope. If the counts differ, confirm that you are viewing a clean installation and its initial picture.

Related reading

• Follow a customer record
• Read quality results
• Review duplicate candidates