Customization Suite - ODBC

Transcription

1 Customization Suite - ODBC

2

3 Notice of Copyright Published by Maximizer Software Inc. Copyright All rights reserved. Registered Trademarks and Proprietary Names Product names mentioned in this document may be trademarks or registered trademarks of Maximizer Software Inc. or other hardware, software, or service providers and are used herein for identification purposes only. Applicability This document applies to Maximizer CRM 10.5 and Maximizer CRM 10.5 Customization Suite software.

4 Maximizer Software Address Information Corporate Headquarters Americas Maximizer Software Inc West Pender Street 10th Floor Vancouver, BC, Canada V6E 2N phone fax support Knowledge Base: Europe, Middle East, and Africa Maximizer Software Ltd 2nd Floor - Apex House, London Road Bracknell, Berkshire RG12 2XH United Kingdom phone fax [email protected] Asia Maximizer Asia Limited 17/F, Regent Centre 88 Queen's Road Central, Hong Kong +(852) phone +(852) fax [email protected] Australia Maximizer Software Solutions Pty. Ltd. Level 10, 815 Pacific Highway Chatswood, New South Wales Australia, (0) phone +61 (0) fax [email protected]

5 i Contents Chapter 1 Introduction...1 Who Should Use This Guide?...2 Related Documentation...2 Chapter 2 Maximizer ODBC: Overview...5 Using Maximizer ODBC...7 Defining a Data Source...8 Using ODBC-Compliant Software...9 Access Control and Security...10 Database Level...10 Table Level...10 Record Level...11 Field Level...11 Chapter 3 Maximizer ODBC: Programmer s...13 Maximizer ODBC Limits...14 ODBC API Conformance...15 Notes on the ODBC API Conformance Table...17 SQLMoreResults...17 SQLTransact...17 SQLSetStmtOption / SQLGetStmtOption...17 SQLSetConnectOption / SQLGetConnectOption...18 SQLGetTypeInfo...18 SQLGetInfo...18 SQLSpecialColumns...23 SQL Conformance...24 Minimum SQL Grammar...24 Core SQL Grammar...25 Extended SQL Grammar...27 Delimited Identifiers in SQL Statements...29 Scalar Functions...30 String Functions...30 Numeric Functions...30 Date Functions...30 System Functions...30 Conversion Functions...31 Data Types...32

6 ii Maximizer CRM 10.5 ODBC Data Type Mapping...32 Limitations on SQL_LONGVARCHAR...33 Comparison of Floats...33 Representation of Float Infinity...34 Maximizer Date and Time...34 Other Characteristics...35 SQL Statement Limitations...35 Stack Size...35 Precision and Scale...35 Collate Sequence...35 Closing an Open Table...36 Concurrency...36 Extensions to the ODBC GROUP BY Syntax...37 GROUP BY Syntax...37 GROUP BY Semantics...37 SELECT Statement select-list...37 HAVING With GROUP BY...38 Left Outer Join...39 Syntax...39 Vendor Strings...39 Examples of Left Outer Join...40 Tips and Tricks for Maximizer ODBC...44 Joining...44 Selecting...44 Updating...44 General Tips...44 Examples of Inserting Records Using Maximizer ODBC...45 Chapter 4 Maximizer ODBC: Data Tables...47 Alphabetical List of Maximizer ODBC Tables...48 Common Fields...50 Identity Fields...50 Security Fields...50 History Fields...51 User-Defined Field Tables...53 About User-Defined Field Tables...53 User-Defined Field Type_Id Constants...54 UDF_List Table...56 UDF_Table_Item Table...61 Combined_Client_User_Fields Table...63 Address Book Entry Tables...64 ABPartners Table...65 Address Table...66 Client Table...68 Company Table...74 People Table...77

7 iii Related_Entries Table...82 Appointment, Hotlist, and Notes Tables...85 Appointments Table...85 Hotlist Table...90 Notes Table...93 Campaign Tables...97 Automatic_Campaign Table...98 CampaignAccounts Table Combined_Campaign_User_Fields Table Manual_Campaign Table Customer Service Tables Combined_CSCase_User_Fields Table CSCases Table Opportunity Tables Activity Table Combined_Opp_User_Fields Table Currency Table OppActivity Table OppComp Table OppContact Table Opportunity Table OppPartners Table OppRole Table OppStep Table OppSuccessFactor Table Prob_Close_Range Table Reasons Table Strategy Library Tables Role Table Role_Standing_Link Table Standing_For_Role Table Standing_For_Success_Factor Table Step Table Step_Activity_Link Table Strategy Table Strategy_Role_Link Table Strategy_Success_Factor_Link Table Strategy_Step_Link Table Success_Factor Table Success_Factor_Standing_Link Table User and Group Tables Security_Group Table Team Table User_Details Table Third-Party Synchronization Tables Custom_Independent Table...168

8 iv Maximizer CRM 10.5 Custom_Child Table Index...179

9 1 C HAPTER 1Introduction In this chapter... Who Should Use This Guide? on page 2 Related Documentation on page 2

10 2 Maximizer CRM 10.5 This guide explains how to use ODBC in the Maximizer environment. It is a reference to the Maximizer database structure. It describes security that the Maximizer ODBC provides at the database, table, record, and field level. In addition the section shows the relationships between Maximizer data tables. It also describes each Maximizer data table, the fields within each table and the table indexes. Who Should Use This Guide? This guide is intended for business partners (value-added resellers) and developers. Related Documentation The Maximizer Customization Suites include the following guides. Accounting Link API Guide DDE API Guide ODBC Data Tables Guide Volume I Guide Volume II Guide Payment Gateway Architecture Guide When the Customization Suite is installed, these guides are available in PDF from the Maximizer Customization Suite folder in the Windows Start menu. The following additional documentation resources are available for Maximizer Enterprise: Online help (Help > Contents) provides additional information about using Maximizer and Administrator. Context-sensitive help (F1) provides details specific to the screen currently active in Maximizer. Press the F1 key to activate context-sensitive help for the current screen. The Maximizer Enterprise User s Guide is your reference guide to using Maximizer. This guide is available in PDF format from the Help menu in Maximizer and Administrator. The Maximizer Enterprise Administrator s Guide is your reference to installing, configuring, and managing Maximizer Enterprise. This guide is available in PDF format from the Help menu in Maximizer and Administrator The Maximizer Accounting Link User s Guide is your reference guide to configuring and using the Maximizer Accounting Link Designed for Use with QuickBooks. This guide is available in PDF format from the Help menu in Maximizer and Administrator. The MaxExchange Administrator s Guide is your reference guide to configuring and using MaxExchange. This guide is available in PDF format from

11 Chapter 1 3 the Maximizer Enterprise folder in the Windows Start menu when MaxExchange Synchronization Server is installed. The Maximizer Enterprise Training Guide includes detailed instructions and step-by-step exercises designed for classroom training or self-instruction. The Maximizer website ( provides the latest product information. It also includes a searchable Knowledge Base at

12 4 Maximizer CRM 10.5

13 2 C HAPTER 2Maximizer ODBC: Overview In this chapter... Using Maximizer ODBC on page 7 Access Control and Security on page 10

14 6 Maximizer CRM 10.5 Open Database Connectivity (ODBC) is an open programming interface that you can use to access data that is stored on database management systems (DBMS). Maximizer ODBC is a translator that allows you to read and write Maximizer data from ODBC-compliant applications. It also lets you access Maximizer databases for reporting and analysis. Typical applications you can use for these purposes include spreadsheets (for example, Excel and Lotus 1-2-3), report writers (for example, Crystal Reports and Impromptu), and executive information systems. On the basis of its read/write capabilities alone, the ODBC Driver extends the reach of your other applications and increases the usability and value of your Maximizer data. But the Maximizer ODBC Driver is much more than a basic driver. To begin, it uses validation rules to ensure the integrity of your Maximizer data which is beyond the scope of a basic ODBC driver. It also provides excellent security at the database, table, record, and field levels to ensure that access to data is tightly controlled according to assigned user rights. In addition, the Customization Suite Guides describe the structure and contents of each Maximizer data table, illustrate the links between tables, provide tips for efficient use of the driver, and contain a thorough programmer s reference. They enable you to optimize your use of the driver and save valuable development time.

15 Chapter 2 7 Using Maximizer ODBC Now that you have installed the driver, you are almost ready to access the data contained in Maximizer databases. Before you can do this, however, you must know how to define a data source. By defining a data source, you create a link between Maximizer and a database that you have selected. And since you are going to open Maximizer s database from within another application, you must also consult the user s guide that comes with that third-party application to determine how to use the program to access the ODBC database. When using ODBC with Address Books that do not have security enabled, you may optionally set the system login registry key as instructed below to suppress the login dialog box. This process should be used only for Address Book folders that do not have security enabled doing otherwise may result in ODBC connection errors. To set the registry key for Address Books not using security Open the Windows Registry Editor. The Registry Editor is an advanced tool that enables you to change settings in your system Registry. To do this: Click the Windows Start button to display the Start menu. Select Run, type REGEDIT and click OK. Go to the branch: HKEY_LOCAL_MACHINE\Software\ODBC\ODBCINST.INI\Maximizer ODBC Driver. Select New > String Value and enter SystemLogin. Double-click on the string and enter the value of False. This suppresses the default Maximizer ODBC login dialog box.

16 8 Maximizer CRM 10.5 Defining a Data Source A data source is the connection you make between the Maximizer ODBC Driver and a Maximizer database. You need to establish a connection in order to access the data in a given Maximizer database. You must define a data source for each database you want to access. Once you have defined a data source, however, the link between the Maximizer ODBC Driver and that database is permanent. To define a data source Open Data Sources (ODBC) from the Administrative Tools menu. You can access Administrative Tools through either the Control Panel or the Windows Start menu. The ODBC Data Source Administrator window appears. Click the System DSN tab. Click the Add button. The Create New Data Source window appears. Select Maximizer ODBC Driver and click Finish. The ODBC Maximizer Driver Setup window appears. From the drop-down list, select the name of the Maximizer database you want to access. Click the Options>> button, and select the following options as required: UDF Table Items Separation Char: Defines the character used to separate the UDF table item TRUE Date: With the default setting not checked, Maximizer date/time field information is retrieved as a String data type. However, if the TRUE Date option is checked, then Maximizer returns date/time fields as Date data type. The format for both the String and Date data types is determined by the short Date style and by the Date separator setting, set into the regional setting. UDF Tables Shown: With the default setting checked, Maximizer ODBC will include all UDF Tables in a Table Def type record set. If the UDF Tables Shown option is not selected, then all UDF Tables are not available through Maximizer ODBC. MR_MS: With the default setting not checked, the Mister/Miss field name appears as MR/MS. For systems that don't accept the '/' as a valid character for a field name, check the MR_MS options to have the Mister/Miss field name appear as MR_MS." Close the Maximizer ODBC Driver Setup dialog box and the ODBC Data Source Administrator.

17 Chapter 2 9 Using ODBC-Compliant Software You are now ready to use ODBC-compliant applications to access data stored in Maximizer databases. However, each ODBC-compliant application has its own set of commands for using an ODBC driver. Therefore, you need to consult the user s guide for the third-party application you are using for information about how to access data in an external relational database through an ODBC driver. Note You must enter a User ID to access Maximizer s ODBC database even if Maximizer security is not enabled. The default User ID is MASTER; the default password is CONTROL. If Maximizer security is enabled, then enter your User ID as you normally would in Maximizer. Note When linking to an external data source in Microsoft Access, you must specify a field or combination of fields as a unique index for each linked table. For the majority of tables, you can use the Data_Machine_Id and Sequence_Number fields as the unique index fields when linking to Maximizer ODBC driver data tables from Microsoft Access. The Team table is one exception because you must specify the first four fields as unique index fields: Db_Id, Rec_Type, Team_Id, and Team_Member_Id. The Maximizer ODBC Driver Data Tables chapter includes a list of index definitions for each table, and you can use any of the unique indexes to link to the tables from Microsoft Access.

18 10 Maximizer CRM 10.5 Access Control and Security The Maximizer ODBC Driver uses the same access control that is set up in Maximizer s Security tab, which is accessible from File > Preferences in Maximizer. The security is implemented at four levels: database level table level record level field level Each of these levels are described in this chapter. To access the Maximizer ODBC Driver Database Level Table Level Select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). Click the Add button. Select Maximizer ODBC Driver from the list, and click Finish. Select the Address Book to use as a data source, and click OK. the list of databases available to Maximizer is present when ODBC data sources are being set up. To gain access to the data source, the user must log in as a valid Maximizer user and supply the correct password. those tables that are set to be readable in Maximizer are visible to the user. If the user has no Read rights, then a table cannot be attached or opened.

19 Chapter 2 11 Record Level Depending on the access rights of the Maximizer user, only certain records are returned. For example, no private Address Book entries and associated tasks and appointments are shown if the Open other user s private entries checkbox is not selected in the Maximizer s Security Tab. The user can see OppActivity, OppStep, OppSuccessFactor, OppRole, and OppComp records only if they are a team member of an Opportunity. Also, only the Opportunity leader can delete an Opportunity record once it has been created. Note Master has access to all non-system records and fields. Field Level Certain fields may be protected depending on the user or group rights. For example, a user who is not a team member of an opportunity cannot modify the opportunity s Objective field.

20 12 Maximizer CRM 10.5

21 3 C HAPTER 3Maximizer ODBC: Programmer s In this chapter... Maximizer ODBC Limits on page 14 ODBC API Conformance on page 15 Notes on the ODBC API Conformance Table on page 17 SQL Conformance on page 24 Scalar Functions on page 30 Data Types on page 32 Other Characteristics on page 35 Extensions to the ODBC GROUP BY Syntax on page 37 Left Outer Join on page 39 Tips and Tricks for Maximizer ODBC on page 44

22 14 Maximizer CRM 10.5 The material in this chapter describes the characteristics of the Maximizer ODBC Driver, including operating system platforms supported by the Maximizer ODBC summary of Maximizer ODBC limits ODBC API conformance of the Maximizer ODBC to ODBC API SQL conformance of the Maximizer ODBC scalar functions supported by the Maximizer ODBC data types supported by the Maximizer ODBC other characteristics of the Maximizer ODBC For detailed information on the ODBC API, SQL grammar, scalar functions, and SQL data types, see Microsoft s ODBC 2.0 Programmer s and SDK Guide. Maximizer ODBC operates on Windows 95, Windows 98, Window NT 4.0, and Windows Maximizer ODBC Limits The following limits apply to Maximizer ODBC: Number of rows: 2 billion Number of columns in a query: 255 Size of a column: 2 gigabytes Number of connections: limited by memory Number of statements per connection: limited by memory Table name length: 64 characters Column name length: 64 characters Database qualifier: 68 characters Number of joined tables: limited by memory

23 Chapter 3 15 ODBC API Conformance Maximizer ODBC conforms to the ODBC Level 1 API. The following table lists the ODBC API functions that Maximizer ODBC supports. Table 1 ODBC API Functions Supported by Maximizer ODBC Function Conformance Level SQLAllocEnv Core SQLAllocEnv Core SQLAllocStmt Core SQLBindCol Core SQLCancel Core SQLColAttributes Core SQLColumns Level 1 SQLConnect Core SQLDataSources Level 2 SQLDescribeCol Core SQLDisconnect Core SQLDriverConnect Level 1 SQLError Core SQLExecDirect Core SQLExecute Core SQLFetch Core SQLFreeConnect Core SQLFreeEnv Core SQLFreeStmt Core SQLGetConnectOption Level 1 SQLGetCursorName Core SQLGetData Level 1 SQLGetFunctions Level 1 SQLGetInfo Level 1 SQLGetStmtOption Level 1 SQLGetTypeInfo Level 1

24 16 Maximizer CRM 10.5 Table 1 ODBC API Functions Supported by Maximizer (Continued) ODBC Function Conformance Level SQLMoreResults Level 2 SQLNumResultCols Core SQLParamData Level 1 SQLPrepare Core SQLPutData Level 1 SQLRowCount Core SQLSetConnectOption Level 1 SQLSetCursorName Core SQLSetParam Core SQLSetStmtOption Level 1 SQLSpecialColumns Level 1 SQLStatistics Level 1 SQLTables Level 1 SQLTransact Core

25 Chapter 3 17 Notes on the ODBC API Conformance Table SQLMoreResults SQLTransact Maximizer ODBC always returns SQL_NO_DATA_FOUND for this function. (Maximizer ODBC supports this function, with its return value, because of Microsoft Access requirements.) Maximizer ODBC does not support transactions or ROLLBACK. It supports AUTOCOMMIT in that all data written is committed automatically. SQLTransact always returns SQL_SUCCESS when ftype is SQL_COMMIT and always returns SQL_ERROR when ftype is SQL_ROLLBACK. SQLSetStmtOption / SQLGetStmtOption The following table describes the options that Maximizer ODBC supports for SQLSetStmtOption and SQLGetStmtOption. Table 2 Option Supported for SQLSetStmtOption / SQLGetStmtOption foption vparam Comments SQL-MAX-LENGTH SQL-NOSCAN SQL-MAX-ROWS See Microsoft s ODBC SDK Programmer s. See Microsoft s ODBC SDK Programmer s. See Microsoft s ODBC SDK Programmer s.

26 18 Maximizer CRM 10.5 SQLSetConnectOption / SQLGetConnectOption The following table describes the options that Maximizer ODBC supports for SQLSetConnectOption and SQLGetConnectOption. Table 3 Option Supported for SQLSetConnectOption / SQL GetConnectOption foption vparam Comments SQL-ACCESS-MODE SQL_AUTOCOMMIT SQL_CURRENT_QUALIFIER (65000) See Microsoft s ODBC SDK Programmer s. Valid with SQLGetConnectOption but not valid with SQLSetConnectOption since SQL_AUTOCOMMIT is always on. Valid with SQLGetConnectOption. Returns the current table qualifier. To set a table qualifier, use the USE statement. SQLGetTypeInfo SQLGetInfo SQLGetTypeInfo generates a list of database-specific data type names ( TYPE_NAME ) specified by Maximizer ODBC. The following table lists the values returned by Maximizer ODBC for the SQLGetInfo options. Table 4 Values Returned for SQLGetInfo Options finfotype SQL_ACCESSIBLE_PROCEDURES SQL_ACCESSIBLE_TABLES SQL_ACTIVE_CONNECTIONS SQL_ACTIVE_STATEMENTS SQL_CONCAT_NULL_BEHAVIOR SQL_CONVERT_BIGINT SQL_CONVERT_BINARY Return Values N for No. N for No. 0 to indicate no limit. 0 to indicate no limit. 1 to indicate that the result is a concatenation of non-null valued columns. 0 for conversion not supported. 0 for conversion not supported.

27 Chapter 3 19 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_CONVERT_BIT SQL_CONVERT_CHAR SQL_CONVERT_DATE SQL_CONVERT_DECIMAL SQL_CONVERT_DOUBLE SQL_CONVERT_FLOAT SQL_CONVERT_FUNCTIONS SQL_CONVERT_INTEGER SQL_CONVERT_LONGVARBINAR Y Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. 1 for conversion supported. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. 0 for conversion not supported.

28 20 Maximizer CRM 10.5 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_CONVERT_LONGVARCHAR SQL_CONVERT_NUMERIC SQL_CONVERT_REAL SQL_CONVERT_SMALLINT SQL_CONVERT_TIME SQL_CONVERT_TIMESTAMP SQL_CONVERT_TINYINT SQL_CONVERT_VARBINARY SQL_CONVERT_VARCHAR Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide. 0 for conversion not supported. Depends on data types supported by Maximizer ODBC. Will be a subset of SQL data type conversions listed in Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide.

29 Chapter 3 21 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_CORRELATION_NAME (65000) SQL_CURSOR_COMMIT_ BEHAVIOR SQL_CURSOR_ROLLBACK_ BEHAVIOR SQL_DATA_SOURCE_NAME SQL_DATA_SOURCE_READ_ONL Y SQL_DATABASE_NAME SQL_DBMS_NAME SQL_DBMS_VER SQL_DEFAULT_TXN_ISOLATION SQL_Driver_HDBC SQL_Driver_HENV SQL_Driver_HSTMT SQL_Driver_NAME SQL_Driver_VER SQL_EXPRESSIONS_IN_ORDERBY SQL_FETCH_DIRECTION SQL_FILE_USAGE (65002) 2 to indicate that any correlation name can be used. 2 to indicate that cursors are preserved in the same position as before the COMMIT operation and that the application can execute or fetch without preparing the statement again. 0 to indicate that cursors are closed and deleted and that the application must prepare and execute the next statement. Long pointer to the name of the underlying data source. N for No. Long pointer to the current table qualifier. Long pointer to the DBMS name character string supplied by Maximizer ODBC (e.g., MAXWIN ). Long pointer to the version character string supplied by Maximizer ODBC (e.g., 1.20 ). 0 to indicate that transactions are not supported. Handled by the Driver Manager (ODBC.DLL). Handled by the Driver Manager (ODBC.DLL). Handled by the Driver Manager (ODBC.DLL). Long pointer to the name of Maximizer ODBC. Long pointer to the version of Maximizer ODBC in the form nn.nn.nnnn (e.g., ). Y for Yes. SQL_FD_FETCH_NEXT. The returned value is a 16-bit integer that indicates how the driver directly treats files in a data source. A value of 0 (SQL_FILE_NOT_SUPPORTED) indicates that the driver is not a single-tier driver. A value of 1 (SQL_FILE_TABLE) indicates a single-tier driver that treats files in a data source as tables. A value of 3 (SQL_FILE_QUALIFIER) indicates a single-tier driver that treats files in a data source as a qualifier.

