Data360 Schema Get

by forcedotcome5164d94d751No license1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated yesterday

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.

Includes scriptsData & Analytics
AI-generated overview

Retrieves Salesforce Data Cloud DLO and DMO schema metadata via SSOT REST APIs using bundled Python scripts.

What it does
This skill lists Data Lake Objects (DLOs) and Data Model Objects (DMOs) in a Salesforce Data Cloud org, or fetches the detailed field schema for a specific object. It runs bundled Python scripts that call the SSOT REST API and then presents results such as field names, data types, primary key indicators, nullable status, record counts and dataspace information. It also suggests follow-up actions like querying data, creating calculated insights or building segments.
When to use it
Use it when you need to inspect which DLOs or DMOs exist in a Data Cloud org, or when you need field definitions, data types or metadata for a particular DLO or DMO. It is also useful before creating DMO mappings to understand the source DLO structure.
Requirements
Requires the Salesforce CLI (sf) installed and authenticated to the target org, Python 3.10 or later, and pip 23.0 or later. The org must have Data Cloud enabled and the user must hold appropriate Data Cloud permissions; network access to the Salesforce APIs is needed. The skill ships executable Python scripts in its scripts directory.

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:

bash
sf org list

Example output:

text
┌────┬───────┬──────────────────────────┬────────────────────┬───────────┐│    │ Alias │ Username                 │ Org Id             │ Status    │├────┼───────┼──────────────────────────┼────────────────────┼───────────┤│    │ myorg │ [email protected] │ 00DKZ00000b80NT2AY │ Connected │└────┴───────┴──────────────────────────┴────────────────────┴───────────┘

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:

bash
sf org display --target-org <org_alias> --json

If not connected, inform user to run:

bash
sf org login web --alias <org_alias>

Step 3a: Execute DLO Schema Script

The Python scripts are bundled with this skill in the scripts/ subdirectory.

To list all DLOs:

bash
python3 ./scripts/get_dlo_schema.py <org_alias>

To get specific DLO schema:

bash
python3 ./scripts/get_dlo_schema.py <org_alias> <dlo_name>

Step 3b: Execute DMO Schema Script

To list all DMOs:

bash
python3 ./scripts/get_dmo_schema.py <org_alias>

To get specific DMO schema:

bash
python3 ./scripts/get_dmo_schema.py <org_alias> <dmo_name>

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

text
GET /services/data/v64.0/ssot/data-lake-objects

Response structure:

json
{  "dataLakeObjects": [    {      "name": "Employee__dll",      "label": "Employee",      "category": "Profile",      "id": "1dlXXXXXXXXXXXXXXX",      "status": "ACTIVE",      "totalRecords": 12,      "fields": [...]    }  ],  "totalSize": 5}

Get DLO Schema

text
GET /services/data/v64.0/ssot/data-lake-objects/{dlo_name}

Response structure (same as individual object in list response, but wrapped in paginated format).

List All DMOs

text
GET /services/data/v64.0/ssot/data-model-objects

Response structure:

json
{  "dataModelObjects": [    {      "name": "Individual__dlm",      "label": "Individual",      "category": "Profile",      "id": "0dmXXXXXXXXXXXXXXX",      "fields": [...]    }  ],  "totalSize": 10}

Get DMO Schema

text
GET /services/data/v64.0/ssot/data-model-objects/{dmo_name}

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
  3. DMO not found

    • Message: "DMO 'XYZ__dlm' not found"
    • Solution: List all DMOs first to verify name
  4. Permission issues

    • Message: HTTP 403 errors
    • Solution: Verify user has Data Cloud permissions
  5. API version mismatch

    • Current: v64.0
    • Solution: Script can be updated for newer API versions

Example Usage

Example 1: List all DLOs

text
User: "Show me all DLOs in afvibe org"
Response:1. Run sf org list to discover connected org alias2. Authenticate to afvibe3. Run: python3 ./scripts/get_dlo_schema.py afvibe4. Display formatted list of DLOs

Example 2: Get specific DLO schema

text
User: "Get the schema for Employee__dll in afvibe"
Response:1. Run sf org list to discover connected org alias2. Authenticate to afvibe3. Run: python3 ./scripts/get_dlo_schema.py afvibe Employee__dll4. Display field schema with types and metadata

Example 3: Explore DLOs then get schema

text
User: "What DLOs exist in myorg and show me the schema for the Employee one"
Response:1. Run sf org list to discover connected org alias2. List all DLOs in myorg3. Identify Employee__dll4. Get detailed schema for Employee__dll5. Present both results

Example 4: List all DMOs

text
User: "Show me all DMOs in afvibe org"
Response:1. Run sf org list to discover connected org alias2. Authenticate to afvibe3. Run: python3 ./scripts/get_dmo_schema.py afvibe4. Display formatted list of DMOs

Example 5: Get specific DMO schema

text
User: "Get the schema for Individual__dlm in afvibe"
Response:1. Run sf org list to discover connected org alias2. Authenticate to afvibe3. Run: python3 ./scripts/get_dmo_schema.py afvibe Individual__dlm4. Display field schema with types and metadata

Example 6: Explore DMOs then get schema

text
User: "What DMOs exist in myorg and show me the schema for the Individual one"
Response:1. Run sf org list to discover connected org alias2. List all DMOs in myorg3. Identify Individual__dlm4. Get detailed schema for Individual__dlm5. Present both results

Output Format

DLO List Output

