Troubleshooting Annual Report Data Import

You are using an older version of the N-PEARS report data import. Download a fresh file from the Report Data Import section and paste your data into this file before recompleting the import. 

Errors in the address column:

Does a sensitive site have an address? Sensitive sites should not include an address in the spreadsheet.

Is a site missing an address that has not been marked as sensitive? 

Errors in the State Column: 

Are state names entered correctly? All state fields should have a two letter abbreviation with both letters capitalized.

Errors in the Zip Column: 

Is this a valid zip code for the address entered? 

Errors in the Project Column

Every row should have a project name entered to help the system map the data to the correct project. 

Errors in the External Site Id Column 

Is there an error for that site on the sites sheet? Sites with errors will not import, causing the system to flag this as a missing site id.

Is this site id entered in the sites sheet? 

Errors in the Intervention Approaches Column

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the Settings Column

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the Project column 

Every row must have a project. 

Each project should only have one row. Duplicated project names will cause the importer to fail.

Errors in the method_in_person column 

This field should only have 1 or 0.

Errors in the method_virtual_live_online column 

This field should only have 1 or 0.

Errors in the method_virtual_self_directed column 

This field should only have 1 or 0.

Errors in the sessions_single column 

This field should only have 1 or 0.

Errors in the sessions_series_2_to_4 column 

This field should only have 1 or 0.

Errors in the sessions_series_5_to_9 column 

This field should only have 1 or 0.

Errors in the sessions_series_10_plus column 

This field should only have 1 or 0.

Errors in the sessions_num_in_person column 

This should be a number greater or equal to 0.

Errors in the sessions_num_virtual column 

This should be a number greater or equal to 0.

Errors in the sessions_average_time_engaged column 

This should be a number greater or equal to 0.

Errors in the languages column 

Languages here must match the languages list in the key mapping sheet. Missing languages should go in the languages_other column.

Errors in the reach_total column

Reach total must match the sum of the values in individual reach fields (ethnicity, age, and race). If the totals do not line up, this field will error.

Errors in the reach_ages_5_to_17_actual column

The sum of the subgroups must be less than the total reported in this field. 

Errors in actual and estimated demographic fields

This column expects a whole number. 

Errors in the Project column 

Every row must have a project. 

Errors in the external_site_id Column 

Is there an error for that site on the sites sheet? Sites with errors will not import, causing the system to flag this as a missing site id.

Is this site id entered in the sites sheet? 

Errors in the change_text column

Each row should include only one PSE change.

Cross-reference the PSE Change vs the Key Mapping document. The PSE change should completely match what’s listed. 

Errors in the reach_total column

A number greater than or equal to 0 should be entered. 

Errors in the Project column 

Every row must have a project. 

Errors in the partner_type column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the partner_levels column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly.

Errors in the partner_contributions column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly.

Errors in the number_of_partners column 

This must be a number. 

Errors in the project column 

Every row must have a project. 

Errors in the primary_topics column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the stage_of_implementation column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the languages column 

Languages here must match the languages list in the key mapping sheet. Missing languages should go in the languages_other column.

Errors in the scale column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the project_areas column 

Cities should be entered as state_city

Counties should be entered as county_state

Zip Codes should be entered as state_zip

Census tracts should be entered as state_tract

Cross-reference the key mapping document for the correct key to use for a reservation name. 

Errors in the external_campaign_id column 

 Verify the campaign number matches what’s listed on the Social Marketing sheet. 

Errors in the market_segments column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

If other is specified, enter another group in the market_segment_other column 

If another market segment is entered, this field must have “other” listed. 

If another ethnic group is entered in market_segment_ethnic_groups this field must have “ethnic-groups” listed. 

Errors in the segment_snaped_individuals or segment_total_individuals columns

This must be a number. 

Errors in the external_campaign_id column 

 Verify the campaign number matches what’s listed on the Social Marketing sheet. 

Errors in the channel column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the impressions column

This must be a number. 

Errors in the snaped_eligible_reach column

This must be a number. 

Errors in the reach_source column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

If another reach is entered in reach_source_other, this field must have “other” listed.

Errors in the directs_audience_to_website column 

This field should only have 1 or 0.

Errors in the Project column 

Every row must have a project. 

Each project should only have one row. Duplicated project names will cause the importer to fail.

Errors in the languages column 

Languages here must match the languages list in the key mapping sheet. Missing languages should go in the languages_other column.

Errors in the channels column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the channels_other column 

This field is limited to 250 characters. 

Errors in the title column 

This field cannot be blank. 

Errors in the External Site Id Column 

Is there an error for that site on the sites sheet? Sites with errors will not import, causing the system to flag this as a missing site id.

Is this site id entered in the sites sheet? 

Errors in the Project column 

Every row must have a project. 

Errors in the partner_types column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the related_indicators column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the external_coalition_id column 

A number is required here.

Errors in the level column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

Errors in the sector column 

Cross-reference the keys against the Key Mapping sheet. Keys must match exactly in order to map correctly. 

If there is a value in the other_sector field, this field should say “other” 

Errors in the num_members column 

This should be a number greater than 0