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.

753stars278forksUpdated 7/25/2026

Data Science & ML API Development #read-only #data-cloud #schema #python #rest-api #salesforce

Security Assessment

Safe(96/100)

Security Score96/100

About data360-schema-get

This skill retrieves Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using the SSOT REST API. It solves the problem of understanding Data Cloud data structures before doing downstream work: it can list all DLOs or DMOs in an org, or return the detailed field schema — field names, data types, primary key indicators, and nullable status — for a specific object. It is fundamentally a read-only inspection tool.

The workflow discovers the connected org with sf org list, validates authentication with sf org display, and then runs bundled Python scripts (get_dlo_schema.py and get_dmo_schema.py) that call four GET endpoints under the ssot REST API for listing and retrieving DLO and DMO schemas. Results are presented in a user-friendly format that highlights objects with data and custom fields, shows record counts and dataspace information when available, and suggests relevant follow-up actions such as querying data, creating calculated insights, building segments, or setting up DMO mappings. Prerequisites are the SF CLI installed and authenticated to the target org, Python 3 with the requests and pyyaml packages, and a Data Cloud-enabled org with appropriate permissions. A troubleshooting table maps common issues (org not connected, missing modules, object not found, permission denied) to fixes.

The target users are Salesforce Data Cloud administrators, developers, and consultants who need to inspect object schemas. Use cases include exploring an unfamiliar org's DLOs and DMOs, checking field types before creating mappings, and confirming which objects hold data. Because every documented call is a GET request, the skill does not modify org data.

FAQ

What does this skill actually do?

It lists DLOs and DMOs in a Data Cloud org and retrieves detailed field schema for a specific DLO or DMO via the SSOT REST API. All documented endpoints are GET calls, so it only reads schema and metadata.

What are the prerequisites?

The SF CLI installed and authenticated to the target org, Python 3 with the requests and pyyaml packages installed, and a Data Cloud-enabled org where the user has appropriate Data Cloud permissions.

What parameters does it take?

A required org_alias (the SF CLI alias), and optionally a dlo_name (e.g. Employee__dll) or dmo_name (e.g. Individual__dlm) to fetch a specific object's schema instead of listing all objects.

How do I run the scripts directly?

Run python3 scripts/get_dlo_schema.py <org_alias> [dlo_name] to list or fetch DLO schema, and python3 scripts/get_dmo_schema.py <org_alias> [dmo_name] for DMOs. Omitting the object name lists all objects of that type.

What if an object or the org isn't found?

The troubleshooting table advises verifying the org connection with sf org login web, confirming DLO names end in __dll and DMO names in __dlm, listing all objects first, installing missing Python modules, and checking Data Cloud permissions for permission-denied errors.