ProjectChangeOrder — data reference
All 16 fields BSuit stores for ProjectChangeOrder (Projects), with the record types they refer to.
On this page
#About ProjectChangeOrder
ProjectChangeOrder is a record type in the Projects area of BSuit. This page lists everything BSuit stores for each projectchangeorder — 16 fields. No dedicated page for it was found in the menu; records may be created by other screens, imports or automatic processes.
#Fields
Every field stored for a projectchangeorder. “Stored as” is the technical field name, useful when talking to support or building reports.
| Field | Stored as | Type | Required | Max length | Refers to |
|---|---|---|---|---|---|
| Project Id | ProjectId | Text | No | — | — |
| Code | Code | Text | No | — | — |
| Title | Title | Text | No | — | — |
| Description | Description | Text | No | — | — |
| Status | Status | Text | No | — | — |
| Cost Impact | CostImpact | Number (decimal) | No | — | — |
| Schedule Impact Days | ScheduleImpactDays | Whole number | No | — | — |
| Requested By | RequestedBy | Text | No | — | — |
| Approved By | ApprovedBy | Text | No | — | — |
| Request Date | RequestDate | Date | No | — | — |
| Decision Date | DecisionDate | Date | No | — | — |
| Project | Project | Text | No | — | — |
| Id | Id | Text | No | — | — |
| Created At | CreatedAt | Date and time | No | — | — |
| Updated At | UpdatedAt | Date and time | No | — | — |
| Is Deleted | IsDeleted | Yes / No | No | — | — |
#Who can do this
Super Admin and other superuser accounts can always see and do everything, regardless of this list. For everyone else, these are the standard roles that have been granted a permission here in this system’s current setup — an organisation can add, remove or customise roles and their permissions, so treat this as an example, not a guarantee.
| Role | Create | Edit | View |
|---|---|---|---|
| PM Finance Approver | Yes | Yes | Yes |
#About this guide
Generated from BSuit’s data model on the date shown under “Seen on a running system”. Field names, types and lengths come from the model itself. References are inferred from field names (a field called “Ledger Id” is treated as pointing to Ledger); the model does not declare relationships, so an inferred link can occasionally be wrong or missing.
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Administrators, analysts and support staff
- Owner
- BSuit documentation team
- Reviewer
- Not yet reviewed
- Last verified
- Never
- Checked against
- Generated from source revision a36c7a086 on 2026-10-02
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:data/project.projectchangeorder