30 22 Maximizer CRM 10.5 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_IDENTIFIER_CASE 4 to indicate that identifiers are mixed case (i.e., not case sensitive). SQL_IDENTIFIER_QUOTE_CHAR Long pointer to the double-quote character ( ). SQL_MAX_COLUMN_NAME_LEN 64. SQL_MAX_CURSOR_NAME_LEN 18. SQL_MAX_OWNER_NAME_LEN SQL_MAX_PROCEDURE_NAME_ LEN SQL_MAX_QUALIFIER_NAME_LE N 0 to specify that owner names are not supported. 0 to specify that procedure names are not supported. 68. SQL_MAX_TABLE_NAME_LEN 64. SQL_MULT_RESULT_SETS SQL_MULTIPLE_ACTIVE_TXN SQL_NUMERIC_FUNCTIONS SQL_NON_NULLABLE_COLUMNS (65001) SQL_ODBC_API_CONFORMANCE SQL_ODBC_SAG_CLI_ CONFORMANCE SQL_ODBC_SQL_CONFORMANC E SQL_ODBC_SQL_OPT_IEF SQL_ODBC_VER SQL_OUTER_JOINS SQL_OWNER_TERM SQL_PROCEDURE_TERM SQL_PROCEDURES SQL_QUALIFIER_NAME_ SEPARATOR SQL_QUALIFIER_TERM N for No. N for No. SQL_FN_NUM_MOD. 1 (SQL_NNC_NON_NULL) to indicate that NOT NULL is enforced in CREATE TABLE statements. 0 (SQL_NNC_NULL) to indicate that NOT NULL is not enforced in CREATE TABLE statements. 1 for Level 1 conformance. 1 for SAG-compliant. 0 to indicate Minimum SQL conformance, although Maximizer ODBC supports some core SQL functions as well. N for No. Handled by the Driver Manager (ODBC.DLL). Y for Yes. to indicate not supported by this driver. to indicate not supported by this driver. N for No. \. DATABASE.

31 Chapter 3 23 Table 4 finfotype Values Returned for SQLGetInfo Options (Continued) Return Values SQL_ROW_UPDATES SQL_SCROLL_CONCURRENCY SQL_SCROLL_OPTIONS SQL_SEARCH_PATTERN_ESCAPE \. SQL_SERVER_NAME Y for Yes. SQL_SCCO_READ_ONLY. SQL_SO_FORWARD_ONLY. Long pointer to the server name character string supplied by Maximizer ODBC (e.g., MAXIMIZER ). SQL_STRING_FUNCTIONS SQL_FN_STR_CONCAT SQL_FN_STR_LEFT SQL_FN_STR_LTRIM SQL_FN_STR_LENGTH SQL_FN_STR_LCASE SQL_FN_STR_RIGHT SQL_FN_STR_RTRIM SQL_FN_STR_SUBSTRING SQL_FN_STR_UCASE. SQL_SYSTEM_FUNCTIONS SQL_TABLE_TERM SQL_FN_SYS_USERNAME SQL_FN_SYS_DBNAME. TABLE. SQL_TIMEDATE_FUNCTIONS SQL_FN_TD_CURDATE SQL_FN_TD_DAYOFMONTH SQL_FN_TD_DAYOFWEEK SQL_FN_TD_MONTH SQL_FN_TD_YEAR SQL_FN_TD_CURTIME. SQL_TXN_CAPABLE SQL_TXN_ISOLATION_OPTION SQL_USER_NAME 0 to indicate that transactions are not supported. 0 to indicate that transactions are not supported. Character string of the login name. SQLSpecialColumns Maximizer ODBC uses unique indexes as the optimal set of columns that uniquely identify a row in the table. Maximizer ODBC cannot identify columns that are automatically updated when any value in the row is updated by a transaction.

32 24 Maximizer CRM 10.5 SQL Conformance Minimum SQL Grammar Maximizer ODBC supports Minimum SQL Grammar as documented in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. The following table shows the Minimum SQL Grammar that Maximizer ODBC supports. Table 5 Minimum SQL Grammar Supported by Maximizer ODBC Minimum SQL Grammar Examples Comments DELETE INSERT SELECT UPDATE DELETE FROM notes WHERE Owner_Id = Kirsten Allen. INSERT INTO notes (Client_Id, Contact_Number, [Date], [Time], [Text]) VALUES ( 1234,0, 1995/ 03/20, 14:03:32:85, Appointment with CIO ). INSERT INTO RELATED_ENTRIES (RELATED_TO_ID, RELATED_TO_NUMBER, RELATED_FROM_ID, RELATED- FROM_NUMBER, DESC ) VALUES ( c, 0, c, 0, Insertion into related_entries table ). SELECT* FROM notes; SELECT Client_Id FROM notes WHERE Type=0. UPDATE notes SET [Text]= Appointment with CEO WHERE Client_Id= 1234 and Contact_Number=0 and Date= 1995/03/20 and Time= 14:03:32:85. Date, Time, and Text are reserved words and thus are enclosed in [. DESC is a reserved word. It is enclosed in double quotes. * should refrain from using Select* From... since all records will be returned.

33 Chapter 3 25 Core SQL Grammar Maximizer ODBC partially supports Core SQL Grammar as documented in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. The following table shows the Core SQL Grammar that Maximizer ODBC supports. Table 6 Core SQL Grammar Supported by Maximizer ODBC Core SLQ Grammar Examples Comments SELECT SELECT (continued) approximatenumeric-literal SELECT COUNT(Date), [Date] FROM notes GROUP BY [Date] HAVING [Date]> 1995/ 03/19. SELECT * FROM notes WHERE type = 0 INSERT INTO notes (type) VALUES (0) In addition to supporting a GROUP BY on a column-list, as specified in Microsoft s ODBC SDK Programmer s, the ODBC Driver has extended the syntax to support a GROUP BY on an expressionlist. HAVING is not supported without GROUP BY. For a more detailed description of the Maximizer ODBC Driver s extensions to the ODBC GROUP BY syntax, see the second list of this chapter. In addition to supporting an ORDER BY on a column-list, as specified in Microsoft s ODBC SDK Programmer s, the Maximizer ODBC Driver has extended the syntax to support an ORDER BY on an expression-list or on any expression in a GROUP BY expression-list. e.g., SELECT * FROM EMP ORDER BY a+b,c+d,e. This causes the result table to be ordered by three expressions: a+b, c+d, and e. If the expression is a single positive integer literal, then that literal will be interpreted as the number of the column in the result set and ordering will be done on that column. No ordering is allowed on Set Functions or on an expression that contains a Set Function. [UNION select-statement] is not supported. Sub-queries are not supported.

34 26 Maximizer CRM 10.5 Table 6 Core SQL Grammar Supported by Maximizer ODBC (Continued) Core SLQ Grammar Examples Comments betweenpredicate correlationname exact-numericliteral SELECT [Text] FROM notes WHERE type BETWEEN 0 AND 3 SELECT * FROM EMP notes WHERE notes.client_id = 1234 INSERT INTO notes (Contact_Number, Type) VALUES (49000,3) The syntax expression1 BETWEEN expression2 and expression3 returns TRUE if expression1>=expression2 or returns FALSE if expression1>= expression3. The Maximizer ODBC Driver supports both table and column correlation names. in-predicate set-function SELECT * FROM notes WHERE [Time] in 13:15:30:95, 14:03:32:8 5 ); SELECT COUNT (Type) FROM notes SELECT MIN([Time]) FROM notes MIN(expression), MAX(expression), SUM(expression), AVG(expression), COUNT(*), and COUNT(expression) are supported. COUNT(expression) counts all non-null values for an expression across a predicate. e.g. SELECT COUNT(A+B) FROM Q counts all the rows in Q where A+B does not equal NULL.

35 Chapter 3 27 Extended SQL Grammar Maximizer ODBC partially supports Extended SQL Grammar as identified in the following table. Table 7 Extended SQL Grammar Supported by ODBC Driver Extended SQL Grammar Examples Comments LEFT OUTER JOIN Two-table outer join: SELECT * FROM People LEFT OUTER JOIN notes ON People.Client_Id = Notes. Client_Id Three-table outer join: SELECT * FROM (People LEFT OUTER JOIN Notes ON People.Client_Id = Notes. Client_Id) LEFT OUTER JOIN Addr ON People.EmpID = Addr.EmpID. Embedded in vendor string: SELECT t1.client_id, ename FROM {oj People t2 LEFT OUTER JOIN notes t1 ON t2.client_id=t1.client_i d} Maximizer ODBC supports two-table outer joins as specified in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. In addition to simple two-table outer joins, Maximizer ODBC supports n-way nested outer joins. The outer join may or may not be embedded in a vendor string. If a vendor string is used, Maximizer ODBC will strip it off and parse the actual outer join text. Maximizer ODBC s implementation of LEFT OUTER JOIN goes beyond the syntax in Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide. For further information on the Driver s support of LEFT OUTER JOIN, see the Left Outer Join section in this appendix.

36 28 Maximizer CRM 10.5 Table 7 Extended SQL Grammar Supported by ODBC Driver (Continued) Extended SQL Grammar Examples Comments date-literal time-literal timestampliteral SELECT * FROM emp WHERE hire_date < ' ' SELECT * FROM emp WHERE hire_date < {d ' '} SELECT * FROM bday WHERE btime = '10:04:29' SELECT * FROM bday WHERE btime = {t '10:04:29'} SELECT * FROM bday WHERE btime = ' :25:00' SELECT * FROM bday WHERE btime = {ts ' :04:29'} Maximizer ODBC supports the following date literal format: YYYY-MM-DD Dates may be in the range of year 0 to Date constants may be expressed in SQL statements as a character string or embedded in a vendor string. Maximizer ODBC treats the character string representation as a string of type SQL_CHAR and the vendor string representation as a value of type SQL_DATE. This becomes important when conversions are attempted. For example, CONVERT({ d ' ' }, SQL_TIMESTAMP) is valid whereas CONVERT(' ', SQL_TIMESTAMP) returns an invalid SQL_TIMESTAMP value. Maximizer ODBC supports the following time literal format: HH:MM:SS Time constants may be expressed in SQL statements as a character string or embedded in a vendor string. Maximizer ODBC treats the character string representation as a string of type SQL_CHAR and the vendor string representation as a value of type SQL_TIME. Maximizer ODBC supports the following time literal format: YYYY-MM-DD HH:MM:SS Timestamp constants may be expressed in SQL statements as a character string or embedded in a vendor string. Maximizer ODBC treats the character string representation as a string of type SQL_CHAR and the vendor string representation as a value of type SQL_TIMESTAMP.

37 Chapter 3 29 Table 7 Extended SQL Grammar Supported by ODBC Driver (Continued) Extended SQL Grammar Examples Comments Date Arithmetic SELECT * FROM invoices WHERE invoice_date > ' ' AND invoice_date < {d ' '} + 30 SELECT * FROM payment WHERE payment_date - invoice_date > 30 Maximizer ODBC supports adding or subtracting an integer from a date where the integer is the number of days to add or subtract, and the date is embedded in a vendor string. (This is equivalent to executing a CONVERT on the date.) Maximizer ODBC also supports subtracting one date from another to yield a number of days. Note: The True Date option must be turned on. Delimited Identifiers in SQL Statements Column names and table names can occur as delimited identifiers if they contain non- ODBC standard characters. The delimiter character for delimiting the SQL syntax for these functions (see Appendix G of Microsoft s ODBC 2.0 Programmer s and SDK Guide) is a double quote (e.g. SELECT last-name FROM non-standard-tbl ).

38 30 Maximizer CRM 10.5 Scalar Functions String Functions Maximizer ODBC supports ODBC scalar functions that may be included in an SQL statement as a primary expression. The scalar functions that the Maximizer ODBC supports are described below. Example Numeric Functions SELECT [Date] FROM notes WHERE LCASE([Text]) = 'appointment with ceo' Example Date Functions SELECT * FROM notes WHERE MOD(Type,3) = 0 Example System Functions CONCAT LENGTH RTRIM LCASE LTRIM SUBSTRING LEFT RIGHT UCASE MOD CURDATE DAYOFMONTH MONTH CURTIME DAYOFWEEK YEAR SELECT * FROM emp WHERE YEAR(hire_date) < 1990 DATABASE IF NULL USER Example SELECT * FROM notes WHERE Owner_Id = USER() Note IF and NULL are internal to Maximizer ODBC.

39 Chapter 3 31 Conversion Functions CONVERT Example SELECT Client_Id FROM notes WHERE =CONVERT ([Date], SQL_DATE) + 30

40 32 Maximizer CRM 10.5 Data Types The following table shows all the ODBC SQL data types that Maximizer ODBC supports. Application writers can use SQLGetTypeInfo to determine which of these ODBC SQL data types are supported by Maximizer ODBC. (For further details on SQLGetTypeInfo, see Microsoft s ODBC 2.0 Programmer s and SDK Guide.) As the following table indicates, how Maximizer ODBC maps a data type to a default type, unless another data type conversion is specified by the user when SQLGetData or SQLBindCol is called, depends on whether or not the type to be mapped is part of a complex expression. (For a discussion of data type conversions, see Appendix D of Microsoft s ODBC 2.0 Programmer s and SDK Guide.) ODBC Data Type Mapping Table 8 ODBC Data Type Mapping ODBC Data Type Expression Default Type SUM/AVG SQL_BIT SQL_BIT N/A SQL_NUMERIC SQL_DOUBLE same SQL_DATE SQL_DATE N/A SQL_TIMESTAMP SQL_TIMESTAMP N/A SQL_DOUBLE SQL_DOUBLE same SQL_REAL SQL_DOUBLE same SQL_INTEGER SQL_DOUBLE same SQL_LONGVARBINARY N/A N/A SQL_LONGVARCHAR SQL_LONGVARCHAR N/A SQL_SMALLINT SQL_DOUBLE same SQL_CHAR SQL_CHAR N/A SQL_TIME SQL_TIME N/A SQL_TINYINT SQL_DOUBLE same SQL_VARCHAR SQL_VARCHAR N/A

41 Chapter 3 33 The table below describes each of the columns in the preceding table. Table 9 Description of Columns in ODBC Data Type Mapping Table Column ODBC Data Type Expression Default Type SUM/AVG Description The ODBC data type. If a column is part of a complex expression, Maximizer ODBC will convert the data type of that column to an expression default type in the result column. For example, in the query SELECT c1 * 10, where c1 is of type SQL_TINYINT, the result column will be of type SQL_DOUBLE. The type of the expression result column is determined at expression compile time and not at expression run time. All numeric expressions will be defaulted to the SQL_DOUBLE data type. This is the data type returned by the aggregate functions SUM and AVG. This column corresponds to the type of expression in the aggregate (e.g., SUM(expression)). An entry of same means that the type returned by SUM renders the same type as the expression. Limitations on SQL_LONGVARCHAR Maximizer ODBC imposes the following limitations on columns of data type SQL_LONGVARCHAR: LIKE predicate operates on the first 65,500 characters of the column data. All other predicates operate on the first 256 characters of the column data. SELECT statements with GROUP BY, DISTINCT, and ORDER BY return all the data but only order on the first 256 characters of the column data. In a single call to SQLGetData, the maximum number of characters returned by Maximizer ODBC for an SQL_LONGVARCHAR column is 65,500. Multiple calls must be made to SQLGetData to retrieve column data over 65,500 characters. Comparison of Floats Maximizer ODBC compares floating point numbers in comparison predicates using an almost equals algorithm. For example, = , and is >= The epsilon value is defined as DBL EPSILON in float.h ( e-016). This feature works for large numbers, but > and < will not be detected for small numbers; small numbers will be detected as equal.

42 34 Maximizer CRM 10.5 Representation of Float Infinity Maximizer ODBC has both a binary and a character representation of float infinity as shown in the following table. Table 10 Representation of Float Infinity Value Name Single BIN Positive Single Character Double BIN Positive Double Character Maximum Positive 0x7FEFFFFFFFFFFFFF Maximum Negative 0x7FEFFFFFFFFFFFFF Infinity Positive Infinity Negative 0x7F E999 0x7FF E999 0xFF E999 0xFFF E999 Maximizer Date and Time Maximizer ODBC presents the Maximizer Date and Time in character string format (i.e., Date_string and Time_string ). The application, however, can convert the Date_string in SQL_CHAR to SQL_DATE if so desired in any date operations. The same is true for Time_string. CAUTION Time_string is in HH:MM:SS:HS format (i.e., Maximizer supports the hundredth of a second, such that a loss in precision may result in converting time in SQL_CHAR to that in SQL_TIME).

