Project identities and data
How to treat Infrenta project identity and status when exchanging data with another system of record.
A project is the root object other records hang from: estimates, layouts, procurement packages, budgets, and execution records.
Integration intent
Typical project-level needs:
- map an Infrenta project to an ERP job number
- read status or health signals
- keep names and identifiers aligned
What is not published here
This site does not document a public list/create/update project REST interface. Those operations exist inside the authenticated product. External access, when granted, is defined in the implementation package for that customer.
Practical guidance
- Use a stable external job identifier in both systems.
- Treat the Infrenta project as the engineering/commercial system of record for solar delivery data, or explicitly choose another system of record — do not silently dual-write.
- Sync against issued state, not against in-progress drafts, unless the integration is specifically a drafting tool.