text
Found 5 DLOs in org 'afvibe':
1. DataCustomCodeLogs__dll   Label: DataCustomCodeLogs   Category: Engagement   Records: 233
2. Employee__dll   Label: Employee   Category: Profile   Records: 12
[...]

DLO Schema Output

yaml
DLO: Employee__dllLabel: EmployeeCategory: ProfileStatus: ACTIVERecords: 12
Custom Fields:  • id__c (Text) - Primary Key  • name__c (Text)  • position__c (Text)  • manager_id__c (Number)
System Fields:  • DataSource__c (Text)  • InternalOrganization__c (Text)  • cdp_sys_SourceVersion__c (Text)
Next steps:- Query data: SELECT * FROM Employee__dll LIMIT 10- Create segment based on position field- Set up data stream for real-time updates

DMO List Output

text
Found 10 DMOs in org 'afvibe':
1. Individual__dlm   Label: Individual   Category: Profile
2. ContactPointEmail__dlm   Label: Contact Point Email   Category: Profile
[...]

DMO Schema Output

yaml
DMO: Individual__dlmLabel: IndividualCategory: ProfileDescription: Represents an individual person
Fields:  • Id__c (Text) - Primary Key  • FirstName__c (Text)  • LastName__c (Text)  • BirthDate__c (DateTime)
Next steps:- Query data: SELECT * FROM Individual__dlm LIMIT 10- View DLO mappings to this DMO- Create calculated insights

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

Source and attribution

Source:forcedotcom/sf-skillsinskills/data360-schema-getat commite5164d9

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from forcedotcom/sf-skills

Service Itsm Teams Itservice Configure

forcedotcom

Configure the "Set Up Salesforce IT Service" checklist for Microsoft Teams Employee Service (ITSM) — the employee side, covering app enablement, marketplace install guidance, user access assignment, and Digital Experience Site selection. Use this for: 'turn on Salesforce IT Service', 'set up IT Service on Teams', 'assign Teams for Employee permission set', 'give employees access to Teams for Employee Service', 'manage user access for Teams ITSM', 'grant users the permission sets needed for Teams Employee Service', 'select a digital experience site for Teams', 'install Salesforce IT Service app on Teams', or any request to complete the IT Service half of the Teams ITSM Go page checklist (including the Manage User Access step). DO NOT TRIGGER for the base Teams Salesforce Go page toggle or Azure/Entra app setup (service-itsm-teams-configure) or for the IT Desk/fulfiller half of the checklist (service-itsm-teams-itdesk-configure).

Awaiting classification1Kupdated yesterday

Service Itsm Teams Coordinate

forcedotcom

End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the Microsoft Entra app, populate Named Credentials, configure the IT Desk and IT Service checklists, turn on Swarming, and optionally embed the Agentforce agent) in one continuous pass, stopping only at the points a human must act. Use when the user asks to set up Microsoft Teams for ITSM end to end, 'set up teams for it service', 'do the whole teams itsm setup', 'configure microsoft teams for employee service', or wants a guided Teams ITSM walkthrough. Delegates each stage to a specialized child skill while driving the sequence itself. DO NOT TRIGGER when the user asks to enable Teams alone, configure just the IT Desk or IT Service checklist alone, or enable Swarming alone — delegate directly to the specific child skill in those cases.

Awaiting classification1Kupdated yesterday

Service Itsm Teams Itdesk Configure

forcedotcom

Configure the "Set Up Salesforce IT Desk" checklist for Microsoft Teams Employee Service (ITSM) — the fulfiller/agent side, covering app enablement, marketplace install guidance, user access assignment, and Swarming collaboration-tool setup. Use this for: 'turn on Salesforce IT Desk', 'set up IT Desk on Teams', 'assign Teams for IT Desk permission set', 'set Teams as collaboration tool for swarming', 'install Salesforce IT Desk app on Teams', or any request to complete the IT Desk half of the Teams ITSM Go page checklist. DO NOT TRIGGER for the base Teams Salesforce Go page toggle or Azure/Entra app setup (service-itsm-teams-configure) or for the IT Service/employee half of the checklist (service-itsm-teams-itservice-configure).

Awaiting classification1Kupdated yesterday

Service Itsm Teams Debug

forcedotcom

Diagnoses failing Microsoft Teams for Employee Service (ITSM) setups by running pass/fail configuration checklists against a Salesforce org.

DevOps & Cloud1Kupdated yesterday

Service Itsm Teams Employee Agent Configure

forcedotcom

Configure the embedded Agentforce Employee Agent so it replies inside the Microsoft Teams ITSM custom client ('Salesforce Employee Assist' / 'Ask AI Agent'). Use this for: 'set up employee agent in Teams', 'embed Agentforce agent in Teams', 'make the IT Service Employee Agent reply in Teams', 'Teams Ask AI Agent not responding', 'agent joins then leaves without replying', 'configure MIAW deployment for Teams employee agent', 'Teams embedded messaging agent setup'. Builds the whole stack headlessly (zero Setup-UI clicks): the Web messaging channel with User Verification ON, the Enhanced Chat User Verification Key Set (JWKS_URL) it requires, the Teams_AgentForce custom-client deployment, the routing flow to the agent, and the Agent Access permission set that lets the portal user reach the agent. DO NOT TRIGGER for enabling the Teams feature Salesforce Go page toggle (service-itsm-teams-configure) or for configuring notification preferences.

Awaiting classification1Kupdated yesterday

Service Itsm Swarming Configure

forcedotcom

Enables the Salesforce Swarming ITSM feature and sets the collaboration tool to Teams via Connect API calls.

DevOps & Cloud1Kupdated yesterday