43 Chapter 3 35 Other Characteristics SQL Statement Limitations Stack Size Precision and Scale Collate Sequence Maximizer ODBC applies the following restrictions to SQL statements: Maximum of 1000 characters in a literal Maximum of 300 ANDed predicates (e.g., SELECT * FROM emp WHERE c1 AND c2 AND c3 use two ANDed predicates). Depending on the stack size allocated by the calling application, limitations on very long expressions (e.g., SELECT * FROM emp where c1 = ) may also apply. (See Stack Size below.) Maximum of 256 columns in a CREATE TABLE statement Maximum of 64 characters in a table or column and in index names A character in a character string literal may be any ANSI character between 1 and 255 decimals. A single quote (') must be represented as two consecutive single quotes (''). Maximizer ODBC requires a minimum available stack size of 10K from the calling application, and in some cases may require more. Therefore, we recommend an available stack size of at least 20K. Maximizer ODBC cannot determine the precision and scale of data values of type SQL_NUMERIC. Maximizer ODBC assumes that all tables accessed during an active connection have the same collate sequence. All tables within a query statement must have the same collating sequence for comparison operations to work properly.

44 36 Maximizer CRM 10.5 Closing an Open Table Concurrency Calling SQLFreeStmt with the SQL_CLOSE option changes the SQLState but does not close the open tables used by the hstmt. To close the tables currently used by hstmt, SQLFreeStmt must be called with the SQL_DROP option. In the following example, the Emp and Dept tables remain open: SQLPrepare(hStmt, SELECT * FROM Emp, Dept, SQL_NTS); SQLExecute(hStmt); SQLFetch until NO_DATA_FOUND SQLFreeStmt(hStmt, SQL_CLOSE); When SQLPrepare is subsequently called on by the hstmt, the tables used in the previous statement are closed. For example, when the following call is made, both the Emp and Dept tables will be closed by Maximizer ODBC: SQLPrepare(hStmt, SELECT * FROM Customer,SQL_NTS); The following call would then close the table Customer: SQLFreeStmt(hStmt, SQL_DROP); The timeliness of data, dynamic or snapshot, is determined by whether or not execution of a query results in a sort. Queries with DISTINCT, GROUP BY, or ORDER BY will result in a sort by Maximizer ODBC, unless an index exists that satisfies the required ordering. For those queries that do not result in a sort by Maximizer ODBC, the data fetched will be from the data files (called dynamic). For those queries that do result in a sort by Maximizer ODBC, the data fetched will be from a temporary table (called a snapshot). The temporary table is built from the required data in the original data file at SQLExecute time. Temporary tables greater than 64K will be written to a temporary file in the directory indicated by the application user s TEMP environment variable. If there is not enough disk space on the user s system to write the temporary file, the sort will fail. If the user is short of disk space on a local machine, the TEMP environment should be set to a network drive. Note For some sort operations (e.g., for SELECT statements where long data columns are included in the select-list or for SELECT statements with GROUP BY), Maximizer ODBC may use bookmarks that the Driver assumes are persistent within a SELECT statement. A situation may arise in which another application updates or deletes the row that a bookmark references. To avoid this situation, an application may set an exclusive lock on the table being sorted through a call to SQLSetStmtOption, with foption = 1153 and vparam = 1.

45 Chapter 3 37 Extensions to the ODBC GROUP BY Syntax GROUP BY Syntax In addition to the GROUP BY syntax in a SELECT statement as specified in Microsoft s ODBC 2.0 Programmer s and SDK Guide, the Maximizer ODBC Driver supports an extended GROUP BY syntax as follows: [GROUP BY expression,[expression]...] If an SQL_LONGVARCHAR expression is used in a GROUP BY clause, the Maximizer ODBC Driver only uses the first 256 characters of that expression. GROUP BY Semantics A GROUP BY query returns a result set which contains one row of the select-list for every group encountered. (See Appendix C of Microsoft s ODBC 2.0 Programmer s and SDK Guide for the syntax of a select-list.) For example, SELECT Dept FROM Emp GROUP BY Dept uses the Emp Table to produce a list of unique departments. Another example might be to count the number of employees in each department: SELECT Dept, COUNT(*) FROM Emp GROUP BY Dept In this case, the result set contains a list of unique departments and the count of employees in each department. SELECT Statement select-list As the above examples show, a select-list in a SELECT statement containing a GROUP BY clause can contain: An exact replica of one of the expressions in the GROUP BY expression-list. The exact replica can actually be a sub-expression in the select-list. For example, SELECT Dept, Salary + Commission, Salary + Commission / AVG(Salary+Commission) * 100 FROM Emp GROUP BY Dept, Salary + Commission is valid since no expression using ambiguous values occurs. Α set function. The rows operated on by the set function are those rows remaining after the WHERE search condition is applied. For example, in SELECT COUNT(*) FROM Emp WHERE Salary > GROUP BY Dept COUNT(*) counts only those rows in the Dept groups that have Salary >

46 38 Maximizer CRM 10.5 HAVING With GROUP BY The expressions in a HAVING clause may contain constants, set functions, or an exact replica of one of the expressions in the GROUP BY expression-list. For example, SELECT Dept, COUNT(*) FROM Emp GROUP BY Dept HAVING COUNT(*) > 2 returns departments where the count of employees is greater than 2. SELECT Dept, COUNT(*) FROM Emp GROUP BY Dept HAVING COUNT(*) > 2 AND Dept BETWEEN '120' AND '180' returns departments between 120 and 180 where the number of employees is greater than 2. Note The Maximizer ODBC Driver does not support HAVING without GROUP BY. The Maximizer ODBC Driver has implemented LEFT OUTER JOIN using SQL92 (SQL2) as a model. Since SQL2 is a new SQL standard and adequate descriptions do not exist, this appendix provides an explanation of this new outer join syntax and its associated meaning in the Maximizer ODBC Driver.

47 Chapter 3 39 Left Outer Join Syntax Vendor Strings The syntax taken here is a subset of the entire SQL92 syntax, which includes right outer joins, full outer joins, and inner joins. The TableRefList non terminal below occurs after the FROM keyword in a SELECT statement and before any subsequent WHERE, HAVING, and other clauses. Note the cooperatively recursive nature of TableRef and LeftOuterJoin. In other words, a TableRef can be a left outer join that can include TableRef s which, in turn, can be left outer joins ad infinitum. TableRefList : TableRef [, TableRefList] TableRef OuterJoinVS [, TableRefList] TableRef : TableName [CorrelationName] LeftOuterJoin ( LeftOuterJoin ) LeftOuterJoin : TableRef LEFT OUTER JOIN TableRef ON SearchCond The SearchCond contains join conditions which in their usual form are LT.ColumnName = RT.ColumnName, where LT is left table, RT is right table, and ColumnName represents some column within a given domain. No literals can exist in the ON SearchCond. The syntax above includes but goes beyond the current ODBC syntax in Appendix C of Microsoft's ODBC 2.0 Programmer s and SDK Guide. Furthermore, the vendor string escape sequence at the beginning and end of the LeftOuterJoin does not change the core syntax of the outer join. As shown in the above syntax, the Maximizer ODBC Driver accepts outer join syntax without the vendor strings. However, for applications that want to comply with ODBC across multiple databases, the vendor string construction should be used. Since ODBC vendor string outer joins do not support more than two tables, it may be necessary to use the syntax shown below in Example 4 below rather than that shown in Examples 2 and 3.

48 40 Maximizer CRM 10.5 Examples of Left Outer Join The following four tables provide examples of Left Outer Join. Employee FirstName LastName DeptID EmpID Frankie Avalon D103 E1 Gordon Lightfoot D102 E2 Lawrence Welk D101 E3 Bruce Cockburn D102 E4 Department DeptID LocID Name D101 L1 TV D102 L2 Folk Address EmpID E1 E2 Street 101 MemLane 14 Yonge St. Location LocID L1 L2 Name PlanetX PlanetY

49 Chapter 3 41 Example 1: Simple Two-way Left Outer Join SELECT * FROM Emp LEFT OUTER JOIN Dept ON Emp.DeptID = Dept.DeptID This simple two-way outer join produces the following result set: Emp Dept FirstName LastName DeptID EmpID DeptID LocID Name Frankie Avalon D103 E1 NULL NULL NULL Gordon Lightfoot D102 E2 D102 L2 Folk Lawrence Welk D101 E3 D101 L1 TV Bruce Cockburn D102 E4 D101 L1 TV Notice the NULL entry for Frankie Avalon. This occurs because no DeptID of D103 was found in the Dept table. In a standard (INNER) join, Franky Avalon would have been dropped from the result set altogether. Algorithm The algorithm that the Maximizer ODBC Driver uses in the above example is as follows: Taking the left table (TL), traverse the right table(tr), and for every case where the ON condition is TRUE, return a result set row composed of the appropriate TR row appended to the current TL row. If the ON condition is false, in all cases of TR row create a row instance of TR with all column values NULL. That result set, combined with the current TL row, becomes the returned result set row. In the simple two-way left outer join shown above, Emp is TL and Dept is TR. Note Although irrelevant to the algorithm, appending TL to TR assumes proper projection as specified in the select list of the query. This projection ranges from all columns (i.e., SELECT * FROM...) to only on column in the result set (i.e., SELECT FirstName FROM...).

50 42 Maximizer CRM 10.5 Example 2: Three-way Radiating Left Outer Join With radiating left outer joins, all other tables are joined onto one central table. In this example, Emp is the central table and all joins radiate from that table. SELECT * FROM (Emp LEFT OUTER JOIN Dept ON Emp.DeptID = Dept.DeptID) LEFT OUTER JOIN Addr ON Emp.EmpID = Addr.EmpID Emp Dept Addr FirstName LastName DeptID EmpID DeptID LocID Name EmpID Street Frankie Avalon D103 E1 NULL NULL NULL E1 101 MemLane Gordon Lightfoot D102 E2 D102 L2 Folk E2 14 Young St Lawrence Welk D101 E3 D101 L1 TV NULL NULL Bruce Cockburn D102 E4 D101 L1 TV NULL NULL Example 3: Three-way Chaining Left Outer Join In a chaining left outer join, one table is joined to another, and that table, in turn, is again joined to another. SELECT * FROM (Emp LEFT OUTER JOIN Dept ON Emp.DeptID = Dept.DeptID) LEFT OUTER JOIN Loc ON Dept.LocID = Loc.LocID Emp Dept Loc FirstName LastName DeptID EmpID DeptID LocID Name LocID Name Frankie Avalon D103 E1 NULL NULL NULL NULL NULL Gordon Lightfoot D102 E2 D102 L2 Folk L2 PlanetY Lawrence Welk D101 E3 D101 L1 TV L1 PlanetX Bruce Cockburn D102 E4 D101 L1 TV L1 PlanetX This join could also be expressed as: SELECT * FROM Emp LEFT OUTER JOIN (Dept LEFT OUTER JOIN Loc ON Dept.LocID = Loc.LocID) ON Emp.DeptID = Dept.DeptID We recommend the first syntax since it lends itself to both the radiating and chaining joins. The second syntax cannot be used for radiating joins because nested left outer join ON conditions cannot reference columns in tables outside their nesting. In other words, in the following query, the reference to Emp.EmpID is illegal: SELECT * FROM Emp LEFT OUTER JOIN (Dept LEFT OUTER JOIN Addr ON Emp.EmpID = Addr.EmpID) ON Emp.DeptID = Dept.DeptID

51 Chapter 3 43 Example 4: Three-way Radiating Left Outer Join, Less Optimized SELECT * FROM Emp E1 LEFT OUTER JOIN Dept ON E1.DeptID = Dept.DeptID, Emp E2 LEFT OUTER JOIN Addr ON E2.EmpID = Addr.EmpID WHERE E1.EmpID = E2.EmpID Emp Dept Addr FirstName LastName DeptID EmpID DeptID LocID Name EmpID Street Frankie Avalon D103 E1 NULL NULL NULL E1 101 MemLane Gordon Lightfoot D102 E2 D102 L2 Folk E2 14 Young St Lawrence Welk D101 E3 D101 L1 TV NULL NULL Bruce Cockburn D102 E4 D101 L1 TV NULL NULL This query returns the same results as the one in Example 2, assuming there are no NULL values for EmpID in Emp. This query, however, is not optimized as well as Example 2 and can be much slower.

52 44 Maximizer CRM 10.5 Tips and Tricks for Maximizer ODBC These tips and techniques help optimize use of the Maximizer ODBC Driver. Joining Selecting Updating Use indexed fields to speed up processing in the Where clause. Join only the tables that you require. See the table relational diagrams and index references in Chapter 4: Maximizer ODBC: Data Tables for fields to use for joining tables. Do not select unnecessary fields. Limit the result set by specifying conditions (e.g., Client_Id = and Contact_Number=1). Consult the Maximizer ODBC Table Index Definitions table (in Chapter 9) to identify which fields are indexed so they can be used in the search condition. Do not skip the beginning portion of the index. For example, if Client_Id and Contact_Number are the fields in the index, do not use Contact_Number=2 as the search condition. Always specify indexed fields together in the Where clause. For example, SELECT... FROM Client WHERE (Client_Id=... AND Contact Number=...) AND (Client_Id=... AND Contact_Number=...) is preferred over SELECT... FROM Client WHERE (Client_Id=... AND Client_Id=...) AND (Contact_Number=... AND Contact_Number=...) Do not include fields that cannot be updated in the SQL statement. Non-modifiable fields will be rejected and require extra validation. General Tips Be creative in determining the correct syntax; some implementations of ODBC SQL are non-standard and may be quite challenging. You may have to be resourceful and consult the application s ODBC SQL reference for the appropriate syntax. If you find syntax errors to be persistent with a specific application, call the manufacturer s technical support line for help. You may also find additional help in that application s Readme file. Use database tools to refine the SQL statement before attempting to use it in embedded SQL in a C/C++ application. Read the ODBC section of the application s documentation. To avoid frustration, make a note of any limitations and restraints.

53 Chapter 3 45 Examples of Inserting Records Using Maximizer ODBC If you are using Maximizer ODBC to insert records, you may find these examples useful. These examples show SQL statements for adding records to certain tables, such as the Appointments table, Company table, or Hotlist table, among others. All examples show the minimum fields that are required to successfully perform an insert for other available fields, refer to the Maximizer CRM Customization Suite - Volume I. Note Some tables are read-only and you cannot perform an insert. These tables include: CLIENT, COMBINED_CLIENT_USER_FIELDS, and COMBINED_OPP_USER_FIELDS. Appointments Table INSERT INTO APPOINTMENTS (App_Date,App_Time, [Text]) VALUES ('11/11/00','08:30:00:00','Inserting Appointments'); Address Table INSERT INTO ADDRESS (Client_ID,Name) VALUES (' C','Alternate Address'); Client Table It is not possible to perform an insert, as the Client table is a read-only table. Company Table INSERT INTO COMPANY (Company_Name) VALUES ('New Company'); HotList Table INSERT INTO HOTLIST (Schedule_Date,Schedule_Time, [Text]) VALUES ('11/11/00','08:30:00:00','Inserting Hotlist');

54 46 Maximizer CRM 10.5 Notes INSERT INTO NOTES (Client_ID,Contact_Number, [Text]) VALUES (' C',0,'Inserting Note'); Opportunity Table INSERT INTO OPPORTUNITY (Client_ID,Team_Id) VALUES (' C',-1); People Table INSERT INTO PEOPLE (Last_Name) VALUES ('Smith'); Prob_Close_Range Table In order for the insert to work correctly, there should be no existing Prob_Close_Range record with a Range_Min or Range_Max value which falls between 90 and 100. INSERT INTO PROB_CLOSE_RANGE (Range_Min,Range_Max,Name) VALUES (90,100,'Closing');

55 4 C HAPTER 4Maximizer ODBC: Data Tables Alphabetical List of Maximizer ODBC Tables on page 48 Common Fields on page 50 User-Defined Field Tables on page 53 Address Book Entry Tables on page 64 Appointment, Hotlist, and Notes Tables on page 85 Campaign Tables on page 97 Customer Service Tables on page 106 Opportunity Tables on page 111 Strategy Library Tables on page 141 User and Group Tables on page 162 Third-Party Synchronization Tables on page 168

56 48 Maximizer CRM 10.5 Alphabetical List of Maximizer ODBC Tables The following table lists the documented Maximizer ODBC tables and their page numbers. Table Name Starting on Page Number ABPartners Table page 65 Activity Table page 115 Address Table page 66 Appointments Table page 85 Automatic_Campaign Table page 98 CampaignAccounts Table page 100 Client Table page 68 Combined_Campaign_User_Fields Table page 102 Combined_Client_User_Fields Table page 63 Combined_CSCase_User_Fields Table page 106 Combined_Opp_User_Fields Table page 117 Company Table page 74 CSCases Table page 107 Custom_Child Table page 172 Custom_Independent Table page 168 Hotlist Table page 90 Manual_Campaign Table page 103 Notes Table page 93 OppActivity Table page 119 OppComp Table page 123 OppContact Table page 125 Opportunity Table page 127 OppPartners Table page 131 OppRole Table page 133 OppStep Table page 135 OppSuccessFactor Table page 137

57 Chapter 4 49 Table Name Starting on Page Number People Table page 77 Prob_Close_Range Table page 138 Reasons Table page 140 Related_Entries Table page 82 Role Table page 142 Role_Standing_Link Table page 143 Security_Group Table page 162 Standing_For_Role Table page 144 Standing_For_Success_Factor Table page 146 Step Table page 147 Step_Activity_Link Table page 149 Strategy Table page 151 Strategy_Role_Link Table page 152 Strategy_Step_Link Table page 156 Strategy_Success_Factor_Link Table page 155 Success_Factor Table page 159 Success_Factor_Standing_Link Table page 160 Team Table page 163 UDF_List Table page 56 UDF_Table_Item Table page 61 User_Details Table page 165

58 50 Maximizer CRM 10.5 Common Fields The following fields are common to many, but not necessarily all, Maximizer ODBC database tables. Some tables use these fields in different ways than described here. Refer to the table documentation for specific information. Identity Fields Table 11 Identity Fields. Data_Machine_Id Numeric 9 Yes System-generated unique database ID for MaxExchange synchronization. Cannot insert or update. Sequence_Numb er Numeric 9 Yes System-generated unique record ID for MaxExchange synchronization. Cannot insert or update. Security Fields Note that users who have the Modify other users private entries access right can view private records. Table 12 Security Fields. Private Integer 2 Specifies Full Access security for the record: 0 = Public (any user may view or modify the record) 1 = Private (only the user or group specified in the Owner_Id field may view or modify the record) Can insert. Can update.

59 Chapter 4 51 Table 12 Security Fields (Continued). Owner_Id String 11 User_Details. User_Id or Security_Group. Group_ID History Fields All Creation information (Creator_Id, Creation_Date, and Creation_Time) is read-only for all users with the exception of the MASTER user who may insert, update, and delete. If a creation Yes User or group who owns the record. Applicable only if Private field value is 1 (Private). Otherwise, the field is Public and is ignored. Can insert. Can update. Read_Id String 11 Ignored if Private = 0. Identifies which user or group has read-only rights to the record. Valid if ReadPriv = 1 and Private = 1. Can insert. Can update. ReadPriv Integer 2 Ignored if Private = 0. Identifies whether read-only access to the record is public or private: 0 = Public (everybody can see the record) 1 = Private (only user or group specified in Read_Id field can see the record, except user or group specified in Owner_Id field, who still has read and modify rights) Can insert. Can update.

60 52 Maximizer CRM 10.5 information field is deleted, it will be replaced by the default. This rule applies to all tables that are not read-only. Table 13 History Fields. Creation_Date or Create_Date or Date (Notes table) Creation_Time or Create_Time or Time (Notes table) DateString TimeString Yes Yes Date and time when the record was created. Default is current system date at time of creation. only for all users with the exception of MASTER user who may insert and update the Creator_Id. Otherwise, cannot insert, cannot update. Creator_Id String 11 Yes User who created the record. Default is current user ID. However, may be any user ID. System generated. only for all users with the exception of MASTER user who may insert and update the Creator_Id. Otherwise, cannot insert, cannot update. Last_Modify_Dat e Last_Modify_Tim e DateString 10 Must be populated by the user. Not automatically TimeString 11 updated. Can insert. Can update.

61 Chapter 4 53 User-Defined Field Tables User-Defined Field Type_Id Constants on page 54 UDF_List Table on page 56 UDF_Table_Item Table on page 61 Combined_Client_User_Fields Table on page 63 About User-Defined Field Tables A table is created for each new user-defined field in Maximizer. For example, when a new user-defined field titled Salary is created in Maximizer, a new table named U_SALARY is displayed as one of the ODBC tables in the table selection list. This new U_SALARY table contains the following fields: Client_Id, Contact_Number, Type_Id, Code_Id, and U_Salary. The last field, U_Salary, will have the same data-type that was selected in the process of creating the user-defined field in Maximizer. In this new U_SALARY table, the two fields that are read-only are Type_Id and Code_Id. Based on the type of user-defined field, the table name is prefixed by a designated letter. The following table identifies the table prefix for each type of user-defined field. Note that these prefixes are different for ODBC. Prefix C_ S_ U_ V_ W_ X_ X Y_ Type of user-defined field Third-Party Integration user-defined fields Customer Service user-defined fields Address Book user-defined fields Opportunity user-defined fields Campaign user-defined fields (X followed by a SINGLE underscore) Applies to special user-defined fields and System Fields, such as X_Category, X_DO_NOT_SOLICIT_BY, etc. (X followed by a DOUBLE underscore) Created dynamically for MaxExchange User user-defined fields Note When a user-defined field begins with a special character, such as an asterisk, the special character is replaced by an underscore in the ODBC table name. For example, a customer service user-defined field named *Maintenance would have a table name S Maintenance.

62 54 Maximizer CRM 10.5 User-Defined Field Type_Id Constants The following table lists all the available Type_Ids in the UDF_List table. Table 14 User-Defined Field Type_Id Constants Type_Id (Unsigned) Type_Id a (Signed) Data Type Field Name Alphanumeric Address Alphanumeric Web Site Alphanumeric Address Alphanumeric Address Table MaxExchange Distribution Table Salutation Table Call Result Table Subject Table Activity Table Mr/Ms Table Position Table City Table State Table Country Table Ext Table Department Table Division Table Company Table Pr Table Relationship Type Table Address Book Notes Category Table Customer Service Notes Category Table Type (Customer Service Case Type) Table Reason (Customer Service Case Reason) Table Origin (Customer Service Case Origin) Table Category (Customer Service Case Category)

63 Chapter 4 55 Table 14 User-Defined Field Type_Id Constants (Continued) Type_Id (Unsigned) Type_Id a (Signed) Data Type Field Name Table Case/Article Subject (Customer Service Case Subject / Knowledge Base Article Subject) Table Billing Type (Customer Service Case Fee) Table Products/Services (Customer Service Case Products/ Services) Table Queue (Customer Service Case Queue) Table Category (Address Book entry Category) Table Do not solicit by Table Descriptions Alphanumeric AccntCustomerID (Accounting Customer ID) Alphanumeric AccntVendorID (Accounting Vendor ID) Alphanumeric Portal Login ID Encrypted Alphanumeric Portal Password Table Status (Customer Service Case Status) Table Opportunity Notes Category Table Campaign Notes Category Table Confidence Rating Table Objective Table Campaign Objective a. You can translate the negative (signed) and positive (unsigned) integers using the constant For example, for the Campaign Objective Type_Id, =

64 56 Maximizer CRM 10.5 UDF_List Table The UDF_LIST table is a read-only table that shows all the available table UDFs and also Maximizer drop-down tables. Table 15 UDF_List Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only Table 16 UDF_List Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Unique Table_Id Type_Id Code_Id 3 Nonunique Name Table_Id Table 17 UDF_List Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Table_Id Integer 2 Flag indicating type of record: 1 = Record defines a UDF or UDF folder 2 = Record defines a UDF table item

65 Chapter 4 57 Table 17 UDF_List Table Fields (Continued) Type_Id Integer 2 Yes Unique identifier of a userdefined field: = fields created by users > = constant values For a list of Type_Id constant values, refer to Table, User- Defined Field Type_Id Constants, on page 54.) Note: Many of these tables are not created until the first item has been added by a user in Maximizer. Code_Id Integer 2 Yes 0 = Root UDF or folder Not 0 = Other Note: When the Code_Id is a value other than 0, and the Table_Id is 1, the Code_Id indicates the Type_Id of the parent folder. When the Code_Id is a value other than 0, and the Table _Id is 2, the records with the same Type_Id are all items belonging to the same table UDF.

66 58 Maximizer CRM 10.5 Table 17 UDF_List Table Fields (Continued) Len_Precision Integer 2 Yes Depending on the UDF type, Len_Precision determines size, decimal places, or an annually recurring event. Alphanumeric: characters Numeric: 1-10 decimal places Date: 0 = Not an annually recurring event 1 = Annually recurring event with year 2 = Annually recurring event without year Table: 0 = Multiple selections allowed 1 = one selection allowed UDF_Type Integer 2 Yes Type of UDF: 0 = Table UDF 1 = Date UDF 2 = Numeric UDF 3 = Alphanumeric UDF 4 = UDF folder InHotlist Integer 2 Yes Flag to determine if Date UDF should be in Hotlist or not. 0 = Don t include in Hotlist 1 = Include in Hotlist 4 = System UDF *UseAlternateForm 5 = (reserved for future use) 6 = System UDF Relationship Type

67 Chapter 4 59 Table 17 UDF_List Table Fields (Continued) Client_Type Integer 2 Yes Bit flag that specifies the type(s) of records the UDF applies to. Address Book UDFs: 1 = Company 2 = Individual 3 = Company or Individual 4 = Contact 5 = Company or Contact 6 = Individual or Contact 7 = Company, Individual, or Contact Other UDFs: 16 = User UDF 32 = Customer Service UDF 64 = Knowledge Base UDF 256 = Campaign UDF 512 = 3rd Party UDF = Opportunity UDF Note: These values can be combined to represent multiple types. For example, the value indicates that the UDF applies to Campaigns (256) and Opportunities (32768) = Name String 79 Name of UDF Limited to 62 characters. a

