System Roles (All Required)

Process Designer

Project Importer

Reference Table Manager

Assignments

Table Owner

Creating Resource Demand Value Import Files

Import resource demand values data into Accolade using two specially named reference tables. The reference table pair begins with ACC_RDVI_, which identifies the tables as reference tables that contain demand value import data.

Note:  To import this type of data to Accolade, you must have the Process Designer, Project Importer, and Reference Table Manager user roles. To import a new version of an existing file, you must be assigned as the owner of the reference table file used for the import.

Follow these steps to import demand value data:

Accolade supports reference tables as spreadsheet, CSV, and XML files through the Reference Tables page, and through an auto-loader service. The information and examples provided are in spreadsheet format, contact Sopheon Customer Support for example files in additional formats.

Create a File That Contains the Demand Value Data to Import (Data Table)

The data table contains the data to import to Accolade. Administrators and Process Designers add the initial versions of the ACC_RDVI data table. The assigned table owner, which requires the Reference Table Manager user role, can add new versions of the table as needed.

Create the resource demand values data table as a spreadsheet, CSV, or XML file, ensuring that the contents of the file meets the following requirements:

Important! Enter all dates in mm/dd/yyyy format, and enter the decimal separator in numbers as a period (.).

Component Requirements

File Name

Resource demand value data must be in a file named ACC_RDVI_<pair identifier>_Data, where <pair identifier> matches the <pair identifier> in the demand value configuration table and is unique within Accolade. For example, ACC_RDVI_ResourceDemandValues_Data.

Rows

Each row contains a different demand values, and each demand value exists in only one row.

Column Names and Position

Column headings are in the first row of the worksheet. You can name columns as you see fit for your installation.

The configuration table described below maps the columns in the data table to the respective fields in the Accolade database.

Data

The following columns and data are required for each demand value:

  • Project ID or Identifier String Metric Name - Either the Project ID that displays on the project header, or a string metric that identifies the project to which the demand value applies. Only one is required to identify the project.

Important! If the Auto-Generate Project IDs system parameter is enabled, use a string metric as the identifier for the project.

  • Process Model Name - Depending on your system's configuration, this may display on the Project Home page. Used to further identify the projects to which the demand value applies.
  • Resource System Name - The unique, shorter name that identifies the resource in queries, reporting views, and field codes. Required if the demand is for a General resource.
  • Demand System Name - Required if a Resource System Name is provided. If the field is blank or missing, the import generates a demand system name automatically. To edit existing values for a demand whose system name you do not know, query the database using the Accolade Office Extensions add-in.
  • First Time Period Start Date - The first time period to which the demand value applies. Enter the date in mm/dd/yyyy format.
  • Last Time Period Start Date - The last time period to which the demand value applies. Enter the date in mm/dd/yyyy format.

The import loads to Accolade in the order the rows appear in the Data table. If the Data table contains resource demand values for overlapping time periods, the last row in the table for the time period is the row that displays in Accolade after the import.

  • Demand Value - The value to apply to all time periods between and including the dates specified in the First Time Period Start Date and the Last Time Period Start Date columns. The value can be between 0 and 100,000. If the field is blank, no value is added for the demand. If the value is 0, the demand is updated to a value of zero. Enter the decimal separator in numbers as a period (.).

 

The following columns and data are optional for each demand value:

  • Demand Type - Requested or Assigned. If the field is blank or missing, the demand type is set to Assigned. If an assigned demand is associated with a requested demand, you cannot change the demand type for either request through an import. See Allocating Assigned Resources to Resource Demand Requests for more information.
Example Icon

Import Resource Demand Values Data Example

* You may need to re-size the Help window to see the entire example.

 

Note the following in the example above:

  • Projects in this import are identified using the combination of the project code and process model name, not by an identifier string metric.
  • The import assigns demands to Project A, B, and C, for varying dates.

Download Sample

Map the Resource Demand Value Data to the Accolade Database (Config Table)

The configuration table contains the data mapping information so Accolade knows what type of data to expect in the accompanying data file. Administrators and Process Designers add the initial versions of the ACC_RDVI config table. The assigned table owner, which requires the Reference Table Manager user role, can add new versions of the table as needed.

Create the resource demand values configuration table as a spreadsheet, CSV, or XML file, ensuring that the file meets the following requirements:

Component Requirements

File Name

The resource demand value configuration must be in a file named ACC_RDVI_<pair identifier>_Config, where the <pair identifier> matches the demand value data file and is unique within Accolade. For example, ACC_RDVI_ResourceDemandValues_Config.

Rows

Each row maps a column in the data table to a specific type of demand value data.

Column Names and Position

The demand value configuration must have the following column names, from left to right as listed below:

  • Export Column Name - Enter each column heading that is included in the data table.
  • Metric System Name - If a string metric is used to identify the projects in the data file, enter the system name of the metric used to identify the projects. If the Project ID is used to identify projects, include this column but leave it blank.
  • Metadata Name - Enter the metadata name below that identifies the data included is in each column in the data table.
  • Unique Identifier - Enter TRUE in the row with the Export Column Name that uniquely identifies the projects within the import. Can be set for either the ProjectCode or a string metric. The import uses what you identify to match the demand values to their respective projects.

Accolade Metadata Names

Use the following metadata names in the Metadata Name column of the configuration table to map the data to the appropriate locations in the Accolade database:

  • ProjectCode
  • ProcessModelName
  • ResourceSystemName
  • DemandTypeSystemName
  • DemandSystemName
  • FirstTimePeriodStartDate
  • LastTimePeriodStartDate
  • DemandValue
Example Icon

Import Resource Demand Value Config Example

* You may need to re-size the Help window to see the entire example.

 

Note the following about the example above:

  • Each item in the Export Column Name column is a column heading in the data table.
  • The Metric System Name must match the metric system name exactly for the value to update.
  • The names listed in the Metadata Name column must match the metadata names listed above exactly for the import to process successfully. Enter the metadata name for each column that matches, or maps, the data in the data file to the Accolade database to ensure the data is imported to the correct location.
  • The TRUE setting in the Unique Identifier column indicates that project code is used to uniquely identify projects to which the demand values apply.

Download Sample

Learn More: