nCORE / nSPECT Data Integration Tags
- Will Rensmith
- Emad Shaat
- Ruth Webster
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 |
|---|---|---|
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 |
|---|---|---|
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 |
|---|---|---|
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 |
|---|---|---|
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 |
|---|---|---|
START_DATE | 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 | 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 | 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 | 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 | 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 |
|---|---|
| Inspection start date |
| Inspector Name |
| Inspection Scheduled date |
| Site City |
| Site Count |
| Site District Code |
| Site Address Line 1 |
| Site Address Line 2 |
| Site State |
| Site Zip Code |
| Site Key |
| 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.
Â
Â