Design the shape of your own records. Add the fields you actually use to any module you have turned on, arrange them, relate them to each other, calculate them — and decide, deliberately, which of them are allowed on your public site.
Design the shape of your own records. Add the fields you actually use to any module you have turned on, relate records to each other, calculate and roll them up — and decide, deliberately, which of them are allowed on your public site.
What's included
Add fields to any active module: text, number, currency, date, picklist, checkbox, geolocation and more
Relate modules to each other — a field on one record that points at a record in another, stored as a reference, never a copy
Calculated fields and roll-up summaries that total, count or average the records linked to this one
Validation rules with your own error message, and per-role rules for who can see and edit each field
Rearrange fields and group them under your own section headers — built-in fields included
Fields are private by default; publishing one to your public site is an explicit, separate decision
Let Wally propose a field set from a spreadsheet, a connected Salesforce object, or a screenshot — you review every field before anything is created
About this module
Data Design lives at /data-design and is the admin surface for shaping every module your org runs. Add custom fields to any active module — text, number, currency, date, picklist, checkbox, geolocation, and more — then rearrange them and group them under your own section headers, built-in fields included, so a record looks the way your team thinks.
It goes past plain fields into real data modeling. Lookup fields relate one module to another as a reference — never a copied value — with a defined behavior when the referenced record is deleted. Formula fields calculate from other fields, and roll-up fields count, sum, or average the child records that point at a record. Validation rules carry your own inline error message, and per-role rules decide who can see and edit each field.
Publishing is a separate, deliberate act. Fields are private by default; putting one on your public site is an explicit decision, not a side effect. And Wally can propose a whole field set from a spreadsheet, a connected record, or a screenshot — but you review every field before anything is created.
What you can do with it
Add the custom fields you actually use to any module you have on
Relate two modules with a lookup that references a record, never copies it
Calculate a formula field, or roll up child records into a total
Set per-role visibility and a custom validation message on a field
Publish a chosen field to your public site as an explicit decision
Get this module
Free for all Turtini organizations.
Who it's for
- Org admins who need records shaped to their real workflow
- Teams relating and calculating data across modules without code
- Anyone who wants control over what internal data ever reaches the public site
Details
- Category
- Operations
- Pricing
- Free
- Built by
- Badge
- New