Project Details Upload
The Project Details upload allows you to bulk create projects and programs or bulk edit the meta-data of existing projects and programs using an excel upload.
Navigate to the Financial Administration page from the drop down menu under your Avatar.
The Project Details Upload and Download functionality can be found in the Project Upload and Reporting section of the page.
Only users with Financial Administrator and Data Administrator permissioning on their account can download and upload project details. Users with only Financial Administrator role only can download the project details file but cannot upload it.
Project Details upload rules
The Project Details Upload functionality can be used to create new projects / programs or update the properties and meta-data of existing projects.
You can find a detailed description of the Project Details file format at the bottom of this page but the following rules need to be applied in order to successfully create or update project data.
Creating a project
The upload functionality makes it very easy to create new projects in bulk.
The project name (column D) must be specified in order to create a new project.
The ProjectID (column A) and ProjectGuid (column B) fields must be left blank to indicate that the project does not exist yet.
If a project external reference is specified, this external reference must not be used by any other project.
Updating a project
The upload functionality can also be used to update the properties of existing project.
To update existing projects, it is recommended to download the Project Details file, make the necessary changes in the excel file and upload the amended file.
The project name (column D) must be specified for a row to be processed. If no project title is found, the upload process will stop and will not process any more rows.
Either the ProjectID (A) or ProjectGuid (B) columns must have a value to uniquely identify the project to be updated:
If the ProjectId column has a value, then the process will search for a project with the specified project ID. If no project is found, then the row will be skipped.
If the row has no ProjectID value but a ProjectGuid value is specified, then the upload process will search for a project with the given GUID. If no project is found, then the row will be skipped.
If no ProjectId and ProjectGUID are specified but the ProjectRef column has a value, then the process will search for a project with the given external reference. If no project is found, then a new project will be created and the external reference of this new project will be set to the value specified in the excel file.
Note that if the row has no value set for ProjectID, ProjectGuid and ProjectRef, then it means that this is a new project.
It is important to note that the file being uploaded does not need to contain the entire project set. Only the projects listed in the upload file will be updated, all other projects will remain unchanged.
Data File Column Description
Column & Title | Description | Data Type | What happens if the field is left blank when uploading the file? |
A. ProjectId | The project unique ID in Fluid. This value is set by the system when a new project is created and is used to uniquely identify the project. This field should therefore be left blank when creating a new project. | Number | If Project GUID value (column B) is blank too and there are no projects in the database matching the ProjectRef value, then it means that this is a new project record. |
B. ProjectGuid | Fluid Global Unique Identifier for the project. This value is set by the system when a new project is created and is used to uniquely identify the project. This field should therefore be left blank when creating a new project. | Text | If Project ID value (column A) is blank too and there are no projects in the database matching the ProjectRef value, then it means that this is a new project record. |
C. ProjectRef | The project external reference. Unlike Project ID and Project GUID that are assigned by the application, you can set your own unique identifier for the project. | Text | If ProjectId and ProjectGuid values (column A and B) are blank, then a new project will be created and Fluid will default the project reference value to the project ID. |
D. Project Name | The project name or title. | Text | This field is mandatory. If left blank, the upload process will stop. |
E. Shortcode | Allows you to stipulate your own preferred prefix for unique identifiers that are assigned to the projects content - i.e. risks, issues, schedule tasks, etc. | Text | Fluid will derive a unique Short Code from the project title. |
F. Methodology | The methodology the project is executing in. The methodologies available are configured by your system administrator. | Text | If the project type is set to Program, then the Methodology field is set to Program. Otherwise the property is not set. |
G. Project Type | The type of executing project - e.g. standard project, small enhancement, RTB or CTB... The options available for this field are configured by the system administrator. | Text | The property is not set. |
H. Cap Eligibility | Is the project eligible for capitalisation. | Yes/No | The Cap eligibility is defaulted to No. |
I. Cap Profile | The profile under which the project will be capitalised. The capitilisation profiles available are configurable by your system administrator. | Text | The property is not set. |
J. Start Date | The commencement date or start date of the project. | Date | The property is not set. |
K. End Date | Project completion or termination date. | Date | The property is not set. |
L. Project Implementation Date | The date the project 'Goes Live'. | Date | The property is not set. |
M. Discretionary vs Non-discretionary | Discretionary: Projects that are nice-to-have. Non-discretionary: Projects that have to happen - typically projects that are compliance/governance or key to the ongoing concern of the organisation. | Text | The property is not set. |
N. Amortisation Period | The period (in months) over which the project will be amortised. | Text | The property is not set. |
O. Category | Field for further categorising the project (e.g. Support Services, Infrastructure, Business, etc). The options available for this field are configured by the system administrator. | Text | The property is not set. |
P. FundingSource | The funding 'pot' that the project is being financed from. The options available for this field are configured by the system administrator. | Text | The property is not set. |
Q. Status | The Status of the project within its lifecycle (e.g. Pipeline, Active, On-Hold, Cancelled, etc). The options available for this field are configured by the system administrator. | Text | Field is set to the default project status configured by the system administrator. This default value is usually set to Active. |
R. Immediate Parent | The immediate parent for the project in the Project Hierarchy. | Text | This column is for information only and is not processed on upload. |
S. Immediate Parent Id | The unique ID of the immediate parent project. | Text | If Immediate Parent Ref value is blank too, then the project does not have a parent project. |
T. Immediate Parent Ref | The external reference of the Immediate Parent. | Text | If Immediate Parent Id value is blank too, then the project does not have a parent project. |
U. Top Parent Project | The Top Parent project for the project in the Project Hierarchy. | Text | This column is for information only and is not processed on upload. |
V. Top Parent Project ID | The unique ID of the Top Parent project. | Text | Fluid use the Immediate Parent ID (S) or Immediate Parent Ref (T) values to determine if the project is part of a hierarchy and if it is, the ID of the top parent project in the hierarchy will be set. |
W. Top Parent Project Ref | The external reference for the Top Parent Project. | Alphanumeric (numbers & text) | Fluid use the Immediate Parent ID (S) or Immediate Parent Ref (T) values to determine if the project is part of a hierarchy and if it is, the external reference of the top parent project in the hierarchy will be set. |
X. Program | The name of the program the project belongs to. | Text | This column is for information only and is not processed on upload. |
Y. Program ID | The unique ID of the program the project belongs to. | Number | Fluid use the Immediate Parent ID (S) or Immediate Parent Ref (T) values to determine if the project is part of a hierarchy and if it is, the ID of the program the project belongs to will be set. |
Z. Program Ref | The external reference for the Program. | Text | Fluid use the Immediate Parent ID (S) or Immediate Parent Ref (T) values to determine if the project is part of a hierarchy and if it is, the external reference of the program the project belongs to will be set. |
AA. ReportingProgram | The Reporting Program the project is linked to. | Text | This column is for information only and is not processed on upload. |
AB. Reporting Program Id | The unique ID of the reporting program the project belongs to. | Number | If Reporting Program Ref (AC) value is blank too, then the project does not have a reporting program. |
AC. Reporting Program Ref | The external reference of the Reporting Program the project belongs to. | Number | If Reporting Program Id value is blank too, then the project does not have a reporting program. |
AD. Primary PM | The project manager responsible for the project. | Name | This column is for information only and is not processed on upload. |
AE. Primary PM Id | Unique identifier for the Primary PM's account - the account username. | Text | The property is not set. |
AF. Owner | The owner of the project. | Name | This column is for information only and is not processed on upload. |
AG. Owner Id | The unique identifier for the Owner account - the account username. | Text | The property is not set. |
AH. Executive | The executive responsible for the project and delivery of its benefits. | Name | This column is for information only and is not processed on upload. |
AI. Executive Id | The unique identifier for the Executive account - the account username. | Text | The property is not set. |
AJ. Editors | Along with the Primary PM, Editors have full READ/WRITE access to the project. | Name | This column is for information only and is not processed on upload. |
AK. Editors Id | The unique identifier for the Editors account - the account username. | Text | The property is not set. |
AL. Business Owner | Person from business working with the delivery team to ensure business objectives are met. | Name | This column is for information only and is not processed on upload. |
AM. Business Owner Id | The unique identifier for the Business Owner account - the account username. | Text | The property is not set. |
AN. Portfolio | The Portfolio the project belongs to. Available portfolios are configured by your system administrator. | Text | The property is not set. |
AO. SubPortfolio | The Sub Portfolio the project belongs to. Available sub portfolios are configured by your system administrator. | Text | The property is not set. |
AP. Business Driver | Which of the organisations business drivers is the project aligned to. | Text | The property is not set. |
AQ. Tier | The tiering of the project. Typically Tier 1 are the most complex/important/expensive projects and Tier 5 the least complex/important/expensive. The business rules assigned to tiering is unique to each organisation. | Text | The property is not set. |
AR. Cost Centre | The cost centre for recharge of project costs. | Text | The property is not set. |
AS. Description | Description of what the project is about. | Text | The property is not set. |
AT. Requirements | Project requirements. | Text | The property is not set. |
AU. Proposed Solution | Proposed solution of what the project will deliver. | Text | The property is not set. |
AV. Progress | The percentage completion/progress of a project. | Number | Fluid will set the value as it is derived from either the project's start and end dates (if the project does not have a schedule) or schedule task % complete values (if the project has a schedule). |
AW. Phase1End | The end date for the first phase of the project. The number of phase end dates to populate depends on the methodology selected for the project. | Date | The property is not set. |
AX. Phase2End | The end date for the second phase of the project. The number of phase end dates to populate depends on the methodology selected for the project. | Date | The property is not set. |
AY. Phase3End | The end date for the third phase of the project. The number of phase end dates to populate depends on the methodology selected for the project. | Date | The property is not set. |
AZ. Phase4End | The end date for the fourth phase of the project. The number of phase end dates to populate depends on the methodology selected for the project. | Date | The property is not set. |
BA. Phase5End | The end date for the fifth phase of the project. The number of phase end dates to populate depends on the methodology selected for the project. | Date | The property is not set. |
BB. Phase6End | The end date for the sixth phase of the project. The number of phase end dates to populate depends on the methodology selected for the project. | Date | The property is not set. |
BC onwards | Project custom properties | Various | No values are set. |
For more on project metadata and how to populate the fields, click here.