registration open

Join the Interfolio team and other customers at the Elsevier Impact Conference in San Diego from April 14–16

Learn more

How Can We Help?

Search icon

Search Results

LM Error Message Glossary

This guide provides a description of error codes and messages that may occur in Interfolio's Lifecycle Management (LM) when doing a manual import or bulk data load. 

 

LM Error Messages

Error Message Explanation of Message Fix
Series
Series with this name/title already exists. This series already exists in LM for that unit. Review the unit name and ensure that this is a new series within that unit. Updates to existing series should be made in the module.
Invalid Unit Name. No corresponding unit found for Unit Name The unit provided in the import file is not in the unit hierarchy. Review the name of the unit in the import file. Unit names must match what exists in the unit hierarchy (in RPT or FS) exactly and are case sensitive. If the unit does not already exist, add it the appropriate module and reimport this record.
Rank
Invalid Rank Name. No corresponding rank found for Rank Name The rank name does not match any rank in the identified series within the specified unit in the module.
  • Review the rank name, the series name, and the name of the unit in the import file. 
  • Ensure that the rank name is spelled correctly and associated with the correct series. 
  • Ensure the series name is spelled correctly and associated with the listed Unit. 
  • Unit names must match what exists in the unit hierarchy (in RPT or FS) exactly and are case sensitive. 
  • If either the series or the Unit does not already exist, add it the appropriate module and reimport this record.
Invalid Rank Type Name. No corresponding rank type found for Rank Type Name The rank type name does not match one of the available values. Update the rank type to match one of the following values: Assistant Professor, Associate Professor, Full Professor, Visiting Professor, Adjunct Professor, Staff, Research, Lecturer, Administration, or Other.
No corresponding rank found for added professional journey The rank name does not match any rank in the identified professional journey within the identified series within the specified unit in the module.
  • Review the rank name, professional journey name, the series name, and the name of the unit in the import file.
  • Ensure that the rank name is spelled correctly and associated with the correct professional journey and series. 
  • Ensure the series name is spelled correctly and associated with the listed unit. 
    • Unit names must match what exists in the unit hierarchy (in RPT or FS) exactly and are case sensitive. 
  • If either the series or the unit does not already exist, add it the appropriate module and reimport this record.
{max_salary} must be greater than or equal to {min_salary} Error occurs when importing a rank with a {max_salary} less than its {min_salary} When importing a rank with salary range information, the maximum salary must be greater than the minimum salary.
Event
Rank Event with this name/title already exists. This rank already exists in LM for that specific rank/series/unit combination. Review the unit name, series name, and rank name to ensure that this is a new rank event for that rank, in that series, within that unit. Updates to existing rank events should be made in the module.
Rank Event already exists. There is already a rank event in the selected month and year. Each month/year can only include a single event, as all events default to the first day of the month. Update the event month and/or year to ensure that no two events are in the same month.
Invalid Event Type Names. No corresponding event type found for Event Type Names The event type name does not match one of the available values.

Update the event type name to match one of the following values: Appointment, Promotion, Reappointment, Review, Sabbatical, Tenure, or Other.

Multiple values must be delimited by a pipe | (pipe only, no spaces between values).

 
Workload
Invalid Workload Name. No corresponding workload found for Workload Name The workload name provided in the import file does not match any workload in the module. Review the name of the previously created workload. Update the import file to reflect the correct workload name.
Professional Journey
Professional Journey with this name/title already exists. This rank already exists in LM for that specific series/unit combination. Review the unit name and series name to ensure that this is a new journey. Updates to existing journeys should be made in the module.
Invalid Professional Journey Title. No corresponding professional journey found for Professional Journey Title. The professional journey Title does not match any journey in the identified series within the specified unit in the module.
  • Review the name of the professional journey title, the series name, and the name of the unit in the import file. 
  • Ensure that the professional journey title is spelled correctly and associated with the correct series. 
  • Ensure the series name is spelled correctly and associated with the listed unit. 
  • Unit names must match what exists in the unit hierarchy (in RPT or FS) exactly and are case sensitive. 
  • If either the series or the unit does not already exist, add it the appropriate module and reimport this record.
Professional journey was already applied This faculty member already has an appointment in the same series, at the same rank in the same journey. While faculty can have multiple appointments at once, they can only have one appointment in each series in the same journey. Review the import file and ensure that appointment details are accurate. Please update the appointment details to ensure that this record is not duplicative.
Appointment
Title can't be blank All appointment records require a title. Add a title to this appointment and reimport this record.
Faculty Profile with this name/title already exists. This faculty member already has an appointment in the same series, at the same rank in the same journey. While faculty can have multiple appointments at once, they can only have one appointment in each series in the same journey. Review the import file and ensure that appointment details are accurate. Please update the appointment details to ensure that this record is not duplicative.
Appointment already exists. This faculty member already has an appointment in the same series, at the same rank in the same journey. While faculty can have multiple appointments at once, they can only have one appointment in each series in the same journey. Review the import file and ensure that appointment details are accurate. Please update the appointment details to ensure that this record is not duplicative.
Contract expiration does not have the required date format: yyyy-mm-dd The date provided for the contract expiration does not have the required date format. Update the date format to be yyyy-mm-dd and reimport this record.
Contract expiration cannot be before the start date. The contract expiration should note the end of the event being added and therefore must come after the appointment date. Confirm that the appointment start date is correct and update the contract expiration date to be after the appointment start date.
Contract expiration is in the future and you import past appointments The contract expiration date for a past appointment (Past Appointment = TRUE) is current or in the future. Review the associated record and ensure that, if this is a past appointment, the contract expiration date is in the past. If this is not a past appointment, please update the past appointment field to FALSE.
Start date should be after profile date hired The faculty profile file contains a hire date earlier than the start date indicated in the appointment file. The start date indicated in the appointment file is used to indicate the contract/agreement start date. Review the faculty member's hire date on the faculty profile file and adjust the start date on the appointment file to be greater than this date.
Start date must not be in the future The start date provided for the appointment is in present or future. Appoints should be imported on or after the appointment start date. All appointment start dates should be in the past.
Was this article helpful?
Give feedback about this article

Related Articles