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
Is Skuid limited to one sObject or Record Type per page?¶
No. Skuid runs in user context - respecting the Salesforce security model. This means that builders or end users can use or view any object data permitted by the security model.
Similarly, Skuid can pull multiple Record Types into the same model, and display them in the same component.
Skuid respects record type dependencies for Salesforce data elements like dependent picklists, but is not limited by page layouts.