68 60 Maximizer CRM 10.5 Table 17 UDF_List Table Fields (Continued) ODBC_TblDesc String 79 Yes Name of the associated ODBC Table for this UDF heading. Limited to 64 characters. a ODBC table names for UDFs are prefixed by a letter depending on the type: S_ = Customer Service UDF U_ = Address Book Entry UDF V_ = Opportunity UDF W_ = Campaign UDF X_ = Special or System UDF (e.g., Do_not_solicit_by) X = MaxExchange (dynamically created UDF) Y_ = User UDF Private Integer 2 See Security Fields on page 50. Owner_Id String 11 Yes See Security Fields on page 50. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 a. The 64-character limitation includes the prefix, so the actual table name is limited to 62 characters. The character limit is further reduced to 60 if queries are done from MS Access because MS Access surrounds table names with quotation marks, which count as two additional characters.

69 Chapter 4 61 UDF_Table_Item Table The UDF_Table_Item table includes the records for the items for table UDFs and Maximizer dropdown tables. Table 18 UDF_Table_Item Table Table Rules Read Rule Delete Rule Insert Rule Type_Id and Code_Id must exist: no list Update Rule Name field is updateable Table 19 UDF_Table_Item Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Unique Table_Id Type_Id Code_Id 3 Nonunique Name Table_Id Table 20 UDF_Table_Item_Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Table_Id Integer 2 Flag indicating type of record: 1 = Record defines a UDF or UDF folder 2 = Record defines a UDF table item

70 62 Maximizer CRM 10.5 Table 20 UDF_Table_Item_Table Fields (Continued) Type_Id Integer 2 Unique identifier of a userdefined field: = fields created by users > = constant values For a list of Type_Id constant values, refer to Table, User- Defined Field Type_Id Constants, on page 54.) Note: Many of these tables are not created until the first item has been added by a user in Maximizer. Code_Id Integer 2 0 = Name of the user-defined field Not 0 = Name of a table item in a table user-defined field Note: When the Code_Id is a value other than 0, and the Table_Id is 1, the Code_Id indicates the Type_Id of the parent folder. When the Code_Id is a value other than 0, and the Table _Id is 2, the records with the same Type_Id are all items belonging to the same table UDF. Name String 79 Name of Table Item. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

71 Chapter 4 63 Combined_Client_User_Fields Table The Combined_Client_User_Fields table is read-only and includes all the user-defined fields that have been created for clients. Note If you use this table for reporting, performance may be slow when reporting on large numbers of user-defined fields. Table 21 Combined_Client_User_Fields Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only Table 22 Combined_Client_User_Fields Table Index Definitions Index # Index Type Field 1 Field 2 1 Non- Unique Client_Id Contact_Number Table 23 Combined_Client_User_Fields Table Fields Client_Id String 23 Combined_Client_ Unique record ID. Contact_Number Integer 2 User_Fields.(Client_I d,contact_number) = Company.(Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Valid values:

72 64 Maximizer CRM 10.5 Address Book Entry Tables ABPartners Table on page 65 Address Table on page 66 Client Table on page 68 Company Table on page 74 People Table on page 77 Related_Entries Table on page 82 Address Book Table Relationships The following diagram shows how the Address Book tables are linked. The Notes, Hotlist, Address, Appointments, Combined_Client_User_ Defined_Fields, and User_Defined_Fields tables can be associated to either the Company or the People table or to both in order to access Company/Individual Contact data.the Company, People, and Address tables collectively make up the Client table. Figure 1 Address Book Table Relationships

