Adding other information to the sample table

You use the Additional Fields tab to view or change the default mappings for fields in your participants text file that do not correspond to the required columns in the sample table. Participants automatically maps these fields to additional columns, and sets the column name to be the same as the field name. The upload process will subsequently copy the value of that field to that column.

For example, for telephone interviewing projects, you might want to upload the participant’s name and address. In addition, for projects whose participants speak different languages, you might want to upload the participant’s language so that you can use interviewer qualifications to match interviewers to participants. For more information about interviewer qualifications, see Adding properties to user property groups.

The Additional Fields tab lists all fields in the file you are uploading. However, you can change the settings only for those fields that are not already mapped to required columns.

Note If you want to use the “Call Outcome by Segment” and “Calls by Segment” reports in the Interviewing activity to display data about segments (that is, groups or categories of your choice), you must upload segment information from your text file into a column called “Segment” in the sample table. For more information about segments, see About segments.

Microsoft SQL Server reserved words cannot be used as field names. The current list of SQL Server reserved words is as follows:

ADD, EXTERNAL, PROCEDURE, ALL, FETCH, PUBLIC, ALTER, FILE, RAISERROR, AND, FILLFACTOR, READ, ANY, FOR, READTEXT, AS, FOREIGN, RECONFIGURE, ASC, FREETEXT, REFERENCES, AUTHORIZATION, FREETEXTTABLE, REPLICATION, BACKUP, FROM, RESTORE, BEGIN, FULL, RESTRICT, BETWEEN, FUNCTION, RETURN, BREAK, GOTO, REVERT, BROWSE, GRANT, REVOKE, BULK, GROUP, RIGHT, BY, HAVING, ROLLBACK, CASCADE, HOLDLOCK, ROWCOUNT, CASE, IDENTITY, ROWGUIDCOL, CHECK, IDENTITY_INSERT, RULE, CHECKPOINT, IDENTITYCOL, SAVE, CLOSE, IF, SCHEMA, CLUSTERED, IN, SECURITYAUDIT, COALESCE, INDEX, SELECT, COLLATE, INNER, SEMANTICKEYPHRASETABLE, COLUMN, INSERT, SEMANTICSIMILARITYDETAILSTABLE, COMMIT, INTERSECT, SEMANTICSIMILARITYTABLE, COMPUTE, INTO, SESSION_USER, CONSTRAINT, IS, SET, CONTAINS, JOIN, SETUSER, CONTAINSTABLE, KEY, SHUTDOWN, CONTINUE, KILL, SOME, CONVERT, LEFT, STATISTICS, CREATE, LIKE, SYSTEM_USER, CROSS, LINENO, TABLE, CURRENT, LOAD, TABLESAMPLE, CURRENT_DATE, MERGE, TEXTSIZE, CURRENT_TIME, NATIONAL, THEN, CURRENT_TIMESTAMP, NOCHECK, TO, CURRENT_USER, NONCLUSTERED, TOP, CURSOR, NOT, TRAN, DATABASE, NULL, TRANSACTION, DBCC, NULLIF, TRIGGER, DEALLOCATE, OF, TRUNCATE, DECLARE, OFF, TRY_CONVERT, DEFAULT, OFFSETS, TSEQUAL, DELETE, ON, UNION, DENY, OPEN, UNIQUE, DESC, OPENDATASOURCE, UNPIVOT, DISK, OPENQUERY, UPDATE, DISTINCT, OPENROWSET, UPDATETEXT, DISTRIBUTED, OPENXML, USE, DOUBLE, OPTION, USER, DROP, OR, VALUES, DUMP, ORDER, VARYING, ELSE, OUTER, VIEW, END, OVER, WAITFOR, ERRLVL, PERCENT, WHEN, ESCAPE, PIVOT, WHERE, EXCEPT, PLAN, WHILE, EXEC, PRECISION, WITH, EXECUTE, PRIMARY, WITHIN, GROUP, EXISTS, PRINT, WRITETEXT, EXIT, PROC

Note Column names in the sample table must comply with the rules for SQL column names. In general, a column name must start with a letter or an underscore and be followed by any combination of letters, numbers, underscores, and the @, $, or # characters. For more information, use the search function in the UNICOM Intelligence Developer Documentation Library documentation to search for the text ‘Rules for Regular Identifiers’ and in the search results open the topic with that title.

This column shows the UNICOM Intelligence Data Model data types. When Participants creates the columns in the database, it converts these data types into the data types used by your database application. Most database applications have a wider range of data types than the UNICOM Intelligence Data Model, so Participants chooses the database data type that best matches the data that it finds in the text field. For example, the UNICOM Intelligence Data Model classifies all whole numbers (integers) as Long, while an SQL database will classify them as either int or smallint depending on the length of the number. If it is important that the columns are created with particular data types in the database, you can examine and change the columns’ definitions using your database application’s tools once the participant records have been loaded.