In This Section
- Concepts
- Data
- Build
- The App Composer
- The Page Index
- Context
- Pages
- Models
- Components
- Best Practices
- Debugging Skuid in the Console
- Logic
- Style
- Deploy
- Extend
- Reference
- The Property Library
- API Reference
- skuid.debug
- skuid.runtime
- skuid.$
- skuid.actions
- skuid.ajax
- skuid.builder.core
- skuid.builder.core.coreProps
- skuid.calendar
- skuid.collaboration
- skuid.component
- skuid.componentType
- skuid.events
- skuid.formula
- skuid.hotkeys
- skuid.label
- skuid.lightning
- skuid.load
- skuid.model
- skuid.model.Model
- skuid.mustache
- skuid.page
- skuid.sfdc
- skuid.snippet
- skuid.time
- skuid.utils
- skuid.version
- Component-Specific APIs
- Skuid Model Metadata Object
- Skuid Model Child Relationship Metadata Object
- Skuid Model Condition Metadata Object
- Skuid Model Field Metadata Object
- Skuid Model Record Type Metadata Object
- Page XML API
- skuid-sfdx
- skuid CLI
- Skuid Metadata Object Reference
- Skuid Glossary
- Formula and Function Reference
- Open Source Software Attributions
- Site Administration
- Tutorials
- Legal terms and conditions
- Skuid for Salesforce Evaluation Guide
In This Topic
Object Relationships?¶
In Skuid, there is no intermediate layer between object data and what end users will see on a page. Because of this, builders can create data relationships between objects without worrying if they can get it in a single screen.
Skuid models read object metadata to provide access to parent-child relationships and reference fields. A builder can configure a model to bring in data from parent-child relationships and from reference fields. Field renderers and templates on data components provide a builder with multiple options for displaying parent-child and reference field data. For example, field renderers on data components provide the option to display reference fields as hyperlinks.