Overview
Code files are the building blocks of project structure in Dash360. A code file is a named list of codes — either a flat list or a hierarchical tree — that gets assigned to one or more projects. Every WBS hierarchy, work package numbering scheme, activity code set, and basis code list in the system is a code file.
Before you can create a project, you need code files for at least the WBS structure and work packages. Administrators create and manage code files here, then assign them to projects in Project Settings.
Permissions
Administrator role required.
Code File Types
Dash360 uses code files for several purposes:
| Type | What It Defines |
|---|
| WBS Code File | The Work Breakdown Structure hierarchy (hierarchical, with separator character) |
| Work Package Code File | Work package identifiers within each WBS element |
| Activity Code File | Activity codes for schedule integration |
| Basis Code File | Estimating basis codes (Analogy, Parametric, Engineering, etc.) |
Code File Fields
| Field | Description | Required |
|---|
| Name | Unique name for the code file | Yes |
| Description | Optional description | No |
| Hierarchical | Whether codes have a parent-child tree structure (WBS) or are a flat list | Yes |
| Separator | The character used to delimit hierarchy levels (e.g., . produces codes like 1.2.3) | If hierarchical |
Managing Code Files
Creating a Code File
- Click Add Code File.
- Set the name, toggle hierarchical if needed, and set the separator for hierarchical files.
- Save. The file is created empty — add codes next.
Copying a Code File
Use Copy to duplicate an entire code file with all its codes and hierarchy. This is useful when a new project needs a structure similar to an existing one with minor changes.
Deleting a Code File
Deleting a code file removes all codes within it and all references to it from projects and cost estimates.
Before deleting a code file, Dash360 checks which projects and records reference it. If any cost estimates, resource assignments, or projects use this code file, deletion will cascade and remove those references. Review the impact list before confirming.
Managing Codes
Within a code file, add individual codes using the Add Code button. For hierarchical files, codes can be nested under parent codes.
Code Fields
| Field | Description | Required |
|---|
| Code | The code value (e.g., 1.2.3 or WP-001) | Yes |
| Description | Human-readable label for this code | Yes |
| Parent | For hierarchical files, the parent code this code belongs under | If hierarchical |
Reordering Codes
Drag rows to reorder codes within the same level, or use Save Sort Order to commit the new sequence. Use Reset Order to restore alphabetical/default ordering.
Bulk Operations
- Update Multiple — Edit several code descriptions at once
- Delete Multiple — Remove a set of codes in one operation
Code Linking
Code files can be linked to other code files to establish relationships. For example, a WBS code file can be linked to a work package code file so that work packages are associated with specific WBS elements. This linking is configured on the code file and determines what cross-references are available in cost estimates.
Code History
Every change to a code or code file is tracked. Click History on any code to see a full audit trail of additions, edits, and deletions with timestamps and the user who made each change.
Shared Code Files
A single code file can be assigned to multiple projects. When you modify a code in a shared file — adding, editing, or deleting a code — the change affects every project using that file. The sharing status is shown on the Projects page.
If you need to modify codes for one project without affecting others, copy the code file first to create a project-specific version, then reassign the project to use the copy.
