Data is often imported from a variety of sources with many different people inputting content. For example, you may have your team members use an Abstract Management System like ScholarOne and other team members use an exhibitor management system like A2Z. 


If, in a tool like ScholarOne, a session is added on that system without a correct date, or it's missing a required field like Session Type, then you will see errors. Some errors are automatically skipped by the CMS. Check the import reports to know which data fields have been excluded from the import so you know to fix those in your data sources. This could be as simple as a wrong image format for your exhibitor logo (e.g. images must be png or jpg format). 


If you are stopped from publishing due to Orphan errors, you are linking to content that doesn't exist in the CMS. Please review the article about Orphans.



Note that the errors are the same, regardless of the type of data.


Session Errors


Session Date Outside Requested Dates

row: 32 id: 1234567, 2017-12-30 outside date range 2017-12-25 to 2017-12-29


The conference dates are set to 12/25-12/29, 2017. The session you are trying to import with Session ID 1234567 has a Date of 1/5/16. This session does not occur within your conference dates. Correct the dates in your source data. 


Start/End time outside the parent Start/End time

row 8 id: 2004, end time 1531900800 is earlier than start time 1531926000


You have a subsession (presentation within a session). The presentation occurs at a date or time when either the parent session is already over or has not yet started. Ensure the presentation dates and times are set to occur within the dates/times of the parent session. 


Missing Session Title Field (required)

row: 10 id: 2039, missing a required field 2 Session Title clean:req:ml=500 title


All sessions must have a title. Ensure your session with ID 2039 has a title filled in in your source data.


Subsession id same as parent

row: 10 id: 2039, subsession cannot have itself as parent 2039


Presentations are linked to parent sessions by listing the ID of the parent session. So if the parent has the ID 10 and the presentation the ID 1000, then the presentation would list 10 as it's parent. This links the two records together. The presentation ID 1000 cannot have 1000 as the parent - this means it links to itself as the parent. Correct your source data. 


Speaker/Exhibitor/Media Errors

URL not in correct format

row: 7 id: 120749, invalid URL could not be corrected delawarelaw.widener.edu/prospective-students/compliance-programs/


The URL is not correctly formatted. It must start with https://


Email not in correct format

row: 3 id: 3010, the following email is invalid: edz at ativsoftware.com


An email address must have this format abc@abc.com and include the @ symbol. 


Email has multiple values

row: 3 id: 3010, only one email address allowed:  edz@ativsoftware.com, econverse@ativsoftware.com

Each email field can only have one single email address per person.

Missing Required Field (ID, Last Name/Exhibitor Name)

row: 2 id: , missing a required field 0 Speaker ID pri:req: personid


The speaker in your data source row 2 is missing required fields. In this example, the record is missing the ID field. 


row: 2 id: 1234a , missing a required field 2 Last Name clean:req:ml=50 lastname    

Speaker ID 1234a is missing Last name field which is required.


Wrong Image Format

row: 1 id: 1000, incorrect image file ext johnphoto.bmp


The image has an unsupported file extension. Only .png or .jpg files can be displayed. 


Wrong Media Item Type

row: 102 id: 1000, invalid media type: doc


You are using a type for media that does not exist. Media items can only have the following types: 

  • html
  • int/html (used for offline abstracts)
  • sso/html
  • pdf
  • ad (banner style image)


Search Training


Value has less than two characters

row: 1 id = 1000, <value>l must be a string of 2 or more characters


You must have terms that are at least two characters long. 




Incorrect Date/Time formats


Date/Time - dt1 validator (Start DateTime)

  • Start value in wrong format
    • row: 1 id: 1000, invalid date-time, expects format Y-m-d H:i:s <value>
  • Missing end value
    • row: 1 id: 1000 specifies a start time, but does not have a matching end time validator
  • End value in wrong format
    • row: 1 id: 1000, starttime field: <value> has an invalid matching endtime <end value>
  • Start value is greater than end value
    • row: 1 id: 1000, end time is earlier than start time
  • Start and end values on different dates
    • row: 1 id: 1000, start and end times must be on the same calendar date


Date/Time - dt2 validator (End DateTime)

  • Value in wrong format
    • row: 1 id: 1000, invalid date-time, expects format MM/dd/yyyy HH:mm:ss $val


