data360-schema-get
Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs. Use this skill when you need to inspect DLO or DMO field definitions, data types, or metadata. Takes org alias and optional DLO/DMO name as parameters.
By forcedotcom · 4,794 installs
npx skills add forcedotcom/sf-skills --skill data360-schema-get
Source repository · Upstream listing
data360 schema get Skill
Overview
This skill retrieves Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using the SSOT REST API. It can list all DLOs or DMOs in an org, or retrieve detailed schema for a specific DLO or DMO.
When to Use
User wants to see all DLOs or DMOs in a Data Cloud org
User needs field schema for a specific DLO or DMO
User is exploring Data Cloud data structures
User needs to understand DLO or DMO field types and metadata
Prerequisites
SF CLI installed and authenticated to target org
Org has Data Cloud enabled
User has appropriate Data Cloud permissions
Skill Execution
Parameters
1. org alias (required): The SF CLI org alias (e.g., 'afvibe', 'myorg')
2. dlo name (optional): Specific DLO developer name (e.g., 'Employee dll')
3. dmo name (optional): Specific DMO developer name (e.g., 'Individual dlm')
Step 1: Discover Connected Org
First, run sf org list to find out which org is connected and extract the alias to use for all subsequent calls:
Example output:
Extract the Alias value (e.g., myorg ) from the output and use it as the <org alias for all subsequent calls. Use all to see expired and deleted scratch orgs as well.
Step 2: Validate SF CLI Authentication
Before making API calls, verify the org is connected:
If not connected, inform user to run:
Step 3a: Execute DLO Schema Script
The Python scripts are bundled with this skill in the scripts/ subdirectory.
To list all DLOs:
To get specific DLO schema:
Step 3b: Execute DMO Schema Script
To list all DMOs:
To get specific DMO schema:
Step 4: Present Results
Parse and present the results in a user friendly format:
For DLO List:
Show DLO name, label, category, and ID
Indicate total count
Highlight DLOs with data (totalRecords 0)
For DLO Schema:
Show basic info (name, label, category, status)
List all fields with:
Field name
Data type
Primary key indicator
Nullable status
Highlight custom fields (exclude system fields like DataSource c, cdp sys )
Show record count if available
For DMO List:
Show DMO name, label, category, and ID
Indicate total count
For DMO Schema:
Show basic info (name, label, category, description)
List all fields with:
Field name
Data type
Primary key indicator
Nullable status
Show dataspace information if available
Step 5: Offer Next Steps
After displaying results, suggest relevant follow up actions:
Query data from the DLO
Create calculated insights
Build segments
Set up data streams
Create DMO mappings
API Endpoints Used
List All DLOs
Response structure:
Get DLO Schema
Response structure (same as individual object in list response, but wrapped in paginated format).
List All DMOs
Response structure:
Get DMO Schema
Response structure (same as individual object in list response, but wrapped in paginated format).
Error Handling
Common Issues:
1. Org not connected
Message: "Org not connected"
Solution: Ask user to authenticate via SF CLI
2. DLO not found
Message: "DLO 'XYZ dll' not found"
Solution: List all DLOs first to verify name
5. DMO not found
Message: "DMO 'XYZ dlm' not found"
Solution: List all DMOs first to verify name
3. Permission issues
Message: HTTP 403 errors
Solution: Verify user has Data Cloud permissions
4. API version mismatch
Current: v64.0
Solution: Script can be updated for newer API versions
Example Usage
Example 1: List all DLOs
Example 2: Get specific DLO schema
Example 3: Explore DLOs then get schema
Example 4: List all DMOs
Example 5: Get specific DMO schema
Example 6: Explore DMOs then get schema
Output Format
DLO List Output
DLO Schema Output
DMO List Output
DMO Schema Output
Notes
DLO names always end with dll suffix
DMO names always end with dlm suffix
Field names always end with c suffix
System fields (DataSource c, KQ , cdp sys ) are automatically added
Primary key fields are required for DLO and DMO queries
API supports pagination (limit/offset) for large result sets
Related Skills
datakit workflow : For DMO mapping operations
datakit validation : For validating datakit configurations
Use this skill before creating DMO mappings to understand source DLO structure