73 Chapter 4 65 ABPartners Table The ABPartners table contains records for partners. Note The ABPartners table does not have any special table-level rules. Table 24 ABPartners Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Nonunique Client_Id Contact_Number 3 Nonunique Client_Id Contact_Number ABPartners_Id Table 25 ABPartners Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Client_Id Contact_Number String Integer 23 2 ABPartners. (Client_Id, Contact_Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Identifies the company or individual that has a partner associated with it. Can read and insert. Cannot delete or update. ABPartners_Id Long 4 Yes Reserved field. Always 0.

74 66 Maximizer CRM 10.5 Table 25 ABPartners Table Fields (Continued) Partner_Id Partner_Number String Integer 23 2 ABPartners. (Partner_Id, Partner_Number) = Company. (Partner_Id, Partner_Number) OR People. (Partner_Id, Partner_Number) Address Table Identifies the Address Book entry that is associated as a partner with the company or individual identified in the Client_Id/Contact_Number fields. Can read and insert. Cannot delete or update. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 The Address Table includes fields for the mailing address and alternative addresses. Table 26 Address Table Table Rules Read Rule Delete Rule Main address will be cleared and not deleted Insert Rule Update Rule Table 27 Address Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Non-Unique City 3 Non-Unique State_Province 4 Non-Unique Zip_Code 5 Non-Unique Firm 6 Unique Client_Id Address_Id

75 Chapter 4 67 Table 28 Address Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Record_Type String 2 Yes Type of Address Book record: 1 = Company 2 = Individual 41 = Alternate Address for Company or Company Contact 42 = Alternate Address for Individual or Individual Contact Owner_Id String 11 Yes See Security Fields on page 50. Private Integer 2 Yes See Security Fields on page 50. Client_Id String 23 Address.Client_Id = Company. (Client_Id) OR People.(Client_Id) Address_Id Integer 2 Address. (Client_Id, Address_Id) = Client. (Client_Id, Address_Id) Yes Unique identification number for a company or individual. Must exist in the Company table or the People table. Mandatory field. Nonmodifiable. Note: Address (Client_Id, Address_Id) must be unique when creating record. System-generated unique address identification number. 0 = Main address 60,000 or a = alternate address Non-modifiable. Name String 59 Description of Address. Mandatory field. Last_Modify_Dat e Last_Modify_Tim e DateString 10 Yes See History Fields on page 51. TimeString 11 Yes

76 68 Maximizer CRM 10.5 Table 28 Address Table Fields (Continued) Transfer_Date DateString 10 Date and time when the Transfer_Time TimeString 11 Address was transferred. If left empty, defaults to the system clock. Department String 39 Firm String 59 Company name. Applicable only if Record_Type is 2 or 42 Division String 39 Address_Line_1 String 39 Address_Line_2 String 39 City String 39 State_Province String 39 Country String 39 Zip_Code String 19 Change_Bits_Low Long 4 MaxMerge change fields. Used by Maximizer. Do not Change_Bits_Hig Long 4 use. h Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Read_Id String 12 See Security Fields on ReadPriv Integer 2 page 50. a. The ODBC driver converts unsigned integers (e.g., 60,000) to signed integers (e.g., -5536). You can convert the signed integers to their unsigned equivalents using the constant For example, = Client Table The Client table is a read-only table that contains information about Company, Individual, and Contact Address Book entries and encompasses the Company, People, and Address tables. This table is useful for reporting purposes. Table 29 Client Table Table Rules Read Rule only

77 Chapter 4 69 Table 29 Client Table Table Rules (Continued) Delete Rule only Insert Rule only Update Rule only Table 30 Client Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique 3 Non- Unique 4 Non- Unique 5 Non- Unique 6 Non- Unique 7 Non- Unique Name_Type City State_Province Zip_Code Firm Reverse_Phone_1 Name 8 Unique Client_Id Contact_Number Table 31 Client Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er

78 70 Maximizer CRM 10.5 Table 31 Client Table Fields (Continued) Record_Type String 2 Company. Record_Type OR People. Record_Type Yes Type of record: 1 = Company 2 = Individual 5 = Default Entries 31 = Company Contact 32 = Individual Contact 41 = Company or Company Contact Alternate Address 42 = Individual or Individual Contact Alternate Address Owner_Id String 11 Yes See Security Fields on page 50. Private Integer 2 Yes See Security Fields on page 50. Client_Id String 23 Yes Unique identification number of the Company, Individual, Contact, Alternate Address, or Default Entry. Contact_Number Integer 2 Yes 0 = Company or Individual <60,000 or <-5536 a = Contact 60,000 or = Alternate address Name_Type String 1 Yes C = Company I = Individual or Contact Name String 59 Yes Name of Company, or Last name of Individual or Contact. Address_Id Integer 2 Client. (Client_Id, Address_Id) = Address. (Client_Id, Address_Id) Yes System-generated unique address identification number. Points to the address to use for the Address Book entry. 0 = Main address 60,000 or a = alternate address Non-modifiable.

79 Chapter 4 71 Table 31 Client Table Fields (Continued) Last_Modify_Dat e Last_Modify_Tim e DateString 10 Yes See History Fields on page 51. TimeString 11 Yes Transfer_Date DateString 10 Yes Date and time when the last Transfer_Time TimeString 11 Yes transfer occurred. Highest_Alt_Add _Number Integer 2 Yes Highest alternate address number in use. Phone_1 String 21 Yes Reverse_Phone_1 String 21 Yes Phone_1_ Extension String 21 Yes Phone_2 String 21 Yes Reverse_Phone_2 String 21 Yes Phone_2_ Extension String 21 Yes Phone_3 String 21 Yes Reverse_Phone_3 String 21 Yes Phone_3_ Extension String 21 Yes Phone_4 String 21 Yes Reverse_Phone_4 String 21 Yes Phone_4_ Extension Highest_Contact_ No String 21 Yes Integer 2 Yes Highest Contact_Number in use.

80 72 Maximizer CRM 10.5 Table 31 Client Table Fields (Continued) Receives_Letters Integer 2 People. Receives_Letters Use_Client_Name Integer 2 Client. Use_Client_Name = People. Use_Client_Name Yes Yes Indicates whether contact (Record_Type = 31 or 32) receives mail sent to the Company/Individual: 0 = Contact doesn t receive mail sent to Company/ Individual 1 = Contact receives mail sent to Company/ Individual Note: For Individual records (Record_Type = 2), this value is always 1. For Company records (Record_Type = 1) and Alternate Addresses (Record_Type = 41 or 42), this value is always 0. Applies to Contacts (Record_Type = 31 or 32) only. Indicates whether the Contact s Company/ Individual name should be included in the address: 0 = Do not include Company/ Individual name in address 1 = Include Company/ Individual name in address First_Name String 39 Yes Applies to Individuals and Initial String 39 Yes Contacts only (Record_Type = 2, 31, or 32). Mr/Ms String 39 Yes Title String 59 Yes Salutation String 39 Yes Department String 39 Yes Firm String 59 Yes Applies to Individuals (Record_Type = 2) only.

81 Chapter 4 73 Table 31 Client Table Fields (Continued) Division String 39 Yes Address_Line_1 String 39 Yes Address_Line_2 String 39 Yes City String 39 Yes State_Province String 39 Yes Country String 39 Yes Zip_Code String 19 Yes Change_Bits_Low Long 4 Yes MaxMerge change fields. Used by Maximizer. Do not Change_Bits_Hig Long 4 Yes use. h Last_Client_Id String 23 Yes Last Client ID used for transfer. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Assigned_To String 11 User_Details. User_Id Yes Phone_1_Desc String 21 Yes Phone_2_Desc String 21 Yes Phone_3_Desc String 21 Yes Phone_4_Desc String 21 Yes _1_Desc String 15 Yes _2_Desc String 15 Yes _3_Desc String 15 Yes User_Id of user assigned to the Address Book entry as the Account Manager. Applies to Company (Record_Type = 1), Individual (Record_Type = 2), and Default Entry (Record_Type = 5) records only.

82 74 Maximizer CRM 10.5 Table 31 Client Table Fields (Continued) Reports_To Long 4 Client. Reports_To = People. Reports_To Company Table The Company table includes fields for Company Address Book entries. Yes Partner_Id Partner_Number String Integer 23 2 Client.(Partner_Id,Partner_Number ) = ABPartners. (Partner_Id, Partner_Number) Yes Yes Contact_Number of Contact (Record_Type = 31 or 32) to whom this contact reports (e.g., contact s supervisor or manager). Applies only to Contact records (Record_Type = 31 or 32). Identifies the Address Book entry that is a partner to the company or individual. Lead_Status Integer 2 Yes 0 = Not sales lead 1 = Sales lead Applies to Company (Record_Type = 1) and Individual (Record_Type = 2) records only. Read_Id String 11 See Security Fields on ReadPriv Integer 2 page 50. a. The ODBC driver converts unsigned integers (e.g., 60,000) to signed integers (e.g., -5536). You can convert the signed integers to their unsigned equivalents using the constant For example, = Table 32 Company Table Table Rules Read Rule Delete Rule Any records that use the same Client_Id will be deleted Insert Rule Update Rule

83 Chapter 4 75 Table 33 Company Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique 3 Non- Unique Name_Type Reverse_Phone_1 Company_Name 4 Unique Client_Id Contact_Number Table 34 Company Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Record_Type String 2 Yes Type of record: 1 = Company Always 1 for records in Company table. Owner_Id String 11 Yes See Security Fields on page 50. Private Integer 2 See Security Fields on page 50. If modified will also modify all contacts and addresses with the same Client_Id. Client_Id String 23 Company. (Client_Id, Contact_Number) = Client.(Client_Id, Contact_Number) Unique identification number. System generated if Null and System to assign ID numbers is checked. Must be unique. Non-modifiable. Contact_Number Integer 2 Yes Always 0 for records in the Company table. Name_Type String 1 Yes Always C (i.e., Company) for records in the Company table. Company_Name String 59 Mandatory field.

84 76 Maximizer CRM 10.5 Table 34 Company Table Fields (Continued) Address_Id Integer 2 Company. (Client_Id, Address_Id) = Address. (Client_Id, Address_Id) Last_Modify_Dat e Last_Modify_Tim e Yes System-generated unique address identification number. Points to the address to use for the Address Book entry. 0 = Main address 60,000 or a = alternate address Non-modifiable. DateString 10 See History Fields on page 51. TimeString 11 Transfer_Date DateString 10 Date and time of transfer. If Transfer_Time TimeString 11 left empty, defaults to the system clock. Phone_1 String 21 Reverse_Phone_1 String 21 Yes Phone_1_ Extension String 21 Phone_2 String 21 Reverse_Phone_2 String 21 Yes Phone_2_ Extension String 21 Phone_3 String 21 Reverse_Phone_3 String 21 Yes Phone_3_ Extension String 21 Phone_4 String 21 Reverse_Phone_4 String 21 Yes Phone_4_ Extension String 21 Change_Bits_Low Long 4 MaxMerge change fields. Used by Maximizer. Do not Change_Bits_Hig Long 4 use. h

85 Chapter 4 77 Table 34 Company Table Fields (Continued) Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Assigned_To String 11 User_Details. User_Id Phone_1_Desc String 21 Phone_2_Desc String 21 Phone_3_Desc String 21 Phone_4_Desc String 21 _1_Desc String 15 _2_Desc String 15 _3_Desc String 15 People Table Yes Partner_Id Partner_Number String Integer 23 2 Company. (Partner_Id, Partner_Number) = ABPartners. (Partner_Id, Partner_Number) Yes Yes The People table includes fields for Individual entries and Contacts. User_Id of user assigned to the Address Book entry as the Account Manager. Identifies the Address Book entry that is a partner to the company or individual. Lead_Status Integer 2 Yes 0 = Not sales lead 1 = Sales lead Read_Id String 11 See Security Fields on ReadPriv Integer 2 page 50. a. The ODBC driver converts unsigned integers (e.g., 60,000) to signed integers (e.g., -5536). You can convert the signed integers to their unsigned equivalents using the constant For example, = Table 35 People Table Table Rules Read Rule Delete Rule Any records that use the same Client_Id and Contact_Number will be deleted

86 78 Maximizer CRM 10.5 Table 35 People Table Table Rules (Continued) Insert Rule Update Rule Table 36 People Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique 3 Non- Unique Name_Type Reverse_Phone_1 Last_Name 4 Unique Client_Id Contact_Number Table 37 People Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Record_Type String 2 Client. Record_Type Yes Type of record: 2 = Individual 31 = Company Contact 32 = Individual Contact Owner_Id String 11 Yes See Security Fields on page 50. Private Integer 2 0 = Public (any user may view the record) 1 = Private (only the user or group specified in the Owner_Id field may view or modify the record)

87 Chapter 4 79 Table 37 People Table Fields (Continued) Client_Id String 23 People. (Client_Id, Contact_Number) = Client. (Client_Id, Contact_Number) Unique identification number. System generated if Null and System to assign ID numbers is checked. If a contact, the Company/ Individual must already exist. Non-modifiable. (Client_Id, Contact_Number) must be unique. Contact_Number Integer 2 Unique identification number. Non-modifiable. (Client_Id, Contact_Number) must be unique. Valid values: = Individual = Contact. Name_Type String 1 Yes Always I (uppercase i). Last_Name String 59 Mandatory field. Address_Id Integer 2 People. (Client_Id, Address_Id) = Address. (Client_Id, Address_Id) Department String 80 Yes System-generated unique address identification number. Points to the address to use for the Address Book entry. Nonmodifiable. 0 = Main address 60,000 or a = alternate address Firm String 80 The Company Name of an Individual record. Applies to Individuals (Record_Type = 2) only. Division String 80 Last_Modify_Dat e Last_Modify_Tim e DateString 10 See History Fields on page 51. TimeString 11

88 80 Maximizer CRM 10.5 Table 37 People Table Fields (Continued) Transfer_Date DateString 10 Date and time of transfer. If Transfer_Time TimeString 11 left empty defaults to the system clock. Phone_1 String 21 Reverse_Phone_1 String 21 Yes Phone_1_ Extension String 21 Phone_2 String 21 Reverse_Phone_2 String 21 Yes Phone_2_ Extension String 21 Phone_3 String 21 Reverse_Phone_3 String 21 Yes Phone_3_ Extension String 21 Phone_4 String 21 Reverse_Phone_4 String 21 Yes Phone_4_ Extension String 21 Receives_Letters Integer 2 People. Receives_Letters = Client. Receives_Letters Indicates whether contact or individual receives mail sent to the Company: 0 = Contact or Individual doesn t receive mail sent to Company 1 = Contact or Individual receives mail sent to Company Note: For Individuals (Record_Type = 2), this value is always 1.

89 Chapter 4 81 Table 37 People Table Fields (Continued) Use_Client_Name Integer 2 People. Use_Client_Name = Client. Use_Client_Name First_Name String 39 Initial String 39 Mr/Ms String 39 Title String 59 Salutation String 39 Applies to Individuals (Record_Type = 2) and Contacts (Record_Type = 31 or 32) only. Indicates whether the individual or Contact s Company name should be included in the address: 0 = Do not include Company name in address 1 = Include Company name in address Change_Bits_Low Long 4 MaxMerge change fields. Used by Maximizer. Do not Change_Bits_Hig Long 4 use. h Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Assigned_To String 11 User_Details. User_Id Phone_1_Desc String 21 Phone_2_Desc String 21 Phone_3_Desc String 21 Phone_4_Desc String 21 _1_Desc String 15 _2_Desc String 15 Yes User_Id of user assigned to the Address Book entry as the Account Manager. Applies to Individual (Record_Type = 2) records only.

90 82 Maximizer CRM 10.5 Table 37 People Table Fields (Continued) _3_Desc String 15 Reports_To Long 4 People. Reports_To = Client. Reports_To Related_Entries Table The data in the Related_Entries table contains all the attributes pertaining to Related Entries. Yes Partner_Id Partner_Number String Integer 23 2 People. (Partner_Id, Partner_Number) = ABPartners. (Partner_Id, Partner_Number) Yes Yes Contact_Number of Contact (Record_Type = 31 or 32) to whom this contact reports (e.g., contact s supervisor or manager). Applies only to Contact records (Record_Type = 31 or 32). Identifies the Address Book entry that is a partner to the individual. Lead_Status Integer 2 Yes 0 = Not sales lead 1 = Sales lead Applies to Individual (Record_Type = 2) records only. Read_Id String 11 See Security Fields on ReadPriv Integer 2 page 50. a. The ODBC driver converts unsigned integers (e.g., 60,000) to signed integers (e.g., -5536). You can convert the signed integers to their unsigned equivalents using the constant For example, = Note The Related_Entries table does not have any special table-level rules. Table 38 Related_Entries Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique Related_Entries_Id Related_Entries_Number

91 Chapter 4 83 Table 38 Related_Entries Table Index Definitions (Continued) Index # Index Type Field 1 Field 2 Field 3 3 Non- Unique Related_Entries_Id Related_Entries_Number Related_Entries_Id Table 39 Related_Entries Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Related_To_Id String 23 Related_Entries. (Related_To_Id, Related_To_ Integer 2 Related_To_ Number Number) = Company. (Client_Id, Contact_Number) OR People. (Client.ID, Contact_Number) Related_Entries_I d Client_Id and Contact_Number of the Address Book entry that has another entry or entries related to it. Mandatory field. Non-modifiable. Long 4 Yes Unique identifier of the related entry record. Related_From_Id String 23 Related_Entries. (Related_From_Id Related_From_ Integer 2, Number Related_From_ Number) = Company. (Client_Id, Contact_Number) OR People.(Client.ID, Contact_Number) Client_Id and Contact_Number of Address Book entry related to the entry identified in Related_To_Id. Must exist in the Company or People table. Mandatory field. Nonmodifiable. Desc String 253 Description of the relationship. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

92 84 Maximizer CRM 10.5 Table 39 Related_Entries Table Fields (Continued) Relationship_Typ e_id Relationship_ Type_Number String 23 If null, this number is system generated. If populated, the ID numbers are checked. Must be unique. Modifiable. Link to system UDF table by using the value: (i.e., ) as the Type_Id. Integer 2 Always 0.

93 Chapter 4 85 Appointment, Hotlist, and Notes Tables Appointments Table on page 85 Hotlist Table on page 90 Notes Table on page 93 Appointments Table The Appointments table includes both personal and company-related appointments. Table 40 Appointments Table Table Rules Read Rule Delete Rule Insert Rule Update Rule Owner_Id only updated by MASTER Table 41 Appointments Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 1 Unique Data_Machine_I d 2 Non- Unique 3 Non- Unique 4 Non- Unique Client_Id Sequence_ Number Contact_Numbe r App_Date App_Time Owner_Id Alert_Flag Lead_Date Lead_Time Owner_Id App_Date App_Time Table 42 Appointments Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Owner_Id String 11 Yes User, location, or resource the appointment belongs to.

94 86 Maximizer CRM 10.5 Table 42 Appointments Table Fields (Continued) App_Date DateString 10 Appointment date and time. App_Time TimeString 11 Mandatory field. Lead_Date DateString 10 Alarm date and time. If left Lead_Time TimeString 11 empty, defaults to the App_Date and App_Time. End_Date DateString 10 End date and time of End_Time TimeString 11 Appointment. End_Time cannot be less than the App_Time. If left empty, defaults to the App_Time. Client_Id Contact_Number String Integer 23 2 Appointments. (Client_Id, Contact_Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Client the appointment is with. If filled in, then must exist in the Company or People table. Nonmodifiable. Alert_Flag Integer 2 0 = Alarm not set 1 = Alarm set Priority String 3 Defines the priority text (e.g., Hi, MED, LOW). Completed Integer 2 0 = Incomplete 1 = Complete Icon_Type Integer 2 0 = None 1 = Mail 2 = ToDo 3 = Phone 4 = Travel 5 = Sale 6 = Meal 7 = Presentation 8 = Speech 9 = Meeting Note: Icons can be viewed when an Appointment is being created.

95 Chapter 4 87 Table 42 Appointments Table Fields (Continued) RSVP Integer 2 Yes User s response to appointment invitation: 0 = No response 1 = User accepts appointment 2 = Declined 3 = Tentative response Non-modifiable. Recurring_ID Integer 2 Yes Unique recurring ID: 0 = Non-recurring Other unique value = Identifier for records belonging to a recurring appointment Recurring_Freq Integer 2 Frequency of recurring appointment: 0 = Daily 1 = Weekly 2 = Day of month (e.g., first Monday) 3 = Monthly (e.g., 14th) 4 = Yearly

96 88 Maximizer CRM 10.5 Table 42 Appointments Table Fields (Continued) Occurence Integer 2 Identifies relative day of recurring appointment (e.g., second Tuesday). Applies to weekly, day of month, and monthly appointments only. Weekly appointments: 0 = Every 1 = Every second 2 = Every third = Every 26th Day of month appointments: 0 = Every 1st of the month 1 = Every 2nd of the month = Every Last of the month Monthly appointments: 0 = First of the month 1 = Second of the month 2 = Third of the month 3 = Fourth of the month 4 = Last of the month Note: This field is spelled as it appears here (i.e., Occurence and not Occurrence ).

97 Chapter 4 89 Table 42 Appointments Table Fields (Continued) Day_Of_Week Integer 2 Day of recurring appointment (e.g., Friday). Applies to weekly, day of month, and monthly appointments only. Weekly and Monthly appointments: 0 = Sunday 1 = Monday 2 = Tuesday 3 = Wednesday 4 = Thursday 5 = Friday 6 = Saturday Day of month appointments: 0 = Day 1 = Weekday Skip_Weekend Integer 2 Applies to daily appointments only. 0 = Default 1 = Daily appointments do not occur on weekends. Move_To_ Weekday Integer 2 Applies to yearly appointments only. 0 = Default 1 = If appointment occurs on a weekend, move to nearest weekday. Start_Date DateString 10 Appointment start date. End_Date DateString 10 Appointment end date. Peg_Board_State Integer 2 Peg Board state when an appointment occurs: 0 = Unknown 1 = Busy 2 = Out (Default) Text String 119 Text of Appointment. Mandatory field.

98 90 Maximizer CRM 10.5 Table 42 Appointments Table Fields (Continued) Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Private Integer 2 See Security Fields on page 50. Hotlist Table The Hotlist table includes both personal and company related tasks. Note The Hotlist table does not have any special table-level rules. Table 43 Hotlist Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 1 Unique Data_ Machine _Id Sequence _Number 2 Non- Unique Owner_ Id Client_Id Contact _ Number Entry_ Type Type_Id Original _Date Original _Time 3 Non- Unique Owner_ Id Complet ed Schedul e_date Schedul e_time 4 Non- Unique Client_I d Contact_ Number Schedul e_date Schedul e_time 5 Unique Opp_Id Opp_ Number Step_Id Activity_ Id 6 Non- Unique Owner_ Id Schedule _Date Schedul e_time 7 Non- Unique Owner_ Id Alarm Lead_ Date Lead_ Time

99 Chapter 4 91 Table 44 Hotlist Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Owner_Id String 11 Yes User or group who owns the record. If originated from OppActivity, it is the Owner_Id of the Team Member responsible for the opportunity. Defaults to the current Login ID. Schedule_Date DateString 10 Date and time when task Schedule_Time TimeString 11 was scheduled. Mandatory field. Client_Id String 23 Hotlist. (Client_Id, Contact_Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Client ID with which the task is associated. Leave empty for a personal appointment. Otherwise it must already exist in the Company or People table. Nonmodifiable. Contact_Number Integer 2 Contact number with which the task is associated. Leave empty for a personal appointment. Otherwise it must already exist in the Company or People table. Non-modifiable. Contact_Number = Entry_Type Integer 2 Source of the task: 0 = Manual task 3 = Date from a date user field table Original_Date DateString 10 Original date and time of Original_Time TimeString 11 task. If left empty, defaults to the system clock. Type_Id Integer 2 Pointer to date field in the UDF_List table. Nonmodifiable. Priority String 3 Priority of task.

100 92 Maximizer CRM 10.5 Table 44 Hotlist Table Fields (Continued) Completed Integer 2 0 = Incomplete 1 = Complete Opp_Id String 23 Hotlist.(Opp_Id, Identifier of the associated Opp_Number Integer 2 Opp_Number, opportunity related to the Step_Id, OppActivity from which the Activity_Id) = OppActivity. (Opp_Id, task originated. Must already exist in the OppActivity table. Opp_Number, Step_Id Long 4 Identifier of the OppActivity Step_Id, from which the task Activity_Id) originated. Must already exist in the OppActivity table. For Follow-up activities, may not exist in the OppActivity table. Activity_Id Long 4 Identifier of the OppActivity from which the task originated. Must already exist in the OppActivity table. Alarm Integer 2 0 = No alarm 1 = Alarm Icon_Type Integer 2 Icon associated with the Hotlist task: 0 = None 1 = Mail 2 = ToDo 3 = Phone 4 = Travel 5 = Sale 6 = Meal 7 = Presentation 8 = Speech 9 = Meeting Note: Icons can be viewed when a Hotlist task is created.

101 Chapter 4 93 Table 44 Hotlist Table Fields (Continued) Lead_Date DateString 10 Date and time when alarm Lead_Time TimeString 11 will occur. If left empty, defaults to Schedule_Date and Schedule_Time. End_Time TimeString 11 Task end time. Greater than or equal to Schedule_Time. If left empty, defaults to system clock s time. Text String 119 Text of the Hotlist item. Mandatory field. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Notes Table The Notes table includes history and Notes that are created for Companies/Individuals and Contacts. Note The Notes table does not have any special table-level rules. Table 45 Notes Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 Field 5 1 Unique Data_ Machine_Id 2 Non- Unique 3 Non- Unique 4 Non- Unique 5 Non- Unique Date Sequence_ Number Time Type Date Time Client_Id Client_Id Contact_ Number Contact_ Number Date Time Type Date Time

102 94 Maximizer CRM 10.5 Table 46 Notes Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Creator_Id String 11 Yes See History Fields on page 51. Client_Id Contact_Number String Integer 23 2 Notes.(Client_Id, Contact_Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) OR Opportunity.(Op p_id,opp_numbe r) Client_Id/Contact_Number the Note is associated with. Valid values for Contact_Number: Associated Company or Person record must already exist. Mandatory field. Nonmodifiable. Must provide Client_Id/Contact_Number to insert. Cannot update.

103 Chapter 4 95 Table 46 Notes Table Fields (Continued) Type a Integer 2 Flag indicating how the note was generated. Standard Maximizer note types may be specified as well as user-defined note types. Range: 0-32,767 0 = Manual note 1 = Mail-out note 2 = Phone call note 3 = Timed note 4 = Transfer note 5 = Completed task or appointment 6 = Scheduled task or appointment 7 = sent note 8 = Opportunity created or opportunity status changes 9 = History note 10 = Reassign task note 11 = Reserved for future use 12 = Customer Service Can insert. Can update. Date DateString 10 Yes See History Fields on Time TimeString 11 page 51. Text Memo n/a Mandatory field. Must be less than or equal to 9,215 characters. Must provide Text to insert. Can insert Can update. Private Integer 2 See Security Fields on page 50. Owner_Id String 11 Yes See Security Fields on page 50.

104 96 Maximizer CRM 10.5 Table 46 Notes Table Fields (Continued) Note_Type String 19 Within Maximizer, this string is used only for display purposes to indicate a subtype of note. If a standard type is defined in the Type field, this string is appended to the standard type name for display. In Maximizer, this field appears as Category on the Note dialog box for manual notes only. Can insert. Can update. Entity_Type Integer 2 Type of parent record the note belongs to. Entity_Type values correspond to the Client_Id/Contact_Number. Cannot update. See the footnote. b 0 = Not specified 1 = Address Book entry 2 = Opportunity 3 = Campaign 4 = User 5 = Customer Service case 6 = Knowledge Base 7 = Order 8 = Order Item 9 = Default Entry 100 = Custom Independent 101 = Custom Child Read_Id String 11 See Security Fields on ReadPriv Integer 2 page 50. a. Some Maximizer functions, such as purging, searching, and MaxExchange synchronization, do not support user-defined note types, which have a Type value greater than 17. b. If the Client_Id/Client_Number matches more than one parent type, the Entity_Type will be inserted according to the following priority: 1-Address Book entry, 2-Opportunity or Campaign, 3-Customer Service case, 4-Custom

105 Chapter 4 97 Campaign Tables Automatic_Campaign Table on page 98 CampaignAccounts Table on page 100 Combined_Campaign_User_Fields Table on page 102 Manual_Campaign Table on page 103 Figure 2 Traditional Campaign Table Relationships Figure 3 Automatic Campaign Table Relationships

106 98 Maximizer CRM 10.5 Automatic_Campaign Table This table contains information for Automated Campaigns in Maximizer. Table 47 Read Rule Delete Rule Insert Rule Update Rule Automatic_Campaign Table Table Rules Deletes entire record tree, including any Notes, Hotlist tasks, Link records, etc.), if there are any Table 48 Automatic_Campaign Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Unique Opp_Id Opp_Number 3 Nonunique Strategy_Id Table 49 Automatic_Campaign Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id String 23 Unique identifier of an Automated Campaign. System generated. Opp_Number Integer 2 Not applicable to Automated Campaigns. Always 0. Owner_Id String 11 Yes Team member that is chosen as the Opportunity leader. If Team ID is equal to -1 (no Team is assigned i.e., this is a Personal Opportunity) then defaults to Login ID. Strategy_Id Long 4 Identifies the automated campaign template.

107 Chapter 4 99 Table 49 Automatic_Campaign Table Fields (Continued) Team_Id Integer 2 Always (single user). Mandatory field. Status Integer 2 Status of the Campaign: 0 = New 1 = In Progress 2 = In Progress New 3 = Completed 5 = Abandoned 6 = Suspended Name String 79 Name of the campaign. Objective String 253 Name of the template used for the Campaign. Probability_ Closing Integer 2 Always 0. Actual_Revenue Double 8 Actual revenue generated by the Campaign. Applicable only if Status = 3. Cost Double 8 Campaign Budget. Forecast_Revenu e Double 8 Revenue expected from Campaign once it is successfully complete. the Campaign Leader or MASTER user can modify this field. Start_Date String 10 Date when the campaign was started. Default is the current system date when campaign was created. Estimated_Close_ Date String 10 Not in use. Close_Date String 10 Actual close date of the Campaign. Must be greater than Start_Date. the Campaign Leader or MASTER user can modify this field. Last_Modify_Dat e String 10 See History Fields on page 51.

108 100 Maximizer CRM 10.5 Table 49 Automatic_Campaign Table Fields (Continued) Comment Memo n/a Description of the campaign. Completion_ Comment CampaignAccounts Table Memo n/a Comment associated with the completion details of the campaign. Creator_Id String 11 Yes See History Fields on Creation_Date String 10 Yes page 51. Creation_Time String 11 Suspended_Date String 10 Not in use. Days_Suspended Long 4 Always 0. Rec_Type Integer 2 Type of automated campaign record: 10 = Automated /fax campaign 15 = Recurring automated /fax campaign 20 = Recurring automated /fax campaign initiated from a 121 Designer web experience The CampaignAccounts table creates the link between automated campaigns and their subscribers (Address Book entries). Note The CampaignAccounts table does not have any special table-level rules. Table 50 CampaignAccounts Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Nonunique CampID ClientID ContactNo

109 Chapter Table 51 CampaignAccounts Table Fields CampID String 23 CampaignAccoun ts.campid = Automatic_Camp aign.opp_id Unique identifier of the campaign. Insert only a ClientID ContactNo String Long 23 4 CampaignAccoun ts.(client_id, ContactNo) = Client. (Client_Id, Contact_Number) Client_Id and Contact_Number of Address Book entries subscribed to the campaign. Insert only a StartDate String 10 Date when the Address Book entry was subscribed to the campaign. NextDate String 10 Date when the next campaign activity for the Address Book entry should be processed. Applies to ongoing campaigns. AccStatus Long 4 Status of the campaign activity for this subscriber: 1 = New 2 = In Progress 3 = Complete 4 = Retry 5 = Unsubscribed ("Do not solicit by" field on Address Book entry) 6 = Suspended by service due to fatal errors 16 = Manually suspended 99 = Failed The following Status codes apply to test campaign activities only: 7 = New test 102 = Test in progress 8 = Test complete 103 = Retry test 9 = Test manually suspended 105 = Test unsubscribed 100 = Test failed

110 102 Maximizer CRM 10.5 Table 51 CampaignAccounts Table Fields (Continued) ActCount Long 4 Next campaign activity to process for the Address Book entry. ActFlag Long 4 Not in use. a. Insert operations are allowed, but not delete and update operations. Combined_Campaign_User_Fields Table This table contains the values of the user-defined fields for each automatic or manual campaign. Each user-defined field is listed as a field in this table, prefixed by W_. Note If you use this table for reporting, performance may be slow when reporting on large numbers of user-defined fields. Table 52 Combined_Campaign_User_Fields Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only Table 53 Combined_Campaign_User_Fields Table Index Definitions Index # Index Type Field 1 Field 2 1 Nonunique Opp_Id Opp_Number

111 Chapter Table 54 Combined_Campaign_User_Fields Table Fields Opp_Id Opp_Number String Integer 23 2 Combined_Camp aign_user_fields. (Opp_Id, Opp_Number = Automatic_Camp aign.(opp_id, Opp_Number) OR Manual_Campaig n.(opp_id, Opp_Number) Yes Yes Identifies the automatic or manual campaign that the user-defined field values belong to. Manual_Campaign Table The Manual_Campaign table contains information for traditional (manual) campaigns in Maximizer. Table 55 Read Rule Delete Rule Insert Rule Update Rule Manual_Campaign Table Table Rules Deletes entire record tree, including any Notes, Hotlist tasks, Link records, etc.), if there are any Table 56 Manual_Campaign Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Unique Opp_Id Opp_Number 3 Nonunique Strategy_Id

112 104 Maximizer CRM 10.5 Table 57 Manual_Campaign Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id String 23 Unique identifier of a Traditional Campaign. System generated. Opp_Number Integer 2 Always 0. Owner_Id String 11 Yes Team member that is chosen as the Opportunity leader. If Team ID is equal to -1 (no Team is assigned i.e., this is a Personal Opportunity) then defaults to Login ID. Strategy_Id Long 4 Manual_Campaig n.strategy_id = Strategy. Strategy_Id Team_Id Integer 2 Manual_Campaig n.team_id = Team.Team_Id Unique identification number of the strategy from the Strategy table. Unique identification number of the team from the Team table. Status Integer 2 Status of the Campaign: 0 = New 1 = In Progress 2 = In Progress New 3 = Completed 5 = Abandoned 6 = Suspended Name String 79 Name of the campaign. Objective String 253 Objective of the campaign. Reason_Id Long 4 Reason why the Campaign was Completed, Abandoned, or Suspended. Modifiable only by the Campaign Leader or MASTER. Blank = Campaign still In Progress Probability_ Closing Integer 2 Always 0.

113 Chapter Table 57 Manual_Campaign Table Fields (Continued) Actual_Revenue Double 8 Actual revenue generated by the Campaign. Applicable only if Status = 3. Cost Double 8 Budget for the campaign. Forecast_Revenu e Double 8 Revenue expected from Campaign once it is successfully complete. Modifiable only by the Campaign Leader or MASTER. Start_Date String 10 Date when the campaign was started. Default is the current system date when campaign was created. Estimated_Close_ Date String 10 Not in use. Close_Date String 10 Actual close date of the Campaign. Updated as the Campaign s steps are applied before or ahead of schedule. Must be greater than Start_Date. Modifiable only by the Campaign Leader or MASTER. Last_Modify_Dat e String 10 See History Fields on page 51. Comment Memo n/a Description of the campaign. Completion_ Comment Memo n/a Comment associated with the completion details of the campaign. Creator_Id String 11 Yes See History Fields on Creation_Date String 10 Yes page 51. Creation_Time String 11 Suspended_Date String 10 Not in use. Days_Suspended Long 4 Always 0.

114 106 Maximizer CRM 10.5 Customer Service Tables Combined_CSCase_User_Fields Table on page 106 CSCases Table on page 107 Figure 4 Customer Service Table Relationships Combined_CSCase_User_Fields Table The Combined_CSCase_User_Fields table is read-only and includes all the User-Defined Fields that have been created for customer service cases. Note If you use this table for reporting, performance may be slow when reporting on large numbers of user-defined fields. Table 58 Combined_CSCase_User_Fields Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only Table 59 Combined_CSCase_User_Fields Table Index Definitions Index # Index Type Field 1 Field 2 1 Nonunique Case_Id Case_Number

115 Chapter Table 60 Combined_CSCase_User_Fields Table Fields Case_Id String 23 Combined_CSCas Yes Unique record ID. Case_Number Integer 2 e_user_fields. (Case_Id, Case_Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Yes Always 0. CSCases Table This table contains the information for customer service cases. Note The CSCases table does not have any special table-level rules. Table 61 CSCases Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Unique Case_Id Case_Number 3 Nonunique 4 Nonunique 5 Nonunique 6 Nonunique 7 Nonunique Client_Id Assign_To_Id Deadline_Date Status Priority Client_Number Deadline_Time Severity 8 Nonunique RecType Case_Id Case_Number

116 108 Maximizer CRM 10.5 Table 62 CSCases Table Fields Data_Machine_Id Long 4 See Identity Fields on Sequence_Numb Long 4 page 50. er Case_Id String 23 Unique customer service case Case_Number Integer 2 identifier. Client_Id Client_Number String Integer 23 2 CSCases. (Client_ID, Client_Number) = Client. (Client_Id, Contact_Number) Contact_Id Contact_Number String Integer 23 2 CSCases. (Contact_Id, Contact_Number) = Client.(Client_Id, Contact_Number) to client. to default contact. Status Integer 2 Case status: = Unassigned = Assigned = Escalated = Callback = WaitCustomer = Cancelled = Resolved Pointer to value in system UDFs (60041/-5495). Priority Integer 2 Case priority: = Low = Medium = High Severity Integer 2 Case severity: = Low = Medium = High Type Integer 2 Case type. Pointer to value in system UDFs (60022/-5514).

117 Chapter Table 62 CSCases Table Fields (Continued) Reason Integer 2 Case reason. Pointer to value in system UDFs (60023/- 5513). Origin Integer 2 Case origin. Pointer to value in system UDFs (60024/- 5512). Category Integer 2 No longer in use. Product Integer 2 No longer in use. Fee Double 8 Case fee. FeeType Integer 2 Case fee type. Pointer to value in system UDFs. Assigned_To_Id String 11 User_Details. User_Id Yes User_Id of user who the case is assigned to. Deadline_Date DateString 10 Follow-up deadline date and Deadline_Time TimeString 11 time. Creator_Id String 11 Yes See History Fields on Create_Date DateString 10 Yes page 51. Create_Time TimeString 11 Modified_By_Id String 11 User ID of the user who most recently changed the record. Last_Modify_Dat e Last_Modify_Tim e DateString 10 See History Fields on page 51. TimeString 11 Owner_Id String 11 Yes See Security Fields on page 50. Private Integer 2 See Security Fields on page 50. Solution_Id String 23 For resolved cases, it points Solution_Number Integer 2 to a Knowledge Base article with the case solution. Subject String 127 Subject line of the case. Queue Integer 2 Pointer to value in system UDFs (60029/-5507).

118 110 Maximizer CRM 10.5 Table 62 CSCases Table Fields (Continued) RecType Integer 2 0 = Customer Service Case 1 = Customer Service User ArticleNumber String 23 This field is intended for remote users who don t have access to the Knowledge Base database but know the article number for this case in the main database. The remote user fills in this field manually, and when the case is synchronized with the main database, it will reference the article in the Knowledge Base. NotifyFlag Integer 2 Customer service case notification flag: 0 = Notification disabled 1 = Notification sent to default list of users 2 = Notification sent to custom list of users Resolved_By_Id String 11 User_Details. User_Id User ID of the user who resolved the case. Resolved_Date DateString 10 Date and time when the case Resolved_Time TimeString 11 was resolved. Case_Owner_Id String 11 User_Details. User_Id User who owns the case. Description Memo n/a Description of the case. BillRate Integer Cost per hour of billable time. BillableTime Integer Number of billable hours.

119 Chapter Opportunity Tables Activity Table on page 115 Combined_Opp_User_Fields Table on page 117 Currency Table on page 118 OppActivity Table on page 119 OppComp Table on page 123 OppContact Table on page 125 Opportunity Table on page 127 OppPartners Table on page 131 OppRole Table on page 133 OppStep Table on page 135 OppSuccessFactor Table on page 137 Prob_Close_Range Table on page 138 Reasons Table on page 140

120 112 Maximizer CRM 10.5 Opportunity Table Relationships The following diagram shows how the Opportunity table and its related tables are linked to the contact management tables. Figure 5 Opportunity Management Table Relationships

121 Chapter The following diagram shows how the Strategy_Success_Factor_Link table is linked to both the OppSuccessFactor table and the Opportunity table. Figure 6 OppSuccessFactor Table Relationships The following diagram shows how the Strategy_Role_Link table is linked to the Opportunity and OppRole tables. Figure 7 OppRole Table Relationships

122 114 Maximizer CRM 10.5 The following diagram shows how the Strategy_Step_Link table is linked to the Opportunity and OppStep tables. Figure 8 OppStep Table Relationships The following diagram shows how associated tables are related to the OppActivity table. Figure 9 OppActivity Table Relationship

123 Chapter The following diagram shows how the OppContact table is linked to the Company and People tables. Figure 10 OppContact Table Relationships Activity Table The data in the Activity table contains all the attributes pertaining to the Activity entity in the Strategy Library. The attributes describe the default settings of an activity that is to be linked to one or more Step entities (linked via the Step_Activity_Link record) in the Strategy Library. Once the activity is linked, all its values (count, duration, etc.) are added to the Steps. The attributes cannot be changed once the activity is in use (i.e., linked). Table 63 Activity Table Table Rules Read Rule Delete Rule Cannot delete if Activity_Id is in use within the Step_Activity table Insert Rule Update Rule Cannot update if Activity_Id is in use within the Step_Activity table Table 64 Activity Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Activity_Id 2 Unique Data_Machine_Id Sequence_Number

124 116 Maximizer CRM 10.5 Table 65 Activity Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Activity_Id Long 4 Yes System-generated unique identifier for an Activity. Icon_Type Integer 2 Icon associated with the Activity: 0 = None 1 = Mail 2 = ToDo 3 = Phone 4 = Travel 5 = Sale 6 = Meal 7 = Presentation 8 = Speech 9 = Meeting Note: Icons can be viewed when an Activity is being created or modified. Effort Long 4 Time required to complete an Activity, in seconds. Cost Double 8 Cost of the Activity. Name String 79 Name of the Activity. Mandatory field. Def_Priority String 3 Default priority of the Activity. Alarm Integer 2 0 = Alarm not set 1 = Alarm set Alarm_Lead_Min Long 4 Lead time for the alarm, in minutes. a 5 million Detail String 119 Text describing the activity. Mandatory field. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

125 Chapter Table 65 Activity Table Fields (Continued) Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. Rec_Type Integer 2 Valid values: 0 = Opportunity-related records 30 = Traditional (manual) campaign a. Up to 999 complete minutes, hours, days, or weeks can be entered in the GUI. (No partial minutes, days, or weeks.) Once 999 minutes is reached, the number must first be rounded up to the nearest whole hour and then converted back to minutes. (I.e., 1000 minutes will be rejected but hours - will be accepted.) Once 999 hours is reached, the number must be converted to days and then back to minutes. The same theory applies once 999 days and weeks have been reached. Combined_Opp_User_Fields Table The Combined_Opp_User_Fields table is read-only and includes all the User-Defined Fields that have been created for opportunities. Note If you use this table for reporting, performance may be slow when reporting on large numbers of user-defined fields. Table 66 Combined_Opp_User_Fields Table Table Rules Read Rule Team Member only Delete Rule only Insert Rule only Update Rule only

126 118 Maximizer CRM 10.5 Table 67 Combined_Opp_User_Fields Table Index Definitions Index # Index Type Field 1 Field 2 1 Non- Unique Opp_Id Opp_Number Table 68 Combined_Opp_User_Fields Table Fields Opp_Id 23 Combined_Opp_ Unique record ID. Opp_Number 2 User_Fields. (Opp_Id, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Always 0. Currency Table The Currency table is visible only if multi-currency is enabled for the Address Book (in Administrator, File > Preferences > Multi-Currency) and if the user has the necessary user access rights. Table 69 Currency Table Table Rules Read Rule Delete Rule only Insert Rule only Update Rule only Table 70 Currency Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Unique Currency_Id

127 Chapter Table 71 Currency Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Currency_Id String 4 Yes Three-character currency code. Name String 79 Yes Name of the currency. Format_String String 79 Yes Three-character currency code. Status Yes Reserved for future use. Creation_Date DateString 10 Yes See History Fields on Creation_Time TimeString 11 Yes page 51. Creator_Id String 11 Yes Last_Modify_Dat e Last_Modify_Tim e OppActivity Table DateString 10 Yes TimeString 11 Yes Modified_by_Id String 11 Yes User ID of the user who last changed the currency. Requestor_Id String 11 Yes User ID of the user who requested the currency. Corporate Integer 2 Yes 0 = Entry Currency 1 = Corporate Currency Rate Double Yes Current rate of the currency The data in the OppActivity table contains all the attributes pertaining to the actual Activity that has been chosen after it has been assigned to the Opportunity via choosing the Strategy_Id. Once the Strategy_Id is assigned to the Opportunity, all entities associated with the Strategy (such as Step and Activity) are available. The Opportunity Management System (OMS) lets users accept the default settings or assign new ones. Table 72 OppActivity Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only b

128 120 Maximizer CRM 10.5 Table 72 Insert Rule Update Rule OppActivity Table Table Rules (Continued) Opp_Leader only Opp_Leader only a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. b. A Hotlist with the same Opp_Id, Opp_Number, Step_Id, and Activity_Id will be deleted. Table 73 OppActivity Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 1 Unique Data_Machine_I d 2 Non- Unique 3 Non- Unique Opp_Id Sequence_ Number Opp_Number Opp_Id Opp_Number Step_Id Activity_Id Table 74 OppActivity Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppActivity. (Opp_Id, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Step_Id Long 4 OppActivity. (Step_Id, Activity_Id) = Step_Activity_Lin k (Step_Id, Activity_Id) Unique identifier for the Opportunity this Activity belongs to. Mandatory field. Non-modifiable. Must be unique. Opp_Number is always 0. Unique identifier of the Step the activity belongs to. Mandatory field. Nonmodifiable. Must be unique. Activity_Id Long 4 Activity Identifier of the activity chosen from the Strategy Library. Mandatory field. Non-modifiable. Must be unique.

129 Chapter Table 74 OppActivity Table Fields (Continued) Status a Integer 2 Status of Step: 3676 = Waiting 3677 = Applied If Applied (3677), a Hotlist entry must exist with the same OppActivity Id. Completed Integer 2 0 = Incomplete 1 = Complete Duration Long 4 Duration of the activity, in seconds. Value must be between 0 and 2,500,000,000. Cost Double 8 Actual cost of the activity. Value must be between 0.0 and 9,999,999, Start_Date DateString 10 Date when the activity starts. End_Date DateString 10 Yes Start_Date + Strategy Table Duration. Reserved for future use. Start_Time Time String 11 Time when the activity starts. Icon_Type Integer 2 Icon associated with the Activity: 0 = None 1 = Mail 2 = ToDo 3 = Phone 4 = Travel 5 = Sale 6 = Meal 7 = Presentation 8 = Speech 9 = Meeting Note: Icons can be viewed when an Activity is being created or modified. Alarm Integer 2 0 = No alarm 1 = Alarm

130 122 Maximizer CRM 10.5 Table 74 OppActivity Table Fields (Continued) Alarm_Lead_Min Long 4 Lead time for alarm, in minutes. b Value must be between 0 and 5,000, Resp_Mem_Id Integer 2 Opportunity. Opp_Id = OppActivity. Opp_Id ID of the Team Member responsible for activity. 0 is default. If Team_Id is -1 then set to 0. (Opportunity. Team_Id,Opp Activity.Resp_ Member_Id) = Team.(Team_ Member_Id,Team _Id) With_Role_Id Long 4 Opportunity. Opp_Id = OppActivity. Opp_Id ID of the Role that this activity is to be assigned to. (Opportunity. Strategy_Id, OppActivity. With_Role_Id) = Strategy_Role. (Strategy_Id, Role_Id) With_Contact_Id Long 4 OppActivity. (With Role_Id, With Contact_Id) = OppContact. (Role_Id, Contact_Id) ID of Contact that this activity is to be assigned to. Priority String 3 Priority to be used for this activity. Detail String 253 Mandatory field. Description of the activity. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

131 Chapter Table 74 OppActivity Table Fields (Continued) Rec_Type Integer 2 0 = Opportunity-related records 30 = Traditional (manual) campaign a. Insertion is allowed for the Status field, except Applied and Waiting. Updating the value is only allowed if changing it to Applied. You cannot change it from Applied to Waiting. b. Up to 999 complete minutes, hours, days, or weeks can be entered in the GUI. (No partial minutes, days, or weeks.) Once 999 minutes has been reached the number must first be rounded up to the nearest whole hour and then converted back to minutes. (I.e., 1000 minutes will be rejected but hours - will be accepted.) Once 999 hours has been reached the number must be converted to days and then back to minutes. The same theory applies once 999 days and weeks have been reached. OppComp Table The OppComp table contains a description of the competitor an Opportunity may have. Table 75 OppComp Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only Insert Rule Team Member only Update Rule Team Member only a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. Table 76 OppComp Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique Opp_Id Opp_Number 3 Non- Unique Opp_Id Opp_Number Comp_Id

132 124 Maximizer CRM 10.5 Table 77 OppComp Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppComp.(Opp_I d, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Opportunity link. Mandatory field. Can insert. Cannot update. Should point to existing Opportunity. Opp_Number is always 0. Comp_Id Long 4 Yes Competitor Identifier. Can insert. Should be unique (generated by default). Can be explicitly specified by MASTER only. Comp_Client_Id String 23 OppComp. (Comp_Client_Id, Comp_Contact_ Num) = Company. (Comp_Client_Id, Comp_Contact_ Num) Comp_Contact_ Num Client ID of the competitor. Must exist in the Company table. Mandatory field. Can insert. Cannot update. Should point (together with Comp_Contact_Num) to valid Address Book entry. Integer 2 Contact number of the competitor. Must exist in the Company table. Can insert. Cannot update. Should point (together with Comp_Client_Id) to valid Address Book entry. Comment String 253 Text describing the competitor. Can insert. Can update. Cannot be blank. May contain up to 253 characters. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

133 Chapter OppContact Table The OppContact table contains link information to the actual person / company that has been chosen as the contact for the Role in the specific Opportunity. Table 78 OppContact Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only Insert Rule Team Member only Update Rule Team Member only a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. Table 79 OppContact Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 1 Unique Data_Machine_I d 2 Non- Unique 3 Non- Unique Opp_Id Sequence_ Number Opp_Number Opp_Id Opp_Number Role_Id Contact_Id Table 80 OppContact Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppContact. (Opp_Id, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Identifier for the associated Opportunity. Mandatory field. Can insert. Cannot update. Should point to existing Opportunity. Opp_Number is always 0.

134 126 Maximizer CRM 10.5 Table 80 OppContact Table Fields (Continued) Role_Id Long 4 (Opportunity. Strategy_Id, OppContact. Role_Id) = Strategy_Role_ Link.(Strategy_Id, Role_Id) Unique identifier for the Role. Mandatory field. Can insert. Cannot update. Contact_Id Long 4 System-generated unique identifier for the Contact. Cannot update. Can be explicitly specified by MASTER only. Contact_Client_Id String 23 OppContact. Contact_Contact_ Num Integer 2 (Contact_Client_I d,contact_contac t_ Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Identifier of the Company/ Individual that is assigned to this Role. Must exist in the Company or People table. Can insert. Can update. Should point to a valid Address Book entry. Comment String 253 Text describing the Opportunity Role. Can insert. Can update. Cannot be blank. May contain up to 253 characters. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

135 Chapter Opportunity Table The data in the Opportunity table contains all the attributes pertaining to the Opportunity entity in the Opportunity Management System. The attributes can be type of identification, foreign links, status, or statistic. For the foreign links, see the Opportunity Management Table Relations diagram at the beginning of this chapter. The statistic types are maintained by the system and should be left untouched. You can modify them, but do so only if you have an in-depth knowledge of the system. Table 81 Read Rule Delete Rule Insert Rule Update Rule Opportunity Table Table Rules Can only delete if Owner_Id is equal to Login_Id. OppActivity, OppStep, OppSuccessFactor, OppRole, Combined_Opp_User_Fields, and OppComp with the same Opp_Id will be deleted. Cannot update if any OppRole, OppActivity, OppComp, OppContact, OppSuccessFactor, or OppStep exists with the same Opp_Id. Table 82 Opportunity Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Data_Machine_Id Sequence_Number 2 Unique Opp_Id Opp_Number 3 Non- Unique 4 Non- Unique Client_Id Strategy_Id Contact_Id Table 83 Opportunity Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er

136 128 Maximizer CRM 10.5 Table 83 Opportunity Table Fields (Continued) Client_Id String 23 Opportunity. (Client_Id, Contact_Number) = Company. (Client_Id, Contact_Number) OR People.(Client_Id, Contact_Number) Company/Individual that is associated with the Opportunity. Mandatory field. Associated Company must already exist in the Company table. Nonmodifiable. Contact_Number Integer 2 Yes Not used. Reserved for future use. Always 0. Opp_Id String 23 Opportunity. (Opp_Id, Opp_Number, Comp_Client_Id, Comp_Contact_ Number) = OppComp. Comp_Client_Id String 23 Competitor that the Opportunity was lost to. (Opp_Id, Comp_Contact_ Integer 2 Competitor that the Opp_Number, Number Opportunity was lost to. Comp_Client_Id, Comp_Contact_ Num) Yes System-generated unique identifier. Opp_Number Integer 2 Yes Unique identifier. Opp_Number is always 0. Owner_Id String 11 Opportunity. (Owner_Id, Team_Id) = Team. (Owner_Id, Team_Id) Strategy_Id Long 4 Opportunity. Strategy_Id = Strategy. Strategy_Id Team_Id Integer 2 Opportunity. (Owner_Id, Team_Id) = Team.(Owner_Id, Team_Id) Team member that is chosen as the Opportunity leader. If Team ID is equal to -1 (no Team is assigned i.e., this is a Personal Opportunity) then defaults to Login ID. Strategy that has been assigned to the Opportunity. Must already exist within the Strategy Table. If the strategy is -1, no strategy is assigned (the user assigned none or not using a strategy) Team that has been assigned to the Opportunity. Mandatory field. If it is not equal to -1 (Single-user Opportunity), must already exist within the Team table.

137 Chapter Table 83 Opportunity Table Fields (Continued) Status Integer 2 Status of the Opportunity: 0 = New 1 = In Progress 2 = In Progress New 3 = Won 4 = Lost 5 = Abandoned 6 = Suspended Name String 79 Company/Individual associated with the Opportunity. Defaults to Client ID. Objective String 253 Sales Objective of the Opportunity. Reason_Id Long 4 Opportunity. (Reason_Id) = Reasons. (Reason_Id) Probability_ Closing ID of the Reason why the Opportunity was completed. Modified by OppLeader only. Integer 2 Percentage probability of closing the Opportunity. Based on an internal calculation formula. Valid values: Modifiable by OppLeader only. (Updated automatically by selecting Refresh Opportunity in OMS.) Actual_Revenue Double 8 Actual revenue generated by the Opportunity. Applicable only if Status = 3. Cost Double 8 Running total of the costs associated with Activities for the Opportunity. Must be greater than 0. Forecast_Revenu e Double 8 Revenue expected from successfully completing an Opportunity. Must be greater than 0. Modifiable by OppLeader only.

138 130 Maximizer CRM 10.5 Table 83 Opportunity Table Fields (Continued) Start_Date DateString 10 Date when the Opportunity was started. If left empty, defaults to the system clock. If 1, the date can be updated by the OppLeader only. Estimated_Close_ Date DateString 10 Original close date for the Opportunity. Based on adding the length of time for the Strategy to the Start_Date. Must be greater than Start Date. Modifiable by OppLeader only. If specified, becomes the Close_Date by default. Close_Date DateString 10 Projected or actual close date for the Opportunity. Updated as the Opportunity's steps are applied before or ahead of schedule. Must be greater than Start Date. Modifiable by OppLeader only. Last_Modify_Dat e DateString 10 Reserved for future use. Comment Memo n/a General comment for the Opportunity. Modifiable by OppLeader only. Completion_ Comment Memo n/a Completion comment for the Opportunity. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Suspended_Date DateString 10 The date an opportunity became suspended. This field is set by Maximizer when an opportunity with a strategy is applied.

139 Chapter Table 83 Opportunity Table Fields (Continued) Days_Suspended Long 4 The number of days an opportunity was suspended. This field is set by Maximizer only when an applied opportunity which was suspended is resumed after one day or more. NextAction String 63 Next action in the Action Plan for this Opportunity, as defined by the user. Cont_Client_Id String 23 Yes Client_Id of the associated Contact. Cont_Cont_ Number NextAction_ Projected Revenue_Currenc y_id Revenue_In_ Corporate_ Currency Long 4 Yes Contact_Number of the associated Contact. String 63 Next action in the Action Plan for this Opportunity, as defined by the strategy. String 4 Yes Three-character currency ID of the corporate or entry currency for the opportunity. Applicable only if multicurrency is enabled for the Address Book. Double 8 Yes Opportunity revenue amount converted to the corporate currency. Applicable only if multicurrency is enabled for the Address Book. OppPartners Table The OppPartners table contains information for Partners related to Opportunities. Table 84 OppPartners Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only Insert Rule

140 132 Maximizer CRM 10.5 Table 84 OppPartners Table Table Rules (Continued) Update Rule a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. Table 85 OppPartners Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique Opp_Id Opp_Number 3 Non- Unique Opp_Id Opp_Number Partner_Id Table 86 OppPartners Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppPartners. (Opp_Id, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Identifier for the associated Opportunity. Mandatory field. Can insert. Cannot update. Should point to existing Opportunity. Opp_Number is always 0. Partner_Id Long 4 Unique identifier. Insert only. Partner_Client_Id String 23 OppPartners. Insert only. (Partner_Client_I Partner_Contact_ Integer 2 Insert only. d,partner_contac Num t_ Num) = Client.(Client_Id, Contact_Number) Comment String 253 Creator_Id String 11 Yes See History Fields on Creation_Date String 10 Yes page 51. Creation_Time String 11

141 Chapter OppRole Table The data in the OppRole table contains all the attributes pertaining to the actual Role that has been chosen. Once the Strategy_Id has been assigned to the Opportunity, all entities associated with the Strategy (such as Step, Activity, and Role) are available. The OMS system lets users accept the default settings or assign new ones. This table is for select records from the Q-file with typ=4. When you assign a strategy to an Opportunity, this record is not yet available in the Q-file. It appears in the Q-file after you modify the Opportunity Role, and it s become different from the original Strategy Role. Table 87 OppRole Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only Insert Rule Team Member only Update Rule Team Member only a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. Table 88 OppRole Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique Opp_Id Opp_Number 3 Non- Unique Opp_Id Opp_Number Role_Id Table 89 OppRole Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppRole.(Opp_Id, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Identifier for the associated Opportunity. Mandatory field. Can insert. Cannot update. Should point to existing Opportunity. Opp_Number is always 0.

142 134 Maximizer CRM 10.5 Table 89 OppRole Table Fields (Continued) Role_Id Long 4 (Opportunity. Strategy_Id, OppRole.Role_Id) = Strategy_Role_ Link.(Strategy_Id, Role_Id) Unique identifier for the Role. Mandatory field. Can insert. Should be unique. Standing_Id Long 4 OppRole. Standing_Id = Standing_For_ Role.Standing_Id ID of the Standing that is associated with this Role. Mandatory field. Can insert. Can update. Should point to Role_Standing_Link table, Standing_Id field. Score Integer 2 Yes The score for this Role. Cannot insert. Cannot update. Desc String 253 Description of the OppRole. Can insert. Can update. Cannot be blank. May contain up to 253 characters. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Rec_Type Integer 2 Can insert. Cannot update. Valid values: 0 = Opportunity-related records

143 Chapter OppStep Table The data in the OppStep table contains all the attributes pertaining to the actual Step that has been chosen. Once the Strategy_Id has been assigned to the Opportunity, all entities associated with the Strategy (such as Step and Activity) are available. The OMS system lets users accept the default settings or assign new ones. Table 90 OppStep Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only Insert Rule Opp_Leader only Update Rule Opp_Leader only a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. Table 91 OppStep Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique Opp_Id Opp_Number 3 Non- Unique Opp_Id Opp_Number Step_Id Table 92 OppStep Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppStep.(Opp_Id, Opp_Number) = Opportunity. (Opp_Id, Opp_Number) Step_Id Long 4 OppStep.Step_Id = Step.Step_Id Identifier for the associated Opportunity. Mandatory field. Can insert. Cannot update. Should point to existing Opportunity. Opp_Number is always 0. Step Identifier. Mandatory field. Non-modifiable.

144 136 Maximizer CRM 10.5 Table 92 OppStep Table Fields (Continued) Status Integer 2 Status of Step: 3337 = Not Applied 3338 = Reviewed 3339 = Behind 3340 = On Schedule 3341 = Ahead 3342 = Complete Duration Long 4 Sum of the (actual) duration for each of the Activities associated with this Step. Must be greater than 0. Cost Double 8 Sum of the (actual) Costs for each of the Activities associated with this Step. Must be greater than 0 Start_Date DateString 10 Projected/Actual start date of the Step. End_Date DateString 10 Yes Projected end date of the Step. Must be greater than Start_Date. Comment String 253 Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Rec_Type Integer 2 Valid values: 0 = Opportunity-related records 30 = Manual campaign

145 Chapter OppSuccessFactor Table The data in the OppSuccessFactor table contains all the attributes pertaining to the actual SuccessFactor that has been chosen. Once the Strategy_Id has been assigned to the Opportunity, all entities associated with the Strategy (such as Step and Activity) are available. The OMS system lets users accept the default settings or assign new ones. Table 93 OppSuccessFactor Table Table Rules Read Rule Team Member only Delete Rule Opp_Leader a only Insert Rule Opp_Leader only Update Rule Team Member only a. Opp_Leader is equal to the User_Id of the individual assigned to manage an Opportunity. Table 94 OppSuccessFactor Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Unique Data_Machine_Id Sequence_Number 2 Non- Unique Opp_Id Opp_Number 3 Non- Unique Opp_Id Opp_Number Success_Factor_Id Table 95 OppSuccessFactor Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Opp_Id Opp_Number String Integer 23 2 OppSuccessFactor.(Opp_Id, Opp_ Number) = Opportunity. (Opp_Id, Opp_Number) Identifier for the associated Opportunity. Mandatory field. Can insert. Cannot update. Should point to existing Opportunity. Opp_Number is always 0.

146 138 Maximizer CRM 10.5 Table 95 OppSuccessFactor Table Fields (Continued) Success_Factor_Id Long 4 OppSuccessFactor.Success_Factor_I d = Success_Factor. Success_Factor_Id Standing_Id Long 4 OppSuccessFactor.Standing_Id = Standing_For_ Success_Factor. Standing_Id Identifier for the Success Factor. Mandatory field. Non-modifiable. ID of the Standing that is associated with this Success Factor. Mandatory field. Score Integer 2 Yes The score for this Success Factor. Calscore Integer 2 On Schedule Activity % updateable for On Schedule entry. Comment String 253 Text describing the OppSuccessFactor. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Rec_Type Integer 2 Valid values: 0 = Opportunity-related records Prob_Close_Range Table The Prob_Close_Range table contains the description of different ranges of probability of closing. The default is the one which starts with 0. The user can change the range as long as the new one does not overlap with (mutually exclude) the other existing ranges. Note The Prob_Close_Range table does not have any special table-level rules. Table 96 Prob_Close_Range Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Range_Id

147 Chapter Table 96 Prob_Close_Range Table Index Definitions (Continued) Index # Index Type Field 1 Field 2 2 Unique Data_Machine_Id Sequence_Number Table 97 Prob_Close_Range Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Range_Id Long 4 Yes System-generated unique identifier for a Range. Sub_Type Integer 2 Yes Type of reason: 0 = System-created range. 3 = User-created range. Range_Min Integer 2 Inclusive range minimum. Mandatory field. Valid values: Range_Max Integer 2 Inclusive range maximum. Mandatory field. Must be greater than the Range minimum. Valid values: Name String 79 Text to be associated for the range. Mandatory field. Unique name. Color Long 4 Yes Color to be displayed for the range. Reserved for future use. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

148 140 Maximizer CRM 10.5 Reasons Table The Reasons table contains the reasons the user can assign to explain why an Opportunity succeeded or failed. Note that this table is read-only for all users with the exception of the MASTER user. Table 98 Reasons Table Table Rules Read Rule only Delete Rule MASTER user only Insert Rule MASTER user only Update Rule MASTER user only Table 99 Reasons Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Reason_Id 2 Unique Data_Machine_Id Sequence_Number Table 100 Reasons Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Reason_Id Long 4 Yes Unique identifier for the Reason. Type Integer 2 Type of Reason: 10 = Win reason 11 = Loss reason 12 = Abandoned reason 16 = Suspended reason Mandatory field. Desc String 79 Text describing Reason. Mandatory field. Must be unique. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

149 Chapter Strategy Library Tables Role Table on page 142 Role_Standing_Link Table on page 143 Standing_For_Role Table on page 144 Standing_For_Success_Factor Table on page 146 Step Table on page 147 Step_Activity_Link Table on page 149 Strategy Table on page 151 Strategy_Role_Link Table on page 152 Strategy_Step_Link Table on page 156 Strategy_Success_Factor_Link Table on page 155 Success_Factor Table on page 159 Success_Factor_Standing_Link Table on page 160 Strategy Library Table Relationships The following diagram shows how the Strategy Library tables are linked.

150 142 Maximizer CRM 10.5 Role Table The data in the Role table contains all the attributes pertaining to the Role entity in the Strategy Library. The attributes describe a Role which is to be associated with one or more Strategy entities (linked via the Strategy_Role_Link record) in the Strategy Library. Table 101 Role Table Table Rules Read Rule Delete Rule Cannot delete if Role_Id is in use in the Strategy_Role table a Insert Rule Cannot insert if Role_Id is in use in the Strategy_Role table Update Rule Cannot update if Role_Id is in use in the Strategy_Role table a. Role_Standing will be deleted. Table 102 Role Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Role_Id 2 Unique Data_Machine_Id Sequence_Number Table 103 Role Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Role_Id Long 4 Yes System-generated unique identifier for the Role. Must be unique. Non-modifiable. Name String 79 Name of the Role. Mandatory field. Unique Name. Desc String 253 Description of the Role. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

151 Chapter Table 103 Role Table Fields (Continued) Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. Rec_Type Integer 2 Valid values: 0 = Opportunity-related record 30 = Traditional (manual) campaign Role_Standing_Link Table The Role_Standing_Link table associates a Standing to a Role entity in the Strategy Library. Each link record reflects a many-to-many relationship between the Standing_For_Role and the Role entities. Note The Role_Standing_Link table does not have any special table-level rules. Table 104 Role_Standing_Link Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Role_Id Standing_Id 2 Unique Data_Machine_Id Sequence_Number 3 Non- Unique Role_Id 4 Unique Standing_Id Role_Id

152 144 Maximizer CRM 10.5 Table 105 Role_Standing_Link Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Role_Id Long 4 Role_Standing_ Link.Role_Id = Role.Role_Id Standing_Id Long 4 Role_Standing_ Link.Standing_Id = Standing_For_ Role.Standing_Id Standing_For_Role Table ID of Role that the Standing is linked to. Must already exist in the Role_Table. Mandatory field. Nonmodifiable. ID of Standing that is linked to the Role. Must already exist in the Standing_For_Role_Table. Mandatory field. Nonmodifiable. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. The data in the Standing_For_Role table contains all the attributes pertaining to the Standing entity in the Strategy Library. The attributes describe the scores associated with a Role. Table 106 Standing_For_Role Table Table Rules Read Rule Delete Rule Cannot delete if Standing_Id is in use in the Role_Standing table Insert Rule Update Rule Cannot update

153 Chapter Table 107 Standing_For_Role Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Standing_Id 2 Unique Data_Machine_Id Sequence_Number Table 108 Standing_For_Role Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Standing_Id Long 4 Yes System-generated unique identifier for the role standing. Non-modifiable. Sub_Type Integer 2 Yes Indicates if this Standing is a System Defined Standing. 0 = Standard Standing Score Integer 2 Score associated with the Standing. Valid values: Calc_Score Integer 2 Reserved for future use. Valid values: -100 to 100 Name String 79 Name of the Role. Mandatory field. Unique Name. Modifiable. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated.

154 146 Maximizer CRM 10.5 Standing_For_Success_Factor Table The data in the Standing_For_Success_Factor table contains all the attributes pertaining to the Standing entity in the Strategy Library. The attributes describe the scores associated with a Success Factor. Table 109 Standing_For_Success_Factor Table Table Rules Read Rule Delete Rule Cannot delete if Standing_Id is in use in the Success_Factor_Standing table Insert Rule Update Rule Cannot update Table 110 Standing_For_Success_Factor Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Standing_Id 2 Unique Data_Machine_Id Sequence_Number Table 111 Standing_For_Success_Factor Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Standing_Id Long 4 Yes System-generated unique identifier for the Success Factor Standing. Nonmodifiable. Sub_Type Integer 2 Yes Indicates if this Standing is a System Defined Standing: 0 = Standard Standing 1 = On Schedule System Defined Standing 2 = Political Alignment System Defined Standing Score Integer 2 Score associated with this Standing. Valid values:

155 Chapter Table 111 Standing_For_Success_Factor Table Fields (Continued) Calc_Score Integer 2 Used in System Defined Standings to match against the internally calculated score. Valid values: -100 to 100 Name String 79 Yes Name of the Standing. Mandatory field. Unique name, if Sub_Type 1 or 2. Non-modifiable. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. Step Table The data in the Step table contains all the attributes pertaining to the Step entity in the Strategy Library. The attributes describe the default settings of a step that is to be linked to one or more Strategy entities (linked via the Strategy_Step_Link record) in the Strategy template. Once the Step is linked, all its values (count, duration, etc.) are added to the Strategy. The attributes cannot be changed once the Step is in use (i.e., linked). Table 112 Step Table Table Rules Read Rule Delete Rule Cannot delete if Step_Id is used in the Strategy_Step table Insert Rule Update Rule Cannot update if Step_Id is used in the Strategy_Step table

156 148 Maximizer CRM 10.5 Table 113 Step Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Step_Id 2 Unique Data_Machine_Id Sequence_Number Table 114 Step Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Step_Id Long 4 Yes System-generated unique identifier for each Step. Activity_Count Integer 2 Yes Count of Activities used by the Step. Effort Long 4 Yes Sum of the Effort of all Activities used by the Step, in seconds. Duration Long 4 Actual time required to complete the Step. Stored in seconds (< 2.5 billion seconds). Valid when the value is between 0 and 2.5 billion seconds. Default is 1 day in seconds (86,400 seconds). Cost Double 8 Yes Sum of costs of all Activities used by the Step. Name String 79 Name of a Step. Mandatory field. Unique name. Goal String 253 Description of a Step. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

157 Chapter Table 114 Step Table Fields (Continued) Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. Rec_Type Integer 2 Valid values: 0 = Opportunity-related records 30 = Traditional (manual) campaign Step_Activity_Link Table The Step_Activity_Link table associates an Activity with a Step entity in the Strategy Library. Each link record reflects a many-to-many relationship between the Step and the Activity entities (i.e., many Activities can be linked to a Step and vice versa). Once the link is established, all the Activity s default values (count, duration, etc.) are added to the Step s accumulated values. Table 115 Read Rule Delete Rule Insert Rule Update Rule Step_Activity_Link Table Table Rules Cannot delete if Step_Id is used in the Strategy_Step table. The Effort and Cost of the Activity record will be subtracted from the Step table via Step_Activity_Link. Activity s Effort field will be subtracted from the Step record Duration field if it is the same as the Effort field. Cannot insert if Step_Id is used with the Strategy_Step table. The Effort and Cost of the Activity record will be added to the Step table via Step_Activity_Link. Activity s Effort field will be added to the Step record Duration field if it is the same as the Effort field. Cannot update Table 116 Step_Activity_Link Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Step_Id Activity_Id

158 150 Maximizer CRM 10.5 Table 116 Step_Activity_Link Table Index Definitions (Continued) Index # Index Type Field 1 Field 2 2 Non- Unique Step_Id 3 Unique Data_Machine_Id Sequence_Number 4 Unique Activity_Id Step_Id Table 117 Step_Activity_Link Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Step_Id Long 4 Step_Activity_Lin k.step_id = Step.Step_Id Activity_Id Long 4 Step_Activity_Lin k.activity_id = Activity.Activity_I d ID of Step that the Activity is linked to. Mandatory field. Value must already exist in the Step_Table. Nonmodifiable. ID of the Activity that is linked to the Step. Mandatory field. Value must already exist in Activity_Table. Nonmodifiable. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated.

159 Chapter Strategy Table The data in the Strategy table contains all the attributes pertaining to the Strategy entity in the Opportunity Management System. The attributes are mainly statistics about the Step and Activity entities associated with this Strategy via the Strategy_Step_Link and Step_Activity_Link files. Table 118 Read Rule Delete Rule Insert Rule Update Rule Strategy Table Table Rules Cannot delete if Strategy_Id is in use in the Opportunity table. Delete Strategy_Role, Strategy_Success_Factor, Strategy_Step with the same Strategy_Id. Cannot update if Strategy_Id is in use in the Opportunity table Table 119 Strategy Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Strategy_Id 2 Unique Data_Machine_Id Sequence_Number Table 120 Strategy Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Strategy_Id Long 4 Yes System-generated unique identifier for a Strategy. Must NOT already exist. Step_Count Integer 2 Yes Number (quantity) of Steps associated with a Strategy. Activity_Count Integer 2 Yes Number (quantity) of Activities associated with a Strategy. Effort Long 4 Yes Sum of the Effort of all Steps used by the Strategy, in seconds. Duration Long 4 Yes Sum of the Duration of all Steps used by the Strategy, in seconds.

160 152 Maximizer CRM 10.5 Table 120 Strategy Table Fields (Continued) Cost Double 8 Yes Sum of costs of all Steps used by the Strategy. Name String 79 Name of the Strategy. Mandatory field. Unique Name. Desc Memo n/a Description of the Strategy. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the strategy is a static or dynamic: 0 = Static strategy (default) 1 = Dynamic strategy (entries of this type may not be inserted or updated) Note: A strategy becomes dynamic after it has been assigned to an Opportunity and then one or more of the Steps has been modified in that Opportunity. Rec_Type Integer 2 Opportunity or Campaign type: 0 = Opportunity 10 = Automated Campaign 30 = Traditional Campaign Strategy_Role_Link Table The Strategy_Role_Link table associates a Role to a Strategy entity in the Strategy Library. Each link record reflects a many-to-many relationship between the Role and the Strategy entities. Table 121 Strategy_Role_Link Table Table Rules Read Rule Delete Rule Cannot delete if Strategy_Id is in use in the Opportunity table

161 Chapter Table 121 Insert Rule Update Rule Strategy_Role_Link Table Table Rules (Continued) Cannot insert if Strategy_Id is in use in the Opportunity table. Total of Weights field of records with the same Strategy_Id must be less than or equal to 100. Cannot update if Strategy_Id is in use in the Opportunity table. Total of Weights field of records with the same Strategy_Id must be less than or equal to 100. Table 122 Strategy_Role_Link Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Strategy_Id Role_Id 2 Unique Data_Machine_Id Sequence_Number 3 Non- Unique 4 Non- Unique 5 Non- Unique Strategy_Id Weight Strategy_Id Weight 6 Unique Role_Id Strategy_Id Table 123 Strategy_Role_Link Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Strategy_Id Long 4 Strategy_Role_ Link.Strategy_Id = Strategy. Strategy_Id Role_Id Long 4 Strategy_Role_ Link.Role_Id = Role.Role_Id ID of Strategy that the Role is linked to. Must already exist in the Strategy_Table. Mandatory field. Nonmodifiable. ID of Role that is linked to the Strategy. Must already exist in the Role_Table. Mandatory field. Nonmodifiable. Weight Integer 2 Mandatory field. Weight assigned to the Role in a Strategy. Range = 0-100

162 154 Maximizer CRM 10.5 Table 123 Strategy_Role_Link Table Fields (Continued) Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated.

163 Chapter Strategy_Success_Factor_Link Table The Strategy_Success_Factor_Link table associates a Success_Factor to a Strategy entity in the Strategy Library. Each link record reflects a many-to-many relationship between the Success_Factor and the Strategy entities. Table 124 Read Rule Delete Rule Insert Rule Update Rule Strategy_Success_Factor_Link Table Table Rules Cannot delete if Strategy_Id is in use in the Opportunity table Cannot insert if Strategy_Id is in use in the Opportunity table. Total of Weights field of records with the same Strategy_Id must be less than or equal to 100. Cannot update if Strategy_Id is in use in the Opportunity table. Total of Weights field of records with the same Strategy_Id must be less than or equal to 100. Table 125 Strategy_Success_Factor_Link Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Strategy_Id Success_Factor_Id 2 Unique Data_Machine_Id Sequence_Number 3 Non- Unique 4 Non- Unique 5 Non- Unique Strategy_Id Weight Strategy_Id Weight 6 Unique Success_Factor_Id Strategy_Id Table 126 Strategy_Success_Factor_Link Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Strategy_Id Long 4 Strategy_Success_ Factor_Link. Strategy_Id = Strategy. Strategy_Id Mandatory field. ID of Strategy that the Success Factor is linked to. Must already exist in the Strategy_Table. Nonmodifiable.

164 156 Maximizer CRM 10.5 Table 126 Strategy_Success_Factor_Link Table Fields (Continued) Success_Factor_Id Long 4 Strategy_Success_ Factor_Link. Sucess_Factor_Id = Success_Factor. Success_Factor_Id Strategy_Step_Link Table Mandatory field. ID of Success Factor that is linked to the Strategy. Must already exist in Success_Factor_Role_Table. Non-modifiable. Weight Integer 2 Mandatory field. Weight assigned to the Success Factor in the Strategy. Valid values: Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. The Strategy_Step_Link table associates a Step to a Strategy entity in the Strategy Library. Each link record reflects a many-to-many relationship between the Step and the Strategy entities. Once the link is established, all the Step s accumulated values (count, duration, etc.) are added to the Strategy s accumulated values. Table 127 Read Rule Delete Rule Insert Rule Strategy_Step_Link Table Table Rules Cannot delete if Strategy_Id is in use in the Opportunity table. The Duration, Cost, and Effort of the Step will be subtracted from the Strategy table via Strategy_Step_Link. Cannot insert if Strategy_Id is in use in the Opportunity table. The Duration, Cost, and Effort of the Step will be added to the Strategy table via Strategy_Step_Link.

165 Chapter Table 127 Strategy_Step_Link Table Table Rules (Continued) Update Rule Cannot update Table 128 Strategy_Step_Link Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Strategy_Id Step_Id 2 Unique Data_Machine_Id Sequence_Number 3 Non- Unique Strategy_Id 4 Unique Step_Id Strategy_Id Table 129 Strategy_Step_Link Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Strategy_Id Long 4 Strategy_Step_ Link.Strategy_Id = Strategy. Strategy_Id Step_Id Long 4 Strategy_Step_ Link.Step_Id = Step.Step_Id ID of Strategy that the Step is linked to. Must already exist in the Strategy_Table. Mandatory field. Nonmodifiable. ID of Step that is linked to the Strategy. Must already exist in Step_Table. Mandatory field. Nonmodifiable. Chron_Order Integer 2 Mandatory field. Order of Steps to be performed. Unique for all the Strategy Steps belonging to a Strategy. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11

166 158 Maximizer CRM 10.5 Table 129 Strategy_Step_Link Table Fields (Continued) Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated.

167 Chapter Success_Factor Table The data in the Success_Factor table contains all the attributes pertaining to the Success_Factor entity in the Strategy Library. The attributes generally describe a Success_Factor which is to be associated with one or more Strategy entities (linked via the Strategy_Success_Factor_Link record) in the Strategy Library. Table 130 Read Rule Delete Rule Insert Rule Update Rule Success_Factor Table Table Rules Cannot delete if Success_Factor is in use in the Strategy_Success_Factor table. Success_Factor_Standing will be deleted as well. Cannot delete if Sub_Type does not equal 0. Cannot update if Success_Factor is in use in the Strategy_Success_Factor. Cannot update if Sub_Type does not equal 0. Table 131 Success_Factor Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Success_Factor_Id 2 Unique Data_Machine_Id Sequence_Number Table 132 Success_Factor Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Success_Factor_Id Long 4 Yes Unique identifier of the Success Factor. Nonmodifiable. Sub_Type Integer 2 Yes Type of Success Factor: 0 = Standard Success Factor 1 = On Schedule System- Defined Success Factor 2 = Political Alignment System-Defined Success Factor

168 160 Maximizer CRM 10.5 Table 132 Success_Factor Table Fields (Continued) Name String 79 Name of the Success Factor. Mandatory field. Unique Name, if Sub_Type 1 or 2. Non-modifiable. Desc String 253 Description of the Success Factor. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated. Rec_Type Integer 2 Valid values: 0 = Opportunity-related records Success_Factor_Standing_Link Table The Success_Factor_Standing_Link table associates a Standing to a Success_Factor entity in the Strategy Library. Each link record reflects a many-to-many relationship between the Standing and the Success_Factor entities. Note The Success_Factor_Standing_Link table does not have any special table-level rules. Table 133 Success_Factor_Standing_Link Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Success_Factor_Id Standing_Id 2 Unique Data_Machine_Id Sequence_Number

169 Chapter Table 133 Success_Factor_Standing_Link Table Index Definitions (Continued) Index # Index Type Field 1 Field 2 3 Non- Unique Success_Factor_Id 4 Unique Standing_Id Success_Factor_Id Table 134 Success_Factor_Standing_Link Table Fields Data_Machine_Id Long 4 Yes See Identity Fields on Sequence_Numb Long 4 Yes page 50. er Success_Factor_Id Long 4 Success_Factor_ Standing_Link. Success_Factor_Id = Success_Factor. Success_Factor_Id Standing_Id Long 4 Success_Factor_ Standing_Link. Standing_Id = Standing_For_ Success_Factor. Standing_Id ID of Success Factor that the Standing is linked to. Must already exist in the Success_Factor table. Mandatory field. Nonmodifiable. ID of Standing that is linked to the Success Factor. Must already exist in the Standing_For_Success_Factor table. Mandatory field. Nonmodifiable. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Strategy_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic strategy, entries of this type may not be inserted or updated.

170 162 Maximizer CRM 10.5 User and Group Tables Security_Group Table on page 162 Team Table on page 163 User_Details Table on page 165 Security_Group Table The Security Group table includes records used by the system to lookup the Ids and names of user groups. This is a read-only table for security reasons. Group ID String Format When entering Group IDs, use the format.east..00, as explained below, unless you are integrating with a Maximizer version older than version 8..EAST..00 Group IDs end with two zeros 00. If the Group ID is less than six characters, append. periods as placeholders at the end of the Group ID, for a total of six characters. (Group ID + placeholders = six characters) Group IDs may contain a maximum of six characters. Group IDs begin with a. period. When integrating with versions of Maximizer older than version 8, use the format âeastëë00, as explained below. âeastëë00 Group IDs end with two zeros 00. If the Group ID is less than six characters, append ë characters as placeholders at the end of the Group ID, for a total of six characters. (Group ID + placeholders = six characters) Group IDs may contain a maximum of six characters. Group IDs begin with the â character. Table 135 Security_Group Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only

171 Chapter Note The Security_Group table does not have an index defined. Table 136 Security_Group Table Fields Group_Id String 11 Yes System ID to identify the security group. Group Name String 39 Yes Name of the security group. Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Team Table The Team table contains a description of each team set up by MaxExchange Site Manager. Note When linking to the Team table in Microsoft Access, you must specify the first four fields as unique index fields. The first four fields are Db_Id, Rec_Type, Team_Id, and Team_Member_Id. Table 137 Team Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only Table 138 Team Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 1 Non- Unique 2 Non- Unique Rec_Type Team_Id Owner_Id Rec_Type Owner_Id Team_Id

172 164 Maximizer CRM 10.5 Table 139 Team Table Fields Db_Id Integer 2 Rec_Type Integer 2 Yes Record type: 1 = Team 2 = Team member Team_Id Integer 2 Yes Unique identification number for a Team. The records for the Team (Rec_Type = 1) and its members (Rec_Type = 2) all share the same Team_Id. Team_Member_I d Integer 2 Yes Unique identification number for a Team Member. 0 = Team 1 = Team member Owner_Id String 11 User_Details. User_Id Yes User_Id of team member. Blank if team. Name String 79 Yes Team name or team member name. Team_Leader Long 4 Yes Team leader status: 0 = Not team lead 1 = Team lead Team_Type Integer 2 Yes Flag indicating whether the record was created as a result of a dynamic strategy in Maximizer. 0 = Default 1 = As a result of a dynamic team Is_Marketing_ Team Integer 2 0 = Sales team (Opportunities) 1 = Marketing team (Campaigns)

173 Chapter User_Details Table The User_Details table contains personal information for users such as name, phone numbers, and address. Table 140 User_Details Table Table Rules Read Rule only Delete Rule only Insert Rule only Update Rule only Table 141 User_Details Table Index Definitions Index # Index Type Field 1 Field 2 1 Unique Rec_Type User_Id Table 142 User_Details Table Fields Rec_Type Integer 2 Yes Value is always 6. User_Id String 11 Yes Mr/Ms String 79 Yes First_Name String 79 Yes Initial String 79 Yes Last_Name String 79 Yes Title String 79 Yes Salutation String 79 Yes Company_Name String 79 Yes Department String 79 Yes Division String 79 Yes Address_Line1 String 79 Yes Address_Line2 String 79 Yes City String 79 Yes State_Province String 79 Yes

174 166 Maximizer CRM 10.5 Table 142 User_Details Table Fields (Continued) Zip_Code String 79 Yes Country String 79 Yes Phone_1 String 21 Yes Phone_1_ Extension String 21 Yes Phone_2 String 21 Yes Phone_2_ Extension String 21 Yes Phone_3 String 21 Yes Phone_3_ Extension String 21 Yes Phone_4 String 21 Yes Phone_4_ Extension String 21 Yes _Address String 119 Yes Web_Site String 119 Yes Custom_Field_1 String 119 Yes Custom_Field_2 String 119 Yes Custom_Field_3 String 119 Yes Custom_Field_4 String 119 Yes Creator_Id String 11 Yes See History Fields on Creation_Date DateString 10 Yes page 51. Creation_Time TimeString 11 Last_Update_Dat e Last_Update_Tim e String 10 Yes String 11 Yes Private_Read Integer 2 Yes 0 = Public 1 = Private CS_Manager Integer 2 Yes 0 = False 1 = True

175 Chapter Table 142 User_Details Table Fields (Continued) CS_Representativ e Integer 2 Yes 0 = False 1 = True KB_Approver Integer 2 Yes 0 = False 1 = True Sales_Manager Integer 2 Yes 0 = False 1 = True Sales_ Representative Integer 2 Yes 0 = False 1 = True Reports_To String 11 Yes The user ID of the person the user reports to. This information is used in organizational charts generated by Maximizer.

176 168 Maximizer CRM 10.5 Third-Party Synchronization Tables These tables store data from non-maximizer databases (third-party software). Additional fields can be stored as user-defined fields, and can be defined in the Third- Party Integration tab in the Set Up User-Defined Fields dialog box in Maximizer and Administrator. Custom_Independent Table on page 168 Custom_Child Table on page 172 Custom_Independent Table This table stores non-maximizer database (third party) data. CAUTION Deleting a Custom_Independent record also deletes any related notes, documents, user-defined fields, and Custom_Child records. Table 143 Read Rule Delete Rule Insert Rule Update Rule Custom_Independent Table Table Rules Can view the record if the record is Public, or the record is Private to you or to a group you are a member of, or you or to a group you are a member of has Read Access rights to the record, or you have the Modify other users private entries access right Can delete the record if the record is Public, or the record is Private to you or to a group you are a member of, or you have the Modify other users private entries access right Anybody can insert records Can update the record if the record is Public, or the record is Private to you or to a group you are a member of, or you have the Modify other users private entries access right Table 144 Custom_Independent Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 1 Unique Data_Machine_I d Sequence_ Number 2 Unique Custom_Id Custom_Number

177 Chapter Table 144 Custom_Independent Table Index Definitions (Continued) Index # Index Type Field 1 Field 2 Field 3 Field 4 3 Nonunique App_Id Name Custom_Id Custom_Number Table 145 Custom_Independent Table Ref. Data_Machine_Id Integer 4 See Identity Fields on page 50. Sequence_Number Integer 4 App_Id String 23 Application Id. Mandatory field. Insertable; Not updateable Maximizer does not limit or test App_Id for uniqueness. Your setup should ensure that it is using a unique App_Id and be prepared to change it if not. While the chances of App_Id collision are quite low, try to use an App_Id that will not be common. For example: Poor App_Id: INVOICES Better App_ID: WMS_CONSULT_INVOICES

178 170 Maximizer CRM 10.5 Table 145 Custom_Independent Table (Continued) Ref. Custom_Id String 23 Unique record identifier. Custom_Number Integer 2 Custom_Id is system generated if not specified (System-generated Custom_Id has X suffix). Insertable; Not updateable. These fields are required. If they are not provided, they will be system-generated. To prevent duplicate ID issues from occurring in a MaxExchange environment, ensure the following: The Custom_Id/ Custom_Number pair (whether generated automatically or manually entered) is unique on the MaxExchange server and each remote, across all databases. Custom_Id is different from Client_Id in AMGR_Clients table, Opp_Id in AMGR_Opportunites table, and Case_Id in AMGR_CSCases table. Name String 79 User-defined. This field is not required, but it is very important and should not be left blank. Text1 String 254 User-defined. Text2 String 254 User-defined. Text3 String 254 User-defined. Text4 String 254 User-defined. Number1 Integer 10 User-defined. Number2 Integer 10 User-defined. Number3 Integer 10 User-defined. Number4 Integer 10 User-defined. Number5 Integer 10 User-defined. Number6 Integer 10 User-defined. Number7 Integer 10 User-defined.

179 Chapter Table 145 Custom_Independent Table (Continued) Ref. Number8 Integer 10 User-defined. Date1 DateString 10 User-defined. Time1 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Date2 DateString 10 User-defined. Time2 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Date3 DateString 10 User-defined. Time3 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Date4 DateString 10 User-defined. Time4 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Currency1 Float 15 User-defined. Currency2 Float 15 User-defined. Currency3 Float 15 User-defined. Currency4 Float 15 User-defined. Private Integer 2 See Security Fields on page 50. Owner_Id String 11 See Security Fields on page 50. ReadPriv Integer 2 See Security Fields on page 50. Read_Id String 11 Create_Date DateString 10 See History Fields on page 51. Create_Time TimeString 11 Note: The milliseconds of time fields will not be synchronized via MaxExchange. Creator_Id String 11 See History Fields on page 51.

180 172 Maximizer CRM 10.5 Table 145 Custom_Independent Table (Continued) Ref. Last_Modify_Date DateString 10 See History Fields on page 51. Last_Modify_Time TimeString 11 Note: The milliseconds of time fields will not be synchronized via MaxExchange. Modified_By_Id String 11 Must be populated by the user. Not automatically updated. The Maximizer ODBC driver does not check whether ther user ID entered is valid. Can insert. Can update. Description String 1023 User-defined. Custom_Child Table This table stores non-maximizer database (third party) data. CustomChild records may be children of a CustomIndependent records or of other records, such as Address Book, Opportunity, or other records, as specified in the Entity_Type field. CAUTION A Custom_Child record will be deleted automatically when the parent record (Address Book entry, customer service case, opportunity, campaign, or Custom_Independent) is deleted. Deleting a Custom_Child record also deletes any related notes, documents, user-defined fields records. Table 146 Read Rule Delete Rule Insert Rule Custom_Child Table Table Rules Can view the record if you have at least read access to the parent record and the record is Public, or the record is Private to you or to a group you are a member of, or you or to a group you are a member of has Read Access rights to the record, or you have the Modify other users private entries access right Can delete the record if you have at least read access to the parent record and the record is Public, or the record is Private to you or to a group you are a member of, or you have the Modify other users private entries access right Anybody can insert records if they have at least read access to the parent record

181 Chapter Table 146 Update Rule Custom_Child Table Table Rules (Continued) Can update the record if you have at least read access to the parent record and the record is Public, or the record is Private to you or to a group you are a member of, or you have the Modify other users private entries access right Table 147 Custom_Child Table Index Definitions Index # Index Type Field 1 Field 2 Field 3 Field 4 1 Unique Data_Machine_I d Sequence_ Number 2 Unique Custom_Id Custom_Number 3 Nonunique 4 Nonunique App_Id Name Custom_Id Custom_Number Client_Id Client_Number Table 148 Custom_Child Table Ref. Data_Machine_Id Integer 4 See Identity Fields on page 50. Sequence_Number Integer 4 App_Id String 23 Application Id. Mandatory field. Insertable; Not updateable

182 174 Maximizer CRM 10.5 Table 148 Custom_Child Table (Continued) Ref. Custom_Id String 23 Unique record identifier. Custom_Number Integer 2 Insertable; Not updateable. Custom_Id is system generated if not specified (System-generated Custom_Id has X suffix).these fields are required. If they are not provided, they will be system-generated. To prevent duplicate ID issues from occurring in a MaxExchange environment, ensure the following: The Custom_Id/ Custom_Number pair (whether generated automatically or manually entered) is unique on the MaxExchange server and each remote, across all databases. Custom_Id is different from Client_Id in AMGR_Clients table, Opp_Id in AMGR_Opportunites table, and Case_Id in AMGR_CSCases table. Client_Id String 23 to master record. Client_Number Integer 2 Insertable; Not updateable. Client_Id/Client_Number reference a master record in another table. For example: Client_Id/Contat_Number in Clients table Opp_Id/Opp_Number in Opportunities table Custom_Id/Custom Number in Custom_Independent table

183 Chapter Table 148 Custom_Child Table (Continued) Ref. Entity_Type Integer 2 Specifies which table Client_Id/ Client_Number references. Entity_Type values supported by Maximizer ODBC driver: Entity_Type values correspond to the Client_Id/Contact_Number pair references on the right: 0 = Not specified 1 = Address Book entry 2 = Opportunity 3 = Campaign 4 = User 5 = Customer Service case 6 = Knowledge base 7= Order 8 = Order item 9 = Default Entry 100 = Custom Independent table Not updateable. Not insertable. a Created automatically by ODBC. Name String 79 User-defined. This field is not required, but it is very important and should not be left blank. Text1 String 254 User-defined. Text2 String 254 User-defined. Text3 String 254 User-defined. Text4 String 254 User-defined. Number1 Integer 10 User-defined. Number2 Integer 10 User-defined. Number3 Integer 10 User-defined. Number4 Integer 10 User-defined. Number5 Integer 10 User-defined. Number6 Integer 10 User-defined. Number7 Integer 10 User-defined. Number8 Integer 10 User-defined. Date1 DateString 10 User-defined.

184 176 Maximizer CRM 10.5 Table 148 Custom_Child Table (Continued) Ref. Time1 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Date2 DateString 10 User-defined. Time2 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Date3 DateString 10 User-defined. Time3 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Date4 DateString 10 User-defined. Time4 TimeString 11 User-defined. Note: The milliseconds of time fields will not be synchronized via MaxExchange. Currency1 Float 15 User-defined. Currency2 Float 15 User-defined. Currency3 Float 15 User-defined. Currency4 Float 15 User-defined. Private Integer 2 See Security Fields on page 50. Owner_Id String 11 See Security Fields on page 50. ReadPriv Integer 2 See Security Fields on page 50. Read_Id String 11 Create_Date DateString 10 See History Fields on page 51. Create_Time TimeString 11 Note: The milliseconds of time fields will not be synchronized via MaxExchange. Creator_Id String 11 See History Fields on page 51. Last_Modify_Date DateString 10 See History Fields on page 51. Last_Modify_Time TimeString 11 Note: The milliseconds of time fields will not be synchronized via MaxExchange.

185 Chapter Table 148 Custom_Child Table (Continued) Ref. Modified_By_Id String 11 Must be populated by the user. Not automatically updated. The Maximizer ODBC driver does not check whether ther user ID entered is valid. Can insert. Can update. Description String 1023 User-defined. a. If the Client_Id / Client_Number are specified and they exist in database, a record is inserted with correct Entity_Type value (automatically determined by ODBC). If the Client_Id / Client_Number are not specified, a record is inserted with Entity_Type = 0. If the Client_Id / Client_Number are specified but they do not exist in database, insertion fails. If the Entity_Type is specified (correct or not) insertion fails with the message Column not updatable.

186 178 Maximizer CRM 10.5

187 179 Index A ABPartners table (Maximizer ODBC) 65 Access control database level 10 field level 11 ODBC 10 record level 11 table level 10 Activity table (Maximizer ODBC) 115 Address Table (Maximizer ODBC) 66 API conformance for ODBC 15 Appointments table (Maximizer ODBC) 85 Automatic_Campaign table (Maximizer ODBC) 98, 102 C CampaignAccounts table (Maximizer ODBC) 100 Client table (Maximizer ODBC) 68 Closing ODBC tables 36 Collating sequence, ODBC 35 Combined_Campaign_User_Fields table (Maximizer ODBC) 102 Combined_Client_User_Fields table (Maximizer ODBC) 63 Combined_CSCase_User_Fields table (Maximizer ODBC) 106 Combined_Opp_User_Fields table (Maximizer ODBC) 106, 117 Company table (Maximizer ODBC) 74 Concurrency,ODBC 36 Contact management tables 64 CSCases table (Maximizer ODBC) 107 Currency table (Maximizer ODBC) 118 Custom_Child table (Maximizer ODBC) 172 Custom_Independent table (Maximizer ODBC) 168 D Data source definition, ODBC 8 Data types supported in ODBC 32 F format, Group ID strings 162 G Group By extensions, ODBC 37 Group ID string format 162 H Hotlist table (Maximizer ODBC) 90 I ID, Group ID string format 162 J Joining, ODBC tip 44 L Left outer join, ODBC 39 limitations Maximizer ODBC 14 SQL statements 35 M Manual_Campaign table (Maximizer ODBC) 103 Maximizer ODBC tables ABPartners 65 Activity 115 Address table 66 Appointments 85 Automatic_Campaign 98, 102 CampaignAccounts 100 Client 68 Combined_Campaign_User_Fields 102 Combined_Client_User_Fields 63 Combined_CSCase_User_Fields 106 Combined_Opp_User_Fields 106, 117 Company 74 contact management 64 CSCases 107 Currency 118 Custom_Child 172 Custom_Independent 168 Hotlist 90 Manual_Campaign 103 Notes 93 OppActivity 119 OppComp 123 OppContact 125 Opportunity 127

188 180 Maximizer CRM 10.5 N opportunity management 112, 141 OppPartners 131 OppRole 133 OppStep 135 OppSuccessFactor 137 People 77 Probability_Close_Range 138 Reasons 140 Related_Entries 82 Role 142 Role_Standing_For_Link 143 Security Group 162 Standing_For_Role 144 Standing_For_Success_Factor 146 Step 147 Step_Activity_Link 149 Strategy 151 Strategy_Role_Link 152 Strategy_Step_Link 156 Strategy_Success_Factor_Link 155 Success_Factor 159 Success_Factor_Standing_Link 160 Team 163 UDF_List 56 UDF_Table_Item 61 User_Details 165 Notes table (Maximizer ODBC) 93 O ODBC 64 access control 10 API conformance 15 closing an open table 36 collating sequence 35 compliant software 9 contact management tables 64 data concurrency 36 defining a data source 8 Group By extensions 37 left outer join 39 limits 14 operating system platforms 14 opportuntity management tables 112, 141 overview 6 precision and scale 35 reference 14 scalar functions 30 security 10 SQL conformance 24 stack size 35 supported data types 32 tips and techniques 44 using 7 Open Database Connectivity 6 Operating system platforms, ODBC 14 OppActivity table (Maximizer ODBC) 119 OppComp table (Maximizer ODBC) 123 OppContact table (Maximizer ODBC) 125 Opportunity management tables, ODBC 112, 141 Opportunity table (Maximizer ODBC) 127 OppPartners table (Maximizer ODBC) 131 OppRole table (Maximizer ODBC) 133 OppStep table (Maximizer ODBC) 135 OppSuccessFactor table (Maximizer ODBC) 137 P People table (Maximizer ODBC) 77 Precision and scale, ODBC 35 prefixes for UDF table names 53 Probability_Close_Range table (Maximizer ODBC) 138 R Reasons table (Maximizer ODBC) 140 reference, ODBC 14 Related_Entries Table (Maximizer ODBC) 82 Role table (Maximizer ODBC) 142 Role_Standing_Link table (Maximizer ODBC) 143 S Scalar functions, ODBC 30 Security database level 10 field level 11 ODBC 10 record level 11 table level 10 Security Group table (Maximizer ODBC) 162 Selecting, ODBC tip 44 SQL conformance 24 SQL statement limitations 35 Stack size, ODBC 35 Standing_For_Role table (Maximizer ODBC) 144 Standing_For_Success_Factor table (Maximizer ODBC) 146 Step table (Maximizer ODBC) 147 Step_Activity_Link table (Maximizer ODBC) 149 Strategy table (Maximizer ODBC) 151 Strategy_Role_Link table (Maximizer ODBC) 152 Strategy_Step_Link table (Maximizer ODBC) 156 Strategy_Success_Factor_Link table (Maximizer ODBC) 155 strings, Group ID format 162 Success_Factor table (Maximizer ODBC) 159 Success_Factor_Standing_Link table (Maximizer ODBC) 160

189 181 T Team table (Maximizer ODBC) 163 U UDF table name prefixes 53 UDF_List table (Maximizer ODBC) 56 UDF_Table_Item table (Maximizer ODBC) 61 Updating, ODBC tip 44 User_Details table (Maximizer ODBC) 165

190 182 Maximizer CRM 10.5