nCORE / nSPECT Data Integration Tags

Owned by Will Rensmith
Last updated: Oct 29, 2024 by Emad Shaat
3 min read

This page lists the available data integration tags that can be used when configuring nSPECT form controls for both inbound and outbound data transfer between nCORE and nSPECT.

Configuring and using nSPECT Integration tags is discussed on the nCORE / nSPECT Data Integration page.

The tags defined under Prepopulating nSPECT Inspections with Data from nCORE will only function when the inspection is pushed from nCORE. Ad hoc inspections cannot use nCORE data for prepopulation; only tags specified in Non-nCORE Evaluations (Ad Hoc Inspections) will work with these inspections.

Prepopulating nSPECT Inspections with data from nCORE

Different data integration tags must be used for repeating and non-repeating sections in an nSPECT Inspection form depending.

Non-repeating data includes information about the site, inspection, related permit, inspection contact, or permit permittee contact.

Repeating data includes information about all other contacts associated with the inspection, features, and permits.

Prepopulating Non-Repeating Data (Site, Evaluation, Permit, Inspection Contact, Permittee Contact)

Technical Note: the following data is provided by the nSpectImport.CME_INSPECTION_MASTER database view.

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

SITE_NUM

SITE.SITE_NUM

Site Number

SITE_SITE_NAME

SITE.SITE_NAME 

Site Name, non-standard tag as SITE_NAME is reserved by nSpect

SITE_ADDR

SITE.ADDR_1, SITE.ADDR_2, SITE.CITY, SITE.REF_STATE_CODE, SITE.ZIP_CODE

Concatenated Site Address fields

SITE_ADDR_1

SITE.ADDR_1 

 

SITE_ADDR_2

S.ADDR_2 

 

SITE_CITY

SITE.CITY 

 

SITE_STATE

SITE.REF_STATE_CODE 

 

SITE_ZIP_CODE

SITE.ZIP_CODE 

 

SITE_ADDR_CMNTS

SITE.ADDR_CMNTS

 

SITE_CNTY

REF_CNTY.DESCR 

 

SITE_OWNER_TYPE

REF_OWNRSH_TYPE.DESCR

 

SITE_LAT

SITE_LATITUDE

 

SITE_LONG

SITE_LONGITUDE

 

PARCEL_NUM

SITE.TAX_PARCEL_NUM

 

EVAL_NUM

EVAL.EVAL_NUM 

 

INSPECTION_TYPE_NAME

REF_EVAL_TYPE.DESC

The type of inspection

PRMT_NUM

PRMT.PRMT_NUM

Permit information is pulled from corresponding EVAL.PRMT_ID record

PRMT_VERSN

PRMT.PRMT_VERSN

 

REF_PRMT_CATG_DESCR

REF_PRMT_CATG.DESCR

 

REF_PRMT_STAT_DESCR

REF_PRMT_STAT.DESCR

 

REF_PRMT_TYPE_DESCR

REF_PRMT_TYPE.DESCR

 

PRMT_ISSUE_DATE

PRMT.ISSUE_DATE

 

PRMT_EFCTV_DATE

PRMT.EFCTV_DATE

 

PRMT_EXPR_DATE

PRMT.EXPR_DATE

 

PROJ_NAME

SUBM.RESRC_PROJ_NAME

 

ICONT_CONTCT_NAME

CONTCT.CONTCT_NAME

Pulled from EVAL.ICONT_CONTCT_ID

ICONT_CONTCT_FIRST_NAME

CONTCT.FIRST_NAME

 

ICONT_CONTCT_LAST_NAME

CONTCT.LAST_NAME

 

ICONT_CONTCT_ORG_NAME

CONTCT.ORG_NAME

 

ICONT_CONTCT_ADDR

CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE

Concatenated Contact Address fields

ICONT_CONTCT_ADDR_1

CONTCT.ADDR_1

 

ICONT_CONTCT_ADDR_2

CONTCT.ADDR_2

 

ICONT_CONTCT_CITY

CONTCT.CITY

 

ICONT_CONTCT_STATE

CONTCT.REF_STATE_CODE

 

ICONT_CONTCT_ZIP_CODE

CONTCT.ZIP_CODE

 

ICONT_CONTCT_COUNTRY

CONTCT.DESCR

 

ICONT_CONTCT_PHONE

PHONE.PHONE

WHERE IS_PRIMARY = 1

ICONT_CONTCT_PHONE_EXT

PHONE.PHONE_EXT

 

ICONT_CONTCT_PHONE_TYPE_CODE

PHONE.REF_PHONE_TYPE_CODE