Time - t1 validator (Start Time)

  • Start value in wrong format
    • row: 1 id: 1000, invalid date-time, expects format HH:mm:ss <value>
  • MIssing end value
    • row: 1 id: 1000, specifies a start time, but does not have a matching end time validator
  • End value in wrong format
    • row: 1 id: 1000, starttime field: <value> has an invalid matching endtime <end value>
  • Start time later than end time
    • row: 1 id: 1000, end time <end value> is earlier than start time <value>
  • Start time same as end time
    • row: 1 id: 1000, end time <end value> is the same as the start time <value>


Time - t2 validator (End Time)

  • Value in wrong format
    • row: 1 id: 1000, invalid date-time, expects format HH:mm:ss <value>


Date - date validator (Date)

  • Value outside of event date range
    • row: 1 id: 1000, <value> outside date range <conf_start_date> to <conf_end_date>
    • Note that above error is written if the CMS Auto Set Date Based on Data Enabled option is OFF, or if the date could not be auto-set
  • Value in wrong format
    • row: 1 id: 1000, invalid date, expects format YYYY-MM-DD: <value>

Bad Data

Value being a comma, or starting with a comma

row: 1 Value cannot be a comma exclusively, data removed for item "1234"


Data cannot just be a comma. There must be actual alphanumeric content such as name, title, date, etc.  You would need to fix the item with the ID 1234


row: 1 Value cannot start with a comma, data removed for item "5678"


Just like you cannot start a sentence with a comma, you cannot have a data field start with a comma. Your content for ID 5678 must start with an alphanumeric character. 


Line breaks in non-description fields

row: 1 id: 7890, Metadata must not contain line breaks: <value>Meta - meta validator (for metadata)


The sample record ID 7890 has line breaks in fields where line breaks are not supported. Remove any line breaks in your source data. Line breaks are supported in subscription fields but cannot be used in other fields. Metadata in this case refers to fields that are used for filter keywords.  


Too much content in a field

row: 1 id: 1000, ID exceeds max length $ml: 20 'workshop-123456-tuesday-afternoon-repeated'


Each field in your table has a content limit. In this example, the ID field allows for 20 characters but, as you can see, the value is much longer than 20 characters. It's exceeding the limit. 





Contact Your Project Manager for the following


Max length - ml validator - ex. ml=20 - this is for the character length of the value

  • Value missing
    • row: 1 id: 1000, ml (max length) missing value 'ml=<val>'


Max - max validator - ex. max=20 - this is for numerical values below a specified value

  • Value exceeds threshold
    • row: 1 id: 1000, <field_name> exceeds max value 10000: 11000
  • Value in validator is not numeric, ex. max=10b
    • row: 1 id: 2000, max (max value) value not numeric 10b
  • Validator is missing value, ex. "max="
    • row: 1 id: 1000, max (max value) missing value 'max=<val>'


Required value - req validator

  • Value being missing
    • row: 1 id: 1000, missing a required field col: <column_num> <column_header>


Primary value - pri validator - usually a field for the session id, media id, etc.

  • Value being missing
    • row: 1 primary field missing


Numeric - value needs to be a number

  • Value is not a number
    • row: 1 id: 1000, the following number is invalid: 100b0


Clean - clean validator (Clean HTML Tags)

  • Value has items that could not be cleaned
    • row: 1 id = 1000, lookup=<column header> Invalid character, unable to clean: <invalid items>


Color - color validator

  • Value in wrong format
    • row: 1 id: 1000, invalid color format: <value> (valid is #FFFFFF, #FFF, FFFFFF, FFF)


Index items - id validator (ex. id=speaker) - used for media items attached to session, exhibitor, etc.

These appear in import dialog Validation field as "Speaker (Index)", etc.

  • No primary value in row
    • row: 1 id: 1000, primary field missing - can't create index
  • An index value missing - ex. "3000, 3010, , 3015"
    • row: 1 id = 1000 val = <value> index value missing for primary key <primary value>


Separated items - sep(x,y) validator

  • Missing value - field is empty
    • row: 1 id: 1000, sep (separated index) missing fields 'sep(x/y)=<field>;<field>
  • Number of () values not equal to 2 - when parsing by the "/", there is not both an x and a y
    • row: 1 id: 1000, sep, invalid syntax, should be in the form of 'sep(x/y)=<val>;<val>
  • Number of = values not equal to 2 - when parsing by "=", there is not a value on both sides of "="
    • row: 1 id: 1000, sep (separated index) missing value 'sep(x/y)=<val>;<val>