Metadata Engine Trail — SmartLite Academy

Why this feature matters

Rina Kapoor · Operations Manager, Northwind Distributors

"We need to start tracking equipment warranties against our customer accounts. Our old CRM vendor quoted six weeks and $15,000 to add one new record type with a handful of fields. We needed it live before our next sales cycle."

In most systems, adding a new type of record means asking a developer to make the change and release an update. That turns every new idea into a request that sits in a queue for weeks.

💡

What this means for you

You can have a brand-new type of record live in minutes — no developer, no extra cost, and no risk of breaking anything. Your setup can change as fast as your business needs it to.

A closer look at the Metadata Engine

Normally, adding a new kind of record means changing the software's inner workings directly — a technical job that carries real risk of something breaking.

SmartLite works differently. It keeps track of what kinds of records and fields exist as simple settings, kept completely separate from your actual data. So adding a new record type or field never touches your real data at all. Think of it like rearranging the furniture in a room, not knocking down a wall.

Term	What it means	In plain terms
Object	Something you create, like "Warranty"	A new kind of record you want to keep track of
Field	One piece of information you add, of a chosen type	A single detail on that record — text, a number, a date, a list to pick from, a link to another record, an automatic calculation, or an auto-generated number
Formula field	Worked out fresh every time it's viewed — never permanently saved	A value the system calculates for you automatically, like labeling a customer "Enterprise" or "Standard" based on how much they've spent
Lookup field	A link to another type of record	Connects two kinds of records together, e.g. a Warranty to the Customer Account it belongs to — the related details show up automatically

✅

Good to know

Anything you build yourself — a new record type, or a new field, even one added to a built-in record type like Lead — automatically gets a small __c tag added to its behind-the-scenes name. Built-in record types and fields that came with the system don't have this tag.

To keep things fast, the system briefly remembers these settings for each company. The moment you make a change, it forgets the old version automatically, so your change shows up right away — no restart needed.

1 Build a "Warranty" record type from scratch

Open Object ManagerGo to Setup → Object Manager → New Object. (Setup is where you configure the CRM — you'll find it in the top-right menu.)

Name itType "Warranty" as the name and "Warranties" as the plural name. The system automatically creates a behind-the-scenes name (warranty__c) for you. Click Save.

Add a fieldOpen your new record type → Fields tab → New Field. Name it "Expiration Date" and choose the DATE type. Save.

Add a lookup fieldNew Field → name it "Account", choose type LOOKUP, and set the related record to Account (this links each Warranty to a customer). Save.

Create a recordGo to Records → Warranties → New. Notice that the form built itself automatically from the fields you just added — you didn't write any code.

🎯

Want to go further?

Try adding a Formula field — for example, "Days Remaining" — that automatically works out how many days are left until the warranty expires. Watch it stay up to date on every record, even though the answer itself is never saved.

Day-to-day: reps and staff

Use the new record type like any otherOnce an admin builds it, Warranty behaves exactly like a built-in record — searchable, listable, linkable to other records.

Day-to-day: admins

Add another record type whenever a need comes upRepeat the same build for the next new idea — no developer request, no waiting.

Add a field to an existing record typeSame Fields tab, same New Field button — works on built-in record types like Lead or Opportunity too.

🎯

What to try next

Look at the Advanced Metadata trail to add validation rules and custom layouts on top of what you just built.

Test what you learned

1. What small tag gets added to the behind-the-scenes name of anything you create yourself?

_std

__c

No tag — everything looks the same

2. Where does a Formula field's answer get saved?

Saved with the record, and updated every time it's saved

Nowhere — it's worked out fresh every time you view the record

In a separate memory area just for formulas

Metadata Engine: Add New Record Types Yourself — No Developer Needed

Why this feature matters

A closer look at the Metadata Engine

1 Build a "Warranty" record type from scratch

Day-to-day: reps and staff

Day-to-day: admins

Test what you learned

Badge Earned: Data Model Architect