Primary phone type. E.g. mobile, office, etc.

ICONT_CONTCT_EMAIL

CONTCT.EMAIL

 

PERMT_CONTCT_NAME

CONTCT.CONTCT_NAME

Pulled from PRMT.PERMT_CONTCT_ID

PERMT_CONTCT_FIRST_NAME

CONTCT.FIRST_NAME

 

PERMT_CONTCT_LAST_NAME

CONTCT.LAST_NAME

 

PERMT_CONTCT_ORG_NAME

CONTCT.ORG_NAME

 

PERMT_CONTCT_ADDR

CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE

Concatenated Contact Address fields

PERMT_CONTCT_ADDR_1

CONTCT.ADDR_1

 

PERMT_CONTCT_ADDR_2

CONTCT.ADDR_2

 

PERMT_CONTCT_CITY

CONTCT.CITY

 

PERMT_CONTCT_STATE

CONTCT.REF_STATE_CODE

 

PERMT_CONTCT_ZIP_CODE

CONTCT.ZIP_CODE

 

PERMT_CONTCT_COUNTRY

CONTCT.DESCR

 

PERMT_CONTCT_PHONE

PHONE.PHONE

WHERE IS_PRIMARY = 1

PERMIT_CONTCT_PHONE_EXT

PHONE.PHONE_EXT

 

PERMIT_CONTCT_PHONE_TYPE

PHONE.REF_PHONE_TYPE_CODE

Primary phone type. E.g. mobile, office, etc.

INSPECTOR_NAME

USER.DISP_NAME

 

LAST_INSP_DATE

EVAL.START_DATE

Is the last date the site was inspected with the same inspection type.

Prepopulating Repeating Data - Inspection Contacts

Technical note: the following data is provided by the nSpectImport.CME_INSPECTION_EVAL_CONTCT database view

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

EVAL_CONTCT_NAME

CONTCT.CONTCT_NAME

 

EVAL_CONTCT_FIRST_NAME

CONTCT.FIRST_NAME

 

EVAL_CONTCT_LAST_NAME

CONTCT.LAST_NAME

 

EVAL_CONTCT_TITLE

CONTCT.TITLE

 

EVAL_CONTCT_ORG_NAME

CONTCT.ORG_NAME

 

EVAL_CONTCT_ADDR

CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE

Concatenated Contact Address fields

EVAL_CONTCT_ADDR_1

CONTCT.ADDR_1

 

EVAL_CONTCT_ADDR_2

CONTCT.ADDR_2

 

EVAL_CONTCT_CITY

CONTCT.CITY

 

EVAL_CONTCT_STATE

CONTCT.REF_STATE_CODE

 

EVAL_CONTCT_ZIP_CODE

CONTCT.ZIP_CODE

 

EVAL_CONTCT_PHONE

PHONE.PHONE

 

EVAL_CONTCT_PHONE_EXT

PHONE.PHONE_EXT

 

EVAL_CONTCT_EMAIL

CONTCT.EMAIL

 

EVAL_CONTCT_AFFIL_CONCAT

REF_AFFIL_TYPE.DESCR

Concatenated Contact Evaluation Affiliation (Role) Types separated by commas

Prepopulating Repeating Data - Permit Contacts

The following integration tags pulls any contacts related to inspection’s related permit and populates data into a repeating nSPECT section.

Technical note: the following data is provided by nSpectImport.CME_INSPECTION_PRMT_CONTCT database view.

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

PRMT_CONTCT_NAME

CONTCT.CONTCT_NAME

 

PRMT_CONTCT_FIRST_NAME

CONTCT.FIRST_NAME

 

PRMT_CONTCT_LAST_NAME

CONTCT.LAST_NAME

 

PRMT_CONTCT_TITLE

CONTCT.TITLE

 

PRMT_CONTCT_ORG_NAME

CONTCT.ORG_NAME

 

PRMT_CONTCT_ADDR

CONTCT.ADDR_1, CONTCT.ADDR_2, CONTCT.CITY, CONTCT.REF_STATE_CODE, CONTCT.ZIP_CODE

Concatenated Contact Address fields

PRMT_CONTCT_ADDR_1

CONTCT.ADDR_1

 

PRMT_CONTCT_ADDR_2

CONTCT.ADDR_2

 

PRMT_CONTCT_CITY

CONTCT.CITY

 

PRMT_CONTCT_STATE

CONTCT.REF_STATE_CODE

 

PRMT_CONTCT_ZIP_CODE

CONTCT.ZIP_CODE

 

PRMT_CONTCT_PHONE

PHONE.PHONE

 

