Define a Property Set library and link custom properties to Trimble Connect model objects
domain: developer.trimble.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Complete the Trimble Connect Get Started access steps to obtain API credentials
Create a Property Set Library and one or more Property Set Definitions specifying property names and data types
Set access control policies on the library (read/write/no-access) for the relevant users
Create Property Set instances from a definition and identify target model objects by their GUIDs
Link each Property Set instance to its model object, using FRN-style reference notation for the link
If the properties must be visible inside Trimble Connect apps (not just standalone), follow the documented ecosystem-specific API and access-policy conventions
Known gotchas
Skipping the special Trimble Connect ecosystem conventions means property sets won't appear in Connect apps even though the API call succeeds
A valid Trimble Connect license is required to use property sets inside Connect applications
Property set schemas and instances are versioned — every edit creates a new version, so 'latest' isn't always what you last wrote
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?