[P2] PCC v2 project record missing salesforce_id — no cross-reference between UUID and Salesforce ID

[seberslinux]

Summary

The PCC v2 API project record does not expose a salesforce_id field. PCC uses Salesforce IDs (e.g. a0941000002wBz9AAE) in projectadmin URLs, but the v2 API returns only UUIDs (e.g. 451efe4e-9322-4b58-97f5-c8e57b5b99f4). There is no cross-reference field on the record.

Impact

Callers that need to correlate PCC v2 project data with Salesforce-based systems (or lens queries that use Salesforce IDs) must round-trip through lens to resolve the mapping. This is:

• An extra network call per project
• Unreliable given the lens IN-list bug (see related issue)
• A barrier to building reliable automation

Example

projectadmin URL:  /project/a0941000002wBz9AAE/...
v2 API response:   { "uid": "451efe4e-9322-4b58-97f5-c8e57b5b99f4", ... }
                   ← no salesforce_id field

Location

PCC v2 · GET /projects/{uid} · search_projects response schema

Severity

P2 — missing cross-reference forces unreliable workarounds

Suggested fix

Add salesforce_id (or equivalent external ID field) to the v2 project response schema. Even a nullable field would allow callers to skip the lens round-trip when the value is present.

---

Reported by Stephan Ebers — found while building NPS survey automation against the LFX APIs.

[emsearcy]

This is intentional: the v2 UUIDs are expected to replace the v1 LFX Project IDs as the new "external ID field". The v1 IDs are a mix of legacy Salesforce identifiers and lf-prefix stand-ins for Salesforce identifiers. This inconsistency (sometimes the LFX v1 ID is the same as the Salesforce ID, sometimes not) creates subtle bugs and makes agentic development harder. As platforms migrate to v2, they'll be expected to adopt the v2 UUIDs as foreign keys. Of course, we also have slugs as a unique, (nearly) immutable field, which also helps bridge the compatibility gap.

In the medium term, we'll need to ensure that the v2 UUIDs are also ingested into our data lake, so we can begin presenting those as an alternative, and eventually, primary, identifier.