PRMT_CONTCT_PHONE_EXT

PHONE.PHONE_EXT

 

PRMT_CONTCT_EMAIL

CONTCT.EMAIL

 

PRMT_CONTCT_CMNTS

CONTCT.ADDR_CMNTS

 

PRMT_CONTCT_AFFIL_CONCAT

REF_AFFIL_TYPE.DESCR

Concatenated Contact Permit Affiliation (Role) Types separated by commas

Prepopulating Repeating Data - Features

These tags populate features for the permit specified in the evaluation record.

Technical Note: the following data is provided by the nSpectImport.CME_INSPECTION_PRMT_FEATR database view.

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

nSPECT Data Integration Tag

nCORE Database Field Name

Comments

FEATR_LOC

FEATR_LOC_GEOG.LAT, FEATR_LOC_GEOG.LONG

Concatenated feature latitude, longitude separated by a comma

PRMT_FEATR_DESCR

FEATR.DESCR

 

PRMT_FEATR_ID_TXT

FEATR.FEATR_ID_TXT

 

PRMT_FEATR_TYPE

REF_FEATR_TYPE.DESCR

 


Outbound: nSPECT Inspections to nCORE Evaluations

Data integration tags can also be used to populate data back into the nCORE evaluation.

See below for configured tags and integration descriptions:

nSPECT Data Integration Tag

nCORE Field Tag

Description

nSPECT Data Integration Tag

nCORE Field Tag

Description

START_DATE
(valid on nSPECT "Date" control)

EVAL.START_DATE

In conjunction with START_TIME, Will fill in nCORE Evaluation Field "Start Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1".

START_TIME
(valid on nSPECT "Time" control)

EVAL.START_TIME

In conjunction with START_DATE, Will fill in nCORE Evaluation Field "Start Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1".

END_DATE
(valid on nSPECT "Date" control)

EVAL.END_DATE

In conjunction with END_TIME, Will fill in nCORE Evaluation Field "End Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1".

END_TIME
(valid on nSPECT "Time" control)

EVAL.END_TIME

In conjunction with END_DATE, Will fill in nCORE Evaluation Field "End Date" when inspection is completed in nSPECT. APP_DEPLOY_SETTING for code NSPECT_OVRRD_START_DATE must be set to "1".

FOLLOWUP_DATE
(valid on nSPECT "Date" control)

See Description

Creates a new Evaluation (EVAL) record in nCORE using the date specified in the control and the Evaluation Type (REF_EVAL_TYPE_CODE) specified as the followup inspection type.

EVAL_DCSN

EVAL.REF_DCSN_CODE

Matches values from nSPECT control to REF_DCSN.DESCR, and populates Evaluation Decision (EVAL.REF_DCSN_CODE) with the matching value.

n/a

EVAL.RPT_TRANSMT_DATE

If Application Deployment Setting flag NSPECT.SET_RPT_TRANMIT_DATE is set to true (1), the Report Transmittal Date will be set to the date the inspection was marked complete in nSPECT. This flag affects  all inspections performed in nSPECT, regardless of type or program area.

 

Non-nCORE Evaluations (Ad Hoc Inspections)

Prepopulated data from nCORE is only available when the inspection is created in nCORE and pushed to nSPECT. Inspections created directly in nSPECT cannot use nCORE tags for prepopulating data listed here.

nSPECT includes its own set of prepopulated data, which differs from the data in nCORE. During form design, you can choose whether a control should be prepopulated with tags from nCORE or nSPECT, based on the form’s use case and the data requirements. A control can be prepopulated from either nCORE or nSPECT.

The following tags can be used to prefill the form with specific data when an inspection is created directly within nSPECT.

nSPECT Tag

Description

nSPECT Tag

Description

WND_ACTUAL_START_DATE

Inspection start date

WND_INSPECTOR_DISPLAY_NAME

Inspector Name

WND_SCHEDULED_START_DATE

Inspection Scheduled date

WND_SITE_ADDRESS_CITY

Site City

WND_SITE_ADDRESS_COUNTY

Site Count

WND_SITE_ADDRESS_DISTRICT_CODE

Site District Code

WND_SITE_ADDRESS_LINE_ONE

Site Address Line 1

WND_SITE_ADDRESS_LINE_TWO

Site Address Line 2

WND_SITE_ADDRESS_STATE

Site State

WND_SITE_ADDRESS_ZIP_CODE

Site Zip Code

WND_SITE_KEY

Site Key

WND_SITE_NAME

Site Name

Site details are defined based on the information in nSPECT or added during inspection creation, depending on whether the inspection was created while online or offline.

 

Â