- Overview
- Platform setup and administration
- Platform setup and administration
- Platform architecture
- Data Bridge onboarding overview
- Connecting a Peak-managed data lake
- Connecting a customer-managed data lake
- Creating an AWS IAM role for Data Bridge
- Connecting a Snowflake data warehouse
- Connecting a Redshift data warehouse (public connectivity)
- Connecting a Redshift data warehouse (private connectivity)
- Reauthorizing a Snowflake OAuth connection
- Using Snowflake with Peak
- SQL Explorer overview
- Roles and permissions
- User management
- Inventory management solution
- Commercial pricing solution
- Merchandising solution
Supply Chain & Retail Solutions user guide
The Projects dataset contains project-level metadata used in commercial pricing scenarios. It defines project entities that may be associated with quotes, pricing decisions, or sales transactions.
This dataset is required for application deployment and pricing insights analysis.
→ For the canonical technical schema (data types, validation rules, request/response examples), see Project in the API Guide.
Purpose
The commercial pricing solution uses the Projects dataset to:
- Associate quotes and sales transactions with specific projects
- Enable project-level pricing analysis
- Support segmentation and reporting based on project context
In project-driven pricing environments, this dataset ensures pricing behavior can be evaluated within the appropriate business context.
Required fields
About the Nullable column: every field below must appear in your data. Nullable: Yes means the field can be sent as null (or left blank in your source) when no value is available; Nullable: No means a non-null value is required for every row.
| Field | Description | Type | Nullable |
|---|---|---|---|
project_id | Unique identifier for each project. | string | No |
project_name | Name of the project. | string | No |
project_category | Category assigned to the project. | string | Yes |
project_subcategory | Sub-category assigned to the project. | string | Yes |
updated_at | Timestamp when the record was updated. | timestamp_tz | Yes |
Usage notes
- Every project referenced in the Quote Line or Sales datasets must exist in the Projects dataset.
- Project identifiers must be consistent across all related datasets.
- Categorization fields improve segmentation-based pricing strategies.
- The
updated_atfield supports incremental data synchronization.
Why this dataset matters
The Projects dataset allows the pricing solution to evaluate pricing behavior in environments where quotes and sales are tied to specific projects. Without it, project-level pricing insights and segmentation would not be possible.