In This Section
- Concepts
- Data
- Build
- The Composer
- Context
- Pages
- Models
- Components
- Best Practices
- Debugging Skuid in the Console
- Logic
- Style
- Deploy
- Extend
- Reference
- API Reference
- skuid.$
- skuid.actions
- skuid.ajax
- skuid.builder.core
- skuid.builder.core.coreProps
- skuid.calendar
- skuid.component
- skuid.componentType
- skuid.events
- skuid.formula
- skuid.hotkeys
- skuid.label
- skuid.load
- skuid.model
- skuid.model.Model
- skuid.mustache
- skuid.page
- skuid.sfdc
- skuid.snippet
- skuid.time
- skuid.ui
- 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 CLI
- Skuid Metadata Object Reference
- Skuid Glossary
- Formula and Function Reference
- Open Source Software Attributions
- API Reference
- Site Administration
- Tutorials
- Skuid Page Tutorials
- Add Related Lists with the Table Component
- Build an Activities Related List Tab
- Build a Custom “Create New Record” Page
- Build a Custom Detail Page
- Build a Custom List Page
- Compose a Branded Header and Navigation
- Conditionally Display Fields
- Create a Custom “Clone Account” page
- Highlight Critical Data: Wrappers, Rich Text, and Ui-Only Fields
- JavaScript Tutorials
- Skuid Page Tutorials
- Legal terms and conditions
In This Topic
Skuid Metadata Object Reference¶
Skuid sites, apps, and pages are made up of several different types of metadata objects. These metadata objects are collections of files: typically XML files for pages and JSON files for almost everything else.
The composition of these files tells Skuid the properties of each object within a Skuid site. This reference reflects the documented properties of those files.
Warning
Any undocumented properties or keys should not be edited, as they are liable to change at any time.
Warning
Skuid metadata object names must be unique and that uniqueness must be case-insensitive. This allows for better compatibility with case-insensitive file systems, like macOS. Because of this, metadata objects that only differ in capitalization will be verified against each other as matching objects.