API Developers Guide: Difference between revisions

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Jump to navigation Jump to search
 
(107 intermediate revisions by 6 users not shown)
Line 1: Line 1:
CommitCRM provides various tools in order to read/add/update information in the CommitCRM
{{usermanuals}}
database. These tools include: Programming API and API by Email for updating the
database, and an ODBC Link for pulling information from the database.
The Commit API provides developers with a set of APIs which allow them to perform
database transactions in order to add and update records in the CommitCRM database. The
API can be used as a Programming API by embedding code which uses the API functions,
or as an API by Email which allows you to send XML formatted emails which will be
processed and executed.


=Introduction=
RangerMSP provides various tools in order to read/add/update information in the RangerMSP database.


*'''Programming API'''<br>The Commit API provides developers with a set of API functions which can be used in VB, C++, Delphi and any other programming language that lets you use a standard Windows dll file. It provides the ability to create a connection to CommitCRM's database, add new records to the database and update them.
These tools include:
*'''Programming API (recommended)'''<br>The RangerMSP Programming API provides developers with a set of API functions which can be used in CSharp, VB.NET and C++. The Programming API libraries provide easy-to-use classes and objects which make the development very simple and friendly.
* '''Low-level Programming API''' <br>Provides low-level functions for programmers using other languages, such as VB, Delphi or any other programming language that lets you use a standard Windows dll file. The Programming API includes two sets of functions: Data-Retrieval API and Data-Update API.
*'''API by Email'''<br>The API by Email allows you to send XML formatted emails which contain database transactions. RangerMSP Email Connector then pulls the incoming XML emails from your POP3 mail server, processes the email and performs the transactions in the XML transaction. XML formatted email gives you access to the Data-Update API, which allows you to perform many actions such as linking to external systems, receiving forms submitted from your web site, and more.
*'''Web API'''<br>The Web API allows you to interact with your RangerMSP server and data over the Web using HTTP.
*'''ODBC Link'''<br>In addition to the Data Retrieval API, there is an option of using ODBC to read data directly from the database. RangerMSP uses an open database structure and allows other applications to access the database using ODBC (Open Data Base Connectivity) for '''read-only''' purposes. The ODBC link should not be used from programs you develop (you should use the data retrieval API for this purpose). You can use ODBC Link in order to read data from the database and integrate it with an external system (i.e. Crystal reports, or any other application).




*'''API by Email'''<br>The API by Email allows you to send XML formatted emails which contain database transactions. Commit Email Connector then pulls the incoming XML emails from your POP3 mail server, processes the email and performs the transactions in the XML transaction. XML formatted email gives you an API for the CommitCRM database, which allows you to perform many actions such as linking to external systems, receiving forms submitted from your web site, and more.
__TOC__
 
 
*'''ODBC Link'''<br>While the API provides the means for adding and updating information in the database, you should use ODBC Link in order to read information from the database. CommitCRM uses an open database structure and allows other applications to access the database using ODBC (Open Data Base Connectivity) for '''read-only''' purposes.<br><br>You can use ODBC Link in order to read data from the database and integrate it with an external system (i.e. Crystal reports, or any other application). You may also use the ODBC Link to read Database Record IDs and update existing records. This will be discussed later in this document.
 


__TOC__
=Glossary=
==Glossary==
*'''RangerMSP API (Application Programming Interface)''' - RangerMSP provides an API which allows you to <u>add and update</u> records in the RangerMSP database. The API includes a list of possible actions and parameters.
*'''Commit API (Application Programming Interface)''' - CommitCRM provides an API which allows you to <u>add and update</u> records in the CommitCRM database. The API includes a list of possible actions and parameters.


*'''ODBC Link (Open Data Base Connectivity)''' - ODBC is a function library which provides a common API for ODBC compliant databases. CommitCRM provides an open database and allows other applications to access the database using ODBC for '''read-only''' purposes.
*'''ODBC Link (Open Data Base Connectivity)''' - ODBC is a function library which provides a common API for ODBC compliant databases. RangerMSP provides an open database and allows other applications to access the database using ODBC for '''read-only''' purposes.


*'''Record''' - Each entity in the CommitCRM database (such as Ticket, Account, Asset, Item, Appointment, Task, etc.) is considered a "record".
*'''Record''' - Each entity in the RangerMSP database (such as Ticket, Account, Asset, Item, Appointment, Task, etc.) is considered a "record".


*'''Database fields''' - Each record contains a list of fields, each of which holds the record's data.
*'''Database fields''' - Each record contains a list of fields, each of which holds the record's data.
Line 32: Line 27:
*'''Transaction Parameters''' - Each transaction contains the parameters for performing the transaction: record type, list of database fields and a list of the values to be updated in these fields.
*'''Transaction Parameters''' - Each transaction contains the parameters for performing the transaction: record type, list of database fields and a list of the values to be updated in these fields.


*'''External Application''' - This refers to the external program which integrates with CommitCRM in order to update the database. This name should be passed when performing updates to the database, and it will be saved in the CommitCRM record to indicate who performed the changes.
*'''External Application''' - This refers to the external program which integrates with RangerMSP in order to update the database. This name should be passed when performing updates to the database, and it will be saved in the RangerMSP record to indicate who performed the changes.


*'''Record ID (REC ID)''' - Each record in CommitCRM has a '''unique Record ID''' which is created when adding the record to the database. Every ID is 20 characters and should be transferred with the API transaction when you need to update an existing record.
*'''Record ID (REC ID)''' - Each record in RangerMSP has a '''unique Record ID''' which is created when adding the record to the database. Every ID is 20 characters and should be transferred with the API transaction when you need to update an existing record.


==Using Commit API==
<br>
Commit API allows you to add and update records in the CommitCRM database, such as
Accounts, Tickets, Assets, Items, Appointments, Tasks and more.


The updates are performed using transactions, where each transaction includes the
=Using API=
operation you wish to perform, the data type you wish to add/update, and any additional
parameters (i.e. record type, database fields and their values).


Every record added to the system is assigned a unique Record ID (REC ID) which is the
==Workflow==
database identifier for this record.
Following is a sample work-flow, which demonstrates the process of adding a new Account, and then adding a new Ticket to this Account, using the RangerMSP API.
 
The Commit API allows you to perform the following operations.
 
*'''Add new records''' - if no Record ID is passed in the transaction, the API assumes that this is a new record, adds it to the system and creates a new Record ID for it.
 
*'''Update existing records''' - if the record ID is passed in the transaction, and the record exists, the system will update the record with the information in the transaction.
 
In both cases, the system will try to set default values for fields which do not exist in the
incoming transaction. If it fails, the action will fail with an error.
 
Note that in order to '''read data''' from the CommitCRM database, you should use the ODBC
Link, which provides a read-only link for the CommitCRM database. See more details in
[[Commit API Reference Manual#Retrieving data using ODBC|Retrieving data using ODBC]].
 
===Workflow===
Following is a sample work-flow, which demonstrates the process of adding a new Account, and then adding a new Ticket to this Account, using the Commit API.


Note that the API can return two parameters to the External Application:
Note that the API can return two parameters to the External Application:
#The Commit REC ID - when adding new records to the database, this will contains the new record ID.
#The RangerMSP REC ID - when adding new records to the database, this will contains the new record ID.
#The ExternalTransactionID (relevant for XML transaction only) - In case the external application passes a parameter to be returned with the response, the ExternalTransactionID will be returned as-is to in the response.  
#The ExternalTransactionID (relevant for XML transaction only) - In case the external application passes a parameter to be returned with the response, the ExternalTransactionID will be returned as-is to in the response.  


Line 72: Line 47:
[[File:flow.gif|center]]
[[File:flow.gif|center]]


===Updating existing records===
==Updating existing records==
In order to update an already existing record in the database (e.g. add a Ticket to an
In order to update an already existing record in the database (e.g. add a Ticket to an
Account, update an Account's phone number, add a new Charge to an existing Ticket,
Account, update an Account's phone number, add a new Charge to an existing Ticket,
Line 81: Line 56:
The Record ID can be obtained in the following ways:
The Record ID can be obtained in the following ways:
#'''API Response''' (as in the flow above) - You can extract the newly created Record ID from the Email Response when adding new records with the API. This requires the developer to process the API responses, and extract the returning REC ID for each newly added record.
#'''API Response''' (as in the flow above) - You can extract the newly created Record ID from the Email Response when adding new records with the API. This requires the developer to process the API responses, and extract the returning REC ID for each newly added record.
#'''ODBC Link''' - Use the ODBC Link to find relevant records (Accounts, Tickets, etc.), and read all information from the database, including the unique Record ID.
#'''Data Retrieval API''' - Use the Data Retrieval API functions to find relevant records (Accounts, Tickets, etc.), and read all information from the database, including the unique Record ID.
#'''Manually''' - from the Account's <u>Notes</u> tab, at the bottom, right-click the REC ID field and copy it.
#'''Manually''' - from the Account's <u>Notes</u> tab, at the bottom, right-click the REC ID field and copy it.


Line 87: Line 62:
API and update this record.
API and update this record.


===Programming API===
<br>
The Programming API allows you access the CommitCRM database and perform transactions
 
from within a program (using various programming language). This means you can embed
=Programming API=
code which accesses the CommitCRM database from within your own application, and add
The Programming API allows you access the RangerMSP database and perform transactions from within a program (using various programming language). This means you can embed code which accesses the RangerMSP database from within your own application, and add
your own functionality which updates the database.
your own functionality which updates the database.


The programming API executes database transactions. Each transaction uses API methods
The RangerMSP Programming API provides developers with a set of API functions which can be used in CSharp, VB.NET and C++. The Programming API libraries provide easy-to-use classes and objects which make the development very simple and friendly.
provides by the API dll file which is located in the CommitCRM installation. Both the
 
Programming API and the API by Email use the same dll for performing the transactions.
See more details and samples about each programming environments in the following links:
* [[VB.NET_API|VB.Net Programming API]]
* [[CSharp_API|CSharp Programming API]]
* [[C%2B%2B_API|C++ Programming API]]
<br>
 
<br>
 
= Low Level Programming API=
The Low-level programming API provides a way to use the API from development languages which are not supported by the main Programming API.


Note that the API provides the tools needed for adding/updating information in the
The Low-level programming API executes database transactions. The low-evel API provides two separate dll programs, one for adding/updating data from the database, and one for retrieving data from the database.  
database. In order to retrieve data, you should use the ODBC link which allows you to
connect to the database and retrieve data directly from the tables. You can read more
about it in the [[Commit API Reference Manual#Retrieving data using ODBC|Retrieving data using ODBC]] section.


You can find more information and samples in the [[API Code samples]] section.
<br>For the full list of API functions go to [[API_Reference_Manual#API_Functions|API Functions]].
<br>For samples go to [[API Code Samples]].


===API by Email (XML transaction)===
Note:
The API by Email operates under the Commit Email Connector module, which
Retrieving data can be performed either by the API (recommended) or using ODBC when needed. You can read more about it in the [[API_Developers_Guide#Data_Retrieval|Data Retrieval]] section.
automatically processes incoming emails arriving at a defined public email address. The
Email may contain XML formatted messages which contain API transactions, and provides
a full API to CommitCRM.


The Email Connector pulls incoming emails from your POP3 mail server, and processes the
==Adding and Updating Data==
email. When an email containing XML formatted message is detected, the system analyzes
RangerMSP API allows you to add and update records in the RangerMSP database, such as Accounts, Tickets, Assets, Items, Appointments, Tasks and more.
the XML content of the email and performs the transactions written in the XML. You may
set the Email Connector to send automatic replies in response to XML formatted email.


The API by Email executes database transactions. Each transaction uses API methods
The updates are performed using transactions, where each transaction includes the operation you wish to perform, the data type you wish to add/update, and any additional parameters (i.e. record type, database fields and their values).
provided by the API dll file which is located in the CommitCRM installation. Both the
Programming API and the API by Email use the same dll for performing the transactions.


Every record added to the system is assigned a unique Record ID (REC ID) which is the database identifier for this record.


Note that the API provides the tools for adding/updating information in the database. In
The RangerMSP API allows you to perform the following operations.
order to retrieve data, you should use the ODBC link which allows you to connect to the
database and retrieve data directly from the tables. You can read more about it in the
[[Commit API Reference Manual#Retrieving data using ODBC|Retrieving data using ODBC]] section.


You can find more information and samples in [[API Code Samples#XML samples|XML samples]].
*'''Add new records''' - if no Record ID is passed in the transaction, the API assumes that this is a new record, adds it to the system and creates a new Record ID for it.


==Retrieving data using ODBC==
*'''Update existing records''' - if the record ID is passed in the transaction, and the record exists, the system will update the record with the information in the transaction.
CommitCRM uses an open database and allows other applications to access it using ODBC
 
*'''Retrieve records''' - The Data Retrieval API allows you to perform an SQL Query to get a list of record IDs and retrieve the details for a single record according to a REC ID.
 
Note that in order to '''retrieve data''' using ODBC (e.g. when linking to Crystal Reports), use the ODBC Link, which provides a read-only link for the RangerMSP database. See more details in [[#Data_Retrieval|Retrieving Data]].
 
==Data Retrieval==
RangerMSP uses an open database and the RangerMSP API provides the ability to retrieve data using standard API functions which let you define queries and retrieve data.
 
In addition to the Data Retrieval API, there is an option of using ODBC to read data directly from the database. The ODBC link should not be used from programs you develop (you should use the data retrieval API for this purpose). Use the ODBC link only when you need to access the database from an external program, such as external report application (i.e. Crystal reports, or any other application).
<br>
* Learn more about [[API_Developers_Guide#Data_Retrieval_API|Data Retrieval API]].
* Learn more about [[API_Developers_Guide#ODBC_Data_Retrieval|Data Retrieval using ODBC Link]].
<br>
 
=API by Email (XML transaction)=
The API by Email operates under the RangerMSP Email Connector module, which automatically processes incoming emails arriving at a defined public email address. The Email may contain XML formatted messages which contain API transactions, and provides
a full data update API to RangerMSP.
 
The Email Connector pulls incoming emails from your POP3 mail server, and processes the email. When an email containing XML formatted message is detected, the system analyzes the XML content of the email and performs the transactions written in the XML. You may set the Email Connector to send automatic replies in response to XML formatted email.
 
The API by Email supported only the Data Update API (Data Retrieval API is not supported via emails). The API by Email executes database the transactions using the functions provided by the API dll file which is located in the RangerMSP installation. Both the Programming API and the API by Email use the same dll for performing the transactions.
 
Note that the API by Mail is supported only for the Data Update API, allowing you to add and update data. In order to retrieve data, you should use the Data Retrieval Programming API (recommended) or use ODBC, both methods do not support API by Email. You can read more about it in the  [[API_Developers_Guide#Data_Retrieval|Data Retrieval]] section.
<br><br>
* Learn more about using [[API_by_Email_and_MSP_Integration|API by Email]].
* Learn more about building the XML transactions for the API by Email in [[API Code Samples#XML samples|XML samples]].
<br>
 
=Web API=
 
The Web API allows you to build applications or addons which interact with your RangerMSP server remotely over the Web. You get access to all the API functions and can query the data or add/edit data (or both) giving you unparallelled control over your data. To use the Web API you need to have the RangerMSP Server service, which is also used by the Email Connector and the Alerts Server modules, installed and running and be using the [[#Programming API|Programming API]].
<br><br>
 
You can find details on connecting remotely using various programming environments here:
<br><br>
 
*[[VB.NET_API#Remote_Server_.28Web_API.29|VB.NET]]
*[[CSharp_API#Remote_Server_.28Web_API.29|CSharp]]
*[[C%2B%2B_API#Remote_Server_.28Web_API.29|C++]]
 
<br>
 
For instructions on how to activate the Web API, go to [[Web API Server Configuration]]
<br><br>
 
=Data Retrieval API=
The Data Retrieval API provides API functions which help you execute database queries and receive the results. Each function uses API functions provided by the Retrieval API dll file which is located in the RangerMSP installation. The Data Retrieval API is available only via the Programming API; no API by Email is available for data retrieval.
 
The Data Retrieval API provides the following abilities:
* Execute a database query and receive a result records list.
* Read each record with its fields.
* Find out field properties.
 
See low-level programming API information in [[API_Developers_Guide#Data_Retrieval|Low Level API Data Retrieval]].<br>
See the [[API_Reference_Manual#Data_Retrieval_API_Functions|Data Retrieval API Reference Manual]] for detailed usage description.
<br><br>
 
==ODBC Data Retrieval==
RangerMSP uses an open database and allows other applications to access it using ODBC
(Open Data Base Connectivity) for '''read-only''' purposes. While the API provides the means
(Open Data Base Connectivity) for '''read-only''' purposes. While the API provides the means
for adding and updating information in the database, it is preferred to use ODBC to read
for adding and updating information in the database, it is preferred to use ODBC to read
Line 135: Line 166:
You can use ODBC Link to read data from the database and integrate it with an external
You can use ODBC Link to read data from the database and integrate it with an external
system (i.e. Crystal reports, or any other application). You may also use the ODBC Link in
system (i.e. Crystal reports, or any other application). You may also use the ODBC Link in
order to read the Database Record ID and update existing records (see [[Commit API Reference Manual#Updating existing records|Updating existing records]]).
order to read the Database Record ID and update existing records (see [[API_Developers_Guide#Updating_existing_records|Updating existing records]]).


<u>'''Activation Notes:'''</u>
<u>'''Activation Notes:'''</u>


*ODBC connection is not officially supported yet, and although ODBC itself is well tested, we do not provide "pure ODBC" support.
*The ODBC drivers are well tested and work well, however, please note that the RangerMSP Support team doesn't provide "pure ODBC" support.


*NEVER use ODBC to modify or delete data; use it for READ purposes only. Modifying data should be done using the Commit API.
*NEVER use ODBC to modify or delete data; use it for READ purposes only. Modifying data should be done using the RangerMSP API.


*The ODBC Link can be used with your installed version of CommitCRM, and only requires installing an external driver. Before working with the API we recommend that you '''backup the database'''.
*The ODBC Link can be used with your installed version of RangerMSP, and only requires installing an external driver. Before working with the API we recommend that you '''backup the database'''.
 
*We also suggest that the CommitCRM application <u>not be in use</u> while data is being accessed with ODBC (this includes the CommitWebInterface and CommitServer services if they are in use). This may prevent data sharing issues.




Line 151: Line 180:
{| class="wikitable"
{| class="wikitable"
|-
|-
! '''CommitCRM Record'''
! '''RangerMSP Record'''
! '''Database Table Name'''
! '''Database Table Name'''
|-
|-
Line 185: Line 214:
|}
|}


For the database fields list, please refer to [[Commit API Reference Manual#API Reference Manual|API Reference Manual]] section.
For the database fields list, please refer to [[API_Developers_Guide#API_Reference_Manual|API Reference Manual]] section.
You can find detailed instructions for using the ODBC Link in the [[Commit API Reference Manual#Installing ODBC Driver|Installing ODBC Driver]] section.
You can find detailed instructions for using the ODBC Link in the [[API_Developers_Guide#Installing_ODBC_Driver|Installing ODBC Driver]] section.




Line 205: Line 234:


To install the Advantage ODBC Driver:
To install the Advantage ODBC Driver:
#[http://www.commitcrm.com/downloads/commit-odbc-8-1-0-26.exe Click here] to download the Advantage ODBC setup program.
#Download the ODBC driver version that corresponds with '''your''' Advantage SQL Database Server version from the following links: (The Advantage Version number can be found in the [[Media:ADS_Version.jpg|Advantage Configuration Utility]] located on the RangerMSP Server)<br> '''[http://{{SERVERNAME}}/downloads/crm-odbc-11-10-0-10-64bit.exe ODBC Driver Version 11.10 – 64 bit]<br> [http://{{SERVERNAME}}/downloads/crm-odbc-11-10-0-10.exe ODBC Driver Version 11.10 – 32 bit]<br>[http://{{SERVERNAME}}/downloads/crm-odbc-10-10-0-28.exe ODBC Driver Version 10.10 – 32 bit]<br> [http://{{SERVERNAME}}/downloads/crm-odbc-10-0-0-3.exe ODBC Driver Version 10.0 – 32 bit]<br> [http://{{SERVERNAME}}/downloads/crm-odbc-9-0-0-7.exe ODBC Driver Version 9.0 – 32 bit]<br> [http://{{SERVERNAME}}/downloads/crm-odbc-8-1-0-26.exe ODBC Driver Version 8.1 – 32 bit] (**Also for systems that do not use the RangerMSP SQL Database)<br> '''
#Run the Setup program.
#Run the Setup program.
#Proceed through the setup windows to complete installation.
#Proceed through the setup windows to complete installation.
'''**DISCLAIMER: Using the ODBC connector without the RangerMSP SQL Database is not recommended, since the chances for Database Corruption would be elevated.'''


<u>'''Data Source Setup for Windows'''</u><br>
<u>'''Data Source Setup for Windows'''</u><br>
Line 225: Line 255:
#From the ODBC Administrator, click Add.
#From the ODBC Administrator, click Add.
#Highlight the Advantage SQL ODBC line, and click OK.
#Highlight the Advantage SQL ODBC line, and click OK.
#Type a unique data source name. For example, type AdvData. This name is used by applications to reference the data source.
#Type a unique data source name. For example, type RangerMSPData. This name is used by applications to reference the data source.
#Specify the database or data dictionary path. Type a valid path name to a mapped drive on the server where the Advantage Database Server is installed or the path and file name of your Advantage Data Dictionary. Click Browse to select a database path or check the Data Dictionary check box and then browse to select a data dictionary file. Note Multiple Advantage data sources may need to be defined for your environment. If different settings are needed for ODBC connections in one application, separate data sources may be required.
#Specify the path to the database - point to folder: \RangerMSP\Db (do '''not''' use the data dictionary option). Click Browse to select a database path. Note Multiple Advantage data sources may need to be defined for your environment. If different settings are needed for ODBC connections in one application, separate data sources may be required.
#When using RangerMSP SQL Database select the '''Remote''' Server option and unselect the Local and Internet ones.
#Review the options and change them to your desired setup.
#Review the options and change them to your desired setup.
#Once the Options are reviewed and/or altered, click OK to exit and save the settings. The new data source is displayed.
#Once the Options are reviewed and/or altered, click OK to exit and save the settings. The new data source is displayed.
Line 286: Line 317:
|}
|}


==Samples==
===Troubleshooting===
The Commit API allows you to add/update the following entities:
In case when using applications you developed with ODBC you receive one of the following errors:
*Accounts
Error 6420:  The 'discovery' process for the Advantage Database Server failed. Unable to connect to the Advantage Database Server.  axServerConnect
*Assets
or
*Tickets
Error 5033:  No connected server was found for the given drive letter.
*Charges
*Appointments
*Tasks
*History Notes
*Opportunities
*Documents
*Knowledge Base Articles


Each API method requires a list of parameters which contain the field names and their values. The field names are the Database field names. You can see each field's name within the application (so you can verify which field you are about to update), by right-clicking the field and selecting Field Settings > Advanced Tab > view the Tech. Rec ID field.
You should perform the following:


You can view the complete list of database fields in the [[Commit API Reference Manual#API Reference Manual|API Reference Manual]] above.
1. [[SQL_Database_Troubleshooting#ADS.ini_.E2.80.93_Server_Locator|Configure the ADS.ini file]]  


Following are samples for using the API by Email and the Programming API. The samples are basic and provide an easy starting point.
2. Copy the ADS.ini file you prepared from the RangerMSP server folder into the following folder on each the affected workstation:


See [[API Code Samples]].
* '''%Windir%\system32'''


==API Reference Manual==
This folder usually translates to: '''C:\Windows\system32'''


The API allows you to add/update the following entities:
'''Note:''' To open these folders on your PC you can paste the paths listed above into a Windows Run dialog box, or into any Windows Explorer path.
*Accounts
*Assets
*Tickets
*Charges (and Contract-price Charges)
*Appointments
*Tasks
*History Notes
*Opportunities
*Documents
*Knowledge Base Articles


You can find a detailed listing of the database fields on the [[API Reference Manual]].  
3. Change the database path configured for ODBC connection to include the server IP address and port used by Advantage Database Server, for example:
\\192.168.0.1:6262\RangerMSP\Db


===Troubleshooting ODBC in 64 Bit Operating Systems===
The RangerMSP ODBC drivers are mainly distributed for 32-bit operating systems; however, the same drivers are supported on the 64-bit operating systems (I.e. Windows 7 x64), and can be used to retrieve data from the RangerMSP database.


<br>


===Account Fields===
===Configuring Data Source in 64-Bit Systems===
The following table lists the most important parameters for adding/updating Account
When installing the ODBC drivers on 64-bit operating systems, the ODBC drivers may not be displayed in the default ODBC manager in windows control panel. In order to view the 32-bit ODBC manager in a 64-bit operating system, you’ll need to browse to '''%windir%\SysWOW64\odbcad32.exe''' and run the 32 bit ODBC Administrator manually. Once the data source has been configured there, you should be able to select the data source in your 3rd party ODBC programs.
records.
Note slight differences when adding a main account vs. adding a secondary contact.


{| class="wikitable"
<br>
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Account REC ID
| FLDTKTCARDID
|The Account record ID (20 chars). The Account Rec ID can be taken from:
#Account Notes tab, at the bottom, rightclick the RecID field and use Copy. <br>e.g. CRDVQYSOD1B4U4HZIQJJ
#Using ODBC to pull information from the database.
#From the Email Response when adding new Account with the API.
|-
| Address: Line1
| FLDCRDADDRESS1
|
|-
| Address: Line2
| FLDCRDADDRESS2
|
|-
| Address: Line3
| FLDCRDADDRESS3
|
|-
| Account Manager
| FLDCRDASSIGNCARDID
| This field has two roles:
#When adding a main Account:<br>The account manager should contain the ID of the Employee who is the account manager.
#When adding a secondary contact:<br>
This field should contain the ID of the main Account to which the secondary contacted is
added.
|-
| Assistant
| FLDCRDASSISTANT
|
|-
|Contract
|FLDCRDBCRECID
|The default Contract for this Account (not required)
|-
|Account Number
|FLDCRDCARDID2
|
|-
|ID
|FLDCRDCARDID3
|
|-
|Popup Message
|FLDCRDCARDMESSAGE
|
|-
|Address: City
|FLDCRDCITY
|
|-
|Address: Zip
|FLDCRDZIP
|
|-
|Company name
|FLDCRDCOMPANY
|
|-
|Contact: First & Last Name
|FLDCRDCONTACT
|
|-
|Address: State
|FLDCRDCOUNTRY
|
|-
|Creation Date
|FLDCRDCREATEDATE
|Any date format, such as DD/MM/YYYY
|-
|Created by User
|FLDCRDCREATEUSERID
|Foreign Software Name which created the account
|-
|Dear
|FLDCRDDEAR
|
|-
|Department
|FLDCRDDEPARTMENT
|
|-
|Documents Store Directory
|FLDCRDDOCSFOLDER
|
|-
|E-Mail Address 1
|FLDCRDEMAIL1
|
|-
|E-Mail Address 2
|FLDCRDEMAIL2
|
|-
|Account Type
|FLDCRDENTITYKIND
|When adding a Main Account = 1<br>When adding a secondary contact = 5
|-
|Fax Number
|FLDCRDFAX1
|
|-
|Fax Number Extension
|FLDCRDFAXDESC1
|
|-
|File as
|FLDCRDFULLNAME
|
|-
|Type
|FLDCRDKIND
|
|-
|Last Name
|FLDCRDLASTNAME
|
|-
|Notes
|FLDCRDNOTES
|
|-
|Field
|FLDCRDPERSONID
|
|-
|Phone 1 Ext.
|FLDCRDPHNDESC1
|
|-
|Phone 2 Ext.
|FLDCRDPHNDESC2
|
|-
|Phone 3 Ext.
|FLDCRDPHNDESC3
|
|-
|Phone 4 Ext.
|FLDCRDPHNDESC4
|
|-
|Phone 1
|FLDCRDPHONE1
|
|-
|Phone 2
|FLDCRDPHONE2
|
|-
|Phone 3
|FLDCRDPHONE3
|
|-
|Phone 4
|FLDCRDPHONE4
|
|-
|Region
|Region FLDCRDREGIONCODE
|
|-
|Popup Message: Display Indication
|FLDCRDSHOWMESSAGE
|
|-
|Address: Country
|FLDCRDSTATE
|
|-
|Sub-Contact Code
|FLDCRDSUBCODE
|
|-
|Salutation
|FLDCRDSUFFIX
|
|-
|Tax1
|FLDCRDTAXCODE1
|
|-
|Tax2
|FLDCRDTAXCODE2
|
|-
|Notes
|FLDCRDNOTES
|
|-
|Title
|FLDCRDTITLE
|
|-
|Last Updated by
|FLDCRDUPDATEUSERID
|When performing updates on existing Account - pass the Foreign Software Name which performs the update.
|-
|Web Address 1
|FLDCRDURL1
|
|-
|Web Address 2
|FLDCRDURL2
|
|-
|Status
|FLDCRDUSER1
|
|-
|Field1
|FLDCRDUSER2
|
|-
|Field2
|FLDCRDUSER3
|
|-
|Field3
|FLDCRDUSER4
|
|-
|Field4
|FLDCRDUSER5
|
|}
 
===Ticket Fields===
 
The table below lists the most important Ticket parameters and behavior:
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Account REC ID
| FLDTKTCARDID
|The Account record ID (20 chars). The Account Rec ID can be taken from:
#Account Notes tab, at the bottom by rightclicking the REC ID field and selecting Copy
#ODBC to pull information from the database
#The automated email response when adding a cnew Account with the API
|-
| Contact REC ID
| FLDTKTCONTACTID
|The Contact for this Account. If not provided, the main Contact for the Account is taken.
|-
| Contract REC ID
| FLDTKTBCRECID
|The Contract ID. If not supplied, will be taken from the Account's default contract.
|-
| Emp. REC ID
| FLDTKTWORKERID
|The worker ID to be linked to the Ticket. Must be an active employee. This is an optional  parameter. If not passed, the system default will be used.
|-
| Priority
| FLDTKTPRIORITY
| The ticket priority. If not passed in the transaction, the default value for new Tickets will be used.
Immediate = 10<br>High = 20<br>Normal = 30<br>Low = 40<br>Not Applicable= 50
|-
| Ticket Number
| FLDTKTTICKETNO
| The Ticket number. If passed, must be an existing Ticket, and this will update the Ticket with the details in the transaction.
|-
|Description
|FLDTKTPROBLEM
|This is the Ticket Description. This is a mandatory field, which must contain text.
|-
|Ticket Type
|FLDTKTKIND
|Ticket Type (optional). The Ticket Type string should be passed. If not provided, default is used.
|-
|Source
|FLDTKTSOURCE
|
|-
|Estimated Duration Time
|FLDTKTSCHEDLENESTIM
|Estimated duration time for the Ticket in minutes.
|-
|Show Ticket in Dispatcher
|FLDTKTFORDISPATCH
|Possible values: Yes/No
|-
|Status
|FLDTKTSTATUS
|The Ticket Status (optional).<br>
Possible values:<br>
New = 100<br>
Pending = 200<br>
Scheduled = 300<br>
In-House Service = 400<br>
On-Site Service = 500<br>
Laboratory Service = 600<br>
Hold = 700<br>
Other = 800<br>
Canceled = 900<br>
Completed = 1000
|-
|Created by User
|FLDTKTCREATEUSER
|Should contain the external software name which created the Ticket
|-
|Due Date
|FLDTKTDUEDATETIME
|Due date for the Ticket. Should be passed in date format. e.g. MM/DD/YYYY
|-
|Resolution
|FLDTKTSOLUTION
|Ticket resolution text
|}


===Charge Fields===
=Samples=
The table below lists the most important Charge parameters and behavior.
For basic samples that provide an easy starting point see the following:
 
* [[VB.NET_API#Complete_Program_Sample|VB.NET Code Sample]].
Contract-price Charges have some special characteristics (see comments marked by * in
* [[CSharp_API#Complete_Program_Sample|CSharp Code Sample]].
the table below):
* [[C%2B%2B_API#Complete_Program_Sample|C++ Code Sample]].
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Record ID
| FLDSLPRECID
|The Charge record ID. If provided, the existing Charge will be updated. Otherwise, this will be
added as a new Charge.
|-
| Charge Source
| FLDSLPSOURCERECID
|The Charge source is the entity for which the charge is created.<br>
Possible values:
*Linked Contract RecID (for Contract-price Charges). Cannot be the "System Global Contract".
**Passing the Contract RecID indicates that this is a Contract-price charge.
*Entity RecID from which the charge is created (for example when creating a charge from an Appointment or Task).
|-
| Account REC ID
| FLDSLPCARDID
|The Account record ID (20 chars). The Account REC ID can be taken from:
#Account Notes tab, at the bottom by rightclicking the REC ID field and selecting Copy
#ODBC to pull information from the database
#The automated email response when adding a new Account with the API
|-
| Employee REC ID
| FLDSLPWORKERID
| The worker record ID to be linked to the Charge. Must be an active employee. This is an optional parameter. If not passed, the system default will be used.
|-
| Charged Item
| FLDSLPITEMID
| The Item Record ID to be linked to the Charge. This is a mandatory field.
*For Contract-price Charge can be only Fixed-Price, Unit-based Item.
|-
| Contract REC ID
| FLDSLPBCRECID
| The contract record ID (must be a Contract of the Account)
|-
|Ticket REC ID
|FLDSLPTICKETID
|The Ticket ID to be linked to the Charge.
*Not relevant for Contract-price Charge
|-
|Date
|FLDSLPSLIPDATE
|The date for the Charge. This is an optional parameter. If not provided, the current date will
be used. Should be passed in date format. e.g. MM/DD/YYYY
|-
|Description
|FLDSLPDESC
|The Charge Description. If not provided, will be taken from the Item's description.
|-
|Units/Hours
|FLDSLPQUANTITY
|This is the quantity of hours/units
|-
|Adjust Amount
|FLDSLPADJUSTAMOUNT
|Discount/Markup amount. Positive number means Markup, negative number means Discount.
|-
|Adjust Percent
|FLDSLPADJUSTPERCENT
|Discount/Markup in percentage, must be between (-100) - 100. Positive number means Markup, negative number means Discount.
|-
|From Time
|FLDSLPSTARTTIME
|From time for labor Charges e.g. 12:06
*Not relevant for Contract-price Charge
|-
|To Time
|FLDSLPENDTIME
|From time for labor Charges e.g. 14:50
* Not relevant for Contract-price Charge
|-
|Price/Rate
|FLDSLPPRICE
|If not provided, the price is taken from the Item.
|-
| Billable
| FLDSLPBILLKIND
| B - Billable<br>
N - Not Billable<br>
If not provided, will be set according to the Contract type.
|-
| Billed
| FLDSLPSTAGE
| D - Draft
B - Billed
|-
| Field1
| FLDSLPUSER1
| User defined field
|-
| Create User
| FLDSLPCREATEUSER
| External software name which created the Charge
|}


===Item Fields===


The table below lists the most important Item parameters and behavior:
For Low-Level API and XML samples see:
* [[API Code Samples#Data Retrieval API Samples|Data Retrieval API Samples]].
* [[API Code Samples#Data Update API Samples|Data Update API Samples]].
* [[API Code Samples#XML samples|XML samples]].


{| class="wikitable"
=API Reference Manual=
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Record ID
| FLDSLPRECID
|The Item record ID. If provided, the existing item will be updated. Otherwise, this will be added as a new item.
|-
| Item Group
| FLDITMITEMTYPEGROUP
|The Item Group to be linked to the Charge. This is a mandatory field:<br>
F - Labor (Fee)<br>
X - Expense<br>
P - Part
|-
| Item Code
| FLDITMITEMNO
|The item code is a mandatory field
|-
| Item Name
| FLDITMNAME
| The item name is a mandatory field
|-
| Price Source
| FLDITMPRICESOURCE
| F - Fixed Price<br>
W - by Employee Rate
|-
| Price per Hour/Unit
| FLDITMUNITISHOUR
| This field indicated whether the price is unitbased or hours-based.<br>
Y - by Hours<br>
N - by Units<br>
This is an optional field, depending on the Item Group. For example, if the item group is Labor, and Price Source is By Employee, the value will always be by hours
|-
|Price
|FLDITMUNITPRICE
|Must be a valid numeric value
|-
|Cost
|FLDITMSTANDARDCOST
|The date for the Charge. This is an optional parameter. If not provided, the current date will
be used. Should be passed in date format. e.g. MM/DD/YYYY
|-
|Taxes
|FLDITMTAXCODE1<br>
FLDITMTAXCODE2<br>
FLDITMTAXCODE3
|You can pass up to 3 different tax codes.
|-
|Description by Name
|FLDITMDESCBYNAME
|Y - take the description from the name field<br>
N - take the description from the Description field
|-
|Description
|FLDITMDESC
|If not provided, the description is taken from the name.
|-
|Suspend
|FLDITMSUSPENDED
|Indicated whether this item is currently suspended:<br>
Y - yes<br>
N - no
|-
|Notes
|FLDITMNOTES
|
|-
|Field1
|FLDSLPUSER1
|User defined field
|-
|Create User
|FLDSLPCREATEUSER
|External software name which created the Charge
|-
| Created by User
| FLDTKTCREATEUSER
| Should contain the external software name which created the Ticket
|}


===History Note Fields===
Find a detailed listing of the database fields in the [[API Reference Manual]].
The table below lists the most important History Note parameters and behavior:


{| class="wikitable"
=See Also=
|-
*[[VB.NET_API|VB.Net Programming API]]
! '''Field Name'''
*[[CSharp_API|CSharp Programming API]]
! '''Database Field Name'''
*[[C%2B%2B_API|C++ Programming API]]
! '''Comment'''
*[[Email Connector|RangerMSP Email Connector]]
|-
| Record ID
| FLDHISRECID
|The History Note record ID. If provided, the existing History Note will be updated. otherwise, this will be added as a new History Note.
|-
| Date
| FLDHISNOTEDATETIME
|Any date format, such as DD/MM/YYYY
|-
| Description
| FLDHISDESCRIPTION
| The Description text
|-
| Opportunity/Ticket/Contract
| FLDHISLINKRECID
| Link to Opportunity or Ticket or Contract
|-
| Field
| FLDHISUSER1
| User defined field
|-
| About
| FLDHISKIND
| Optional field
|-
|Employee
|FLDHISWORKERID
|The worker ID to be linked to the Ticket. Must be an active employee. This is an optional parameter. If not passed, the system default will be used.
|-
|Account
|FLDHISCARDID
|The Account record ID (20 chars). The Account Rec ID can be taken from:
#Account Notes tab, at the bottom, right-click the REC ID field and use Copy. <br>e.g. CRDVQYSOD1B4U4HZIQJJ
#Using ODBC to pull information from the database
#From the Email Response when adding new Account with the API
|-
|Contact
|FLDHISCONTACTID
|The Contact for this Account. If not provided, the main Contact for the Account is taken.
|-
|Document
|FLDHISDOCID
|Linked Document ID, can be taken from the Document Properties window (right-click RecID and use Copy), or using the ODBC to pull information from the database.
|-
|Created by User
|FLDHISCREATEUSER
|Name of the external software which created this History Note
|}
 
===Asset Fields===
The table below lists the most important Asset parameters and behavior:
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Asset Code
| FLDASTASSETCODE
|If an existing Asset Code is provided, then existing Asset is updated. Otherwise a new Asset is added.
|-
| Asset Type
| FLDASTASSETTYPE
|The Type field is mandatory:<br>
Hardware = H<br>
Software = S<br>
Other = T
|-
| Asset Name
| FLDASTNAME
|
|-
| Status
| FLDASTSTATUS
| Mandatory field.<br>
Active = A<br>
Not Active = N<br>
If not provided, default Active is used.
|-
| Record ID
| FLDASTRECID
| If provided, must exist in the database. Ignored if empty
|-
| Serial No.
| FLDASTSERIALNO
|
|-
|Account
|FLDASTACCRECID
|The Account which is linked to the Asset
|-
|Contact
|FLDASTCONTACTRECID
|The Contact for this Account. If not provided, the main Contact for the Account is taken.
|-
|Created by user
|FLDASTCREATEUSER
|Name of external software which created this Asset
|-
|Purchase Date
|FLDASTCUSTPURDATE
|Any date format, such as DD/MM/YYYY
|-
|Purchased From Us
|FLDASTCUSTPURFROMUS
|Possible values: Y/N.<br>
If not provided, default value Y is used.
|-
| Purchase Invoice #
| FLDASTCUSTPUROURINV
|
|-
| Customer PO
| FLDASTCUSTPURPO
|
|-
| Purchase Price
| FLDASTCUSTPURPRICE
|
|-
| Delivered Date
| FLDASTDELIVEDATE
|
|-
| Description
| FLDASTDESC
|
|-
| Installed By
| FLDASTINSTALBY
|
|-
| Installed Date
| FLDASTINSTALDATE
|
|-
| License Codes
| FLDASTLICENSECODE
|
|-
| License Keys
| FLDASTLICENSEKEY
|
|-
| License Notes
| FLDASTLICENSENOTES
|
|-
| Location
| FLDASTLOCATION
|
|-
| Manufacturer
| FLDASTMANUFACTURER
|
|-
| Mnf Serial No.
| FLDASTMNFSERIALNO
|
|-
| Model
| FLDASTMODEL
|
|-
| Notes
| FLDASTNOTES
|
|-
| Quantity
| FLDASTQUANTITY
| If not provided, default value of 1 is used.
|-
| Last Update By
| FLDASTUPDATEUSER
| Name of externals software which performed the update
|-
| Field1
| FLDASTUSER1
| User defined field
|-
| Field2
| FLDASTUSER2
| User defined field
|-
| Field3
| FLDASTUSER3
| User defined field
|-
| Field4
| FLDASTUSER4
| User defined field
|-
| Field5
| FLDASTUSER5
| User defined field
|-
| Date1
| FLDASTUSERDATE1
| User defined field
|-
| Number1
| FLDASTUSERNUMBER1
| User defined field
|-
| Vendor Purchased Date
| FLDASTVENDORDATEPURC
|
|-
| Vendor Invoice #
| FLDASTVENDORINVNO
|
|-
| Vendor PO
| FLDASTVENDOROURPO
|
|-
| Vendor Price
| FLDASTVENDORPRICE
|
|-
| Vendor
| FLDASTVENDORRECID
|
|-
| Vendor Serial No.
| FLDASTVENDORSERNO
|
|-
| Vendor Warranty Exp. Date
| FLDASTVENDORWARREXP
| Any date format, such as DD/MM/YYYY
|-
| Version
| FLDASTVERSION
|
|-
| Warranty/License Exp.
| FLDASTWARREXPDATE
| Any date format, such as DD/MM/YYYY
|-
| Date
|
|
|}
 
===Calendar Fields===
The table below lists the most important Calendar parameters and behavior:
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Record ID
| FLDEVTRECID
|The Appointment/Task record ID. If provided, the existing entity will be updated. Otherwise, this
will be added as a new Appointment/Task.
|-
| Event Type
| FLDEVTWRITETOID
|The Event type is a mandatory field.<br>
Appointment = 1<br>
Task = 2
|-
| Employee
| FLDEVTWORKERID
| The Task/Appointment owner (for private events)
|-
| Private: User
| FLDEVTPRIVATEID
| Possible values: Y/N<br>
If an Employee was set, this field must be Y
|-
| Account
| FLDEVTCARDID
| The Account record ID (20 chars). The Account REC ID can be taken from:
#Account Notes tab, at the bottom by rightclicking
the REC ID field and selecting Copy
#ODBC to pull information from the database
#The automated email response when adding a
new Account with the API
|-
| Contact
| FLDEVTCONTACTID
| The Contact for this Account. If not provided, the main Contact for the Account is taken.
|-
|Document
|FLDEVTDOCID
|Linked Document ID, can be taken from the Document Properties window (right-click RecID and use Copy), or using the ODBC to pull information from the database.
|-
|Done Indication
|FLDEVTDONE
|Possible values: Y/N
|-
|Date
|FLDEVTEVENTDATE
|The Appointment/Task date is a mandatory field of Any date format, such as DD/MM/YYYY. If not
provided, the current date will be used.
|-
|Description
|FLDEVTFREETEXT
|
|-
|Time: Start
|FLDEVTFROMTIME
|Mandatory field
|-
| Time: End
| FLDEVTTOTIME
| Relevant only for Appointments. If this parameter is not provided, 30 min. interval from Start Time is used.
|-
| Opportunity/Ticket
| FLDEVTLINKRECID
| Linked Ticket/Opportunity/Contract/Asset
|-
| Field1
| FLDEVTFAMILY
| User Defined field
|-
| Field2
| FLDEVTACTION
| User Defined field
|-
| Field3
| FLDEVTPLACE
| User Defined field
|-
| Field4
| FLDEVTPLACE1
| User Defined field
|-
| Field5
| FLDEVTPLACE2
| User Defined field
|-
| Created by User
| FLDEVTCREATEUSERID
| Name of external software which created the event
|-
| Last Update: By User
| FLDEVTUPDATEUSER
| Name of external software which updated the
event
|}
 
 
===Opportunity Fields===
The table below lists the most important Opportunity parameters and behavior:
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Record ID
| FLDOPPRECID
| The Opportunity record ID. If provided, the existing Opportunity will be updated. Otherwise, this will be added as a new Opportunity.
|-
| Opportunity Name
| FLDOPPNAME
| Mandatory field.
|-
| Opportunity ID
| FLDOPPUSERID
| Optional (Oppty ID)
|-
| Account
| FLDOPPCARDID
| The Account record ID (20 chars). The Account REC ID can be taken from:
#Account Notes tab, at the bottom by right-clicking the REC ID field and selecting Copy
#ODBC to pull information from the database
#The automated email response when adding a new Account with the API
|-
| Contact
| FLDEVTCONTACTID
| The Contact for this Account. If not provided, the main Contact for the Account is taken.
|-
| Source
| FLDOPPSOURCE
|
|-
|Document
|FLDEVTDOCID
|Linked Document ID, can be taken from the Document Properties window (right-click RecID and use Copy), or using the ODBC to pull information from the database.
|-
|Done Indication
|FLDEVTDONE
|Possible values: Y/N
|-
|Close Date
|FLDOPPCLOSEDATE
|
|-
|Manager
|FLDOPPWORKERID
|The Manager's REC ID
|-
|Open Date
|FLDOPPOPENDATE
|
|-
| Close By Date
| FLDOPPESTDATE
| Opportunity must be closed by this date
|-
| Amount
| FLDOPPAMOUNT
|
|-
| Probability %
| FLDOPPPROBABILITY
|
|-
| Stage
| FLDOPPSTAGE
|
|-
| Status
| FLDOPPSTATUS
|
|-
| Closing Amount
| FLDOPPCLOSEAMOUNT
|
|-
| Description
| FLDOPPDESCRIPTION
|
|-
| Opportunity Type
| FLDOPPKIND
|
|-
| Opportunity Reason
| FLDOPPREASON
|
|-
| Note
|  FLDOPPNOTES
|
|-
|  Territory
|  FLDOPPREGION
|
|-
|  Field1
|  FLDEVTFAMILY
| User Defined field
|-
|  Field2
|  FLDEVTACTION
| User Defined field
|-
|  Field3
|  FLDEVTPLACE
| User Defined field
|-
|  Created by User
|  FLDEVTCREATEUSERID
| Name of external software which created the event
|-
|  Last Update: By User
|  FLDEVTUPDATEUSER
| Name of external software which updated the event
|}
 
===Document Fields===
The table below lists the Document parameters and behavior:
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Record ID
| FLDDOCRECID
| The Document record ID. If provided, the existing Document will be updated. Otherwise, this will be added as a new Document.
|-
| Document Date
| FLDDOCDOCDATE
| The date for the Document. This is an optional parameter. If not provided, or if the value is illegal, the current date will be used. Should be passed in date format. e.g. MM/DD/YYYY
|-
| Subject
| FLDOPPUSERID
|
|-
| Linked Record
| FLDDOCLINKRECID
| The RECID of a linked object. Each Document can be linked to one of the following objects:
*Ticket
*Contract
*Opportunity
*Knowledge Base Article
*Asset
The Record ID (20 chars) can be taken from:
#Object's Notes tab, at the bottom by right-clicking the REC ID field and selecting Copy
#ODBC to pull information from the database
#The automated email response when adding a new object with the API.
|-
| Account Rec ID
| CARDID
| The Account record ID (20 chars). The Account REC ID can be taken from:
#Account Notes tab, at the bottom by right-clicking the REC ID field and selecting Copy
#ODBC to pull information from the database
#The automated email response when adding a new Account with the API
|-
| Contact REC ID
| FLDDOCCONTACTID
| The Contact for this Account. If not provided, the main Contact for the Account is taken.
|-
|Field1
|FLDDOCTRANSPORT
|User Defined field
|-
|Field2
|FLDDOCFOLDER
|User Defined field
|-
|Field3
|FLDDOCUMENTPLACE
|User Defined field
|-
|File Path + File name
|FLDDOCDOCUMENTNAME
|The Document path
|-
|Category
|FLDDOCTREEID
|The category record ID should be taken from the database table called TreeTbl which contains the Category tree
|-
| Employee REC ID
| FLDDOCWORKERID
| The worker record ID to be linked to the Document. Must be an active employee. This is an optional parameter. If not passed, the system default will be used.
|-
| Created by User
| FLDDOCCREATEUSER
| Name of external software which created the document
|-
| Last Update: By User
| FLDDOCUPDATEUSER
| Name of external software which updated the document
|}
 
===Knowledge Base Article Fields===
The table below lists the Knowledge Base Article parameters and behavior:
 
{| class="wikitable"
|-
! '''Field Name'''
! '''Database Field Name'''
! '''Comment'''
|-
| Record ID
| FLDKBARECID
| The Article record ID. If provided, the existing Article will be updated. Otherwise, this will be added as a new Article.
|-
| Document Date
| FLDKBACREATEDATE
| The date for the Document. This is an optional parameter. If not provided, or if the value is illegal, the current date will be used. Should be passed in date format. e.g. MM/DD/YYYY
|-
| Title
| FLDKBATITLE
|
|-
| Problem
| FLDKBAPROBLEM
|
|-
| Solution
| FLDKBASOLUTION
|
|-
| Status
| FLDKBASTATUS
| Possible values:
*DRAFT = 'D'
*PUBLISHED = 'P'
*OBSOLETE = 'O'
|-
|Category
|FLDKBACATEGORY
|
|-
|Public
|FLDKBAISPUBLIC
|Is the Document public.<br>
Possible values:<br>
*'Y' = Yes
*'N' = No
|-
|Created by User
|FLDDOCCREATEUSER
|Name of external software which created the document
|-
|Last Update: By User
|FLDDOCUPDATEUSER
|Name of external software which updated the document
|}
 
 
===Error Codes Description===
<u>These error codes are returned when calling the CmtGetDescriptionByStatus function:</u><br>
'''1000''' CmtDbEng.dll not found.<br>
'''1001''' Invalid value for the Data Kind value.<br>
'''1002''' Invalid DATA buffer received. Make sure you have allocated the buffer correctly and
that you have passed the correct buffer length.<br>
'''1003''' Invalid MAP buffer received. Make sure you have allocated the buffer correctly and
that you have passed the correct buffer length.<br>
'''1004''' Invalid REC ID buffer received. Make sure you have allocated the buffer correctly
and that you have passed the correct buffer length.<br>
'''1005''' Invalid LOG buffer received. Make sure you've allocated the buffer correctly and
that you've passed the correct buffer length.<br>
'''1006''' Invalid REC ID buffer received. It should be at least 20 characters.<br>
'''1007''' Invalid external software name received. Specify a unique name that identifies your
software.<br>
'''1008''' Cannot process the transaction. Make sure to call the INIT procedure at least once
prior to sending transactions for processing.<br>
'''1009''' Path specified for Commit DB folder not found.<br>
'''1010''' Path specified for Commit DB folder found, but its contents do not reflect a valid DB
folder.<br>
'''1011''' The RED ID received for the employee/user was not found in Commit, is invalid or is
related to an inactive employee record.<br>
'''1012''' Error registering software.<br>
'''1013''' Software name is missing. Make sure you specify a name that identifies your
software.<br>
'''1014''' Software name is less than 3 characters long. Make sure you enter a software name
that has 3 to 15 characters.<br>
'''1015''' Software name is too long. Make sure your software name has 3 to 15 characters.<br>
'''1100''' Database access error.<br>
 
<u>General error codes, returned when calling the functions CmtGetDescriptionByCode:</u><br>
'''50000''' The data is not correct for its type.<br>
'''50001''' The field value has been truncated due to the field length in the database.<br>
'''50002''' The insert operation Failed because the REC ID already existed in the database.<br>
'''50003''' Failed to update Record since it is being updated by another user.<br>
'''50103''' Illegal REC ID.<br>
'''50104''' REC ID Creation failed.<br>
'''50105''' Illegal Sub-Contact REC ID.<br>
'''50106''' Illegal Contract REC ID.<br>
'''50107''' Illegal Employee REC ID.<br>
'''50108''' Illegal Ticket REC ID.<br>
'''50109''' Illegal Account REC ID.<br>
'''50110''' Illegal data for that Contract.<br>
'''50111''' This Employee is not active.<br>
'''50112''' Illegal Document REC ID.<br>
'''50113''' Illegal linked object REC ID.<br>
'''50114''' Employee not found.<br>
'''50115''' Some mandatory fields have no values.<br>
'''51000''' Illegal kind of Account entity.<br>
'''51001''' Account Manager not found.<br>
'''51002''' The REC ID of the Account Manager is illegal.<br>
'''51003''' Illegal tax code.<br>
'''51004''' This code does not exist in Commit.<br>
'''52000''' Illegal kind of event.<br>
'''52001''' Illegal start time.<br>
'''52002''' Illegal end time.<br>
'''52003''' Illegal event date.<br>
'''52004''' The field Reminder1 has Illegal Value.<br>
'''52005''' The amount in the field has an illegal value.<br>
'''52006''' The Field Remider1:Units has Illegal Value.<br>
'''52007''' The Field Remider2:Active has Illegal Value.<br>
'''52008''' The Field Remider2:Amount has Illegal Value.<br>
'''52009''' The Field Remider2:Units has Illegal Value.<br>
'''52010''' Illegal employee REC ID.<br>
'''52011''' Error occurred while updating the Task/Appointment employee field.<br>
'''54000''' Illegal Ticket open date.<br>
'''54001''' Illegal Ticket close date.<br>
'''54002''' Illegal Ticket code area.<br>
'''54004''' Illegal Ticket priority.<br>
'''54005''' Illegal Ticket status.<br>
'''54006''' The Ticket Account was not found in the database.<br>
'''54007''' The Ticket Account Manager was not ound in the database.<br>
'''54008''' This code does not exist in Commit.<br>
'''54009''' This code does not exist in Commit.<br>
'''54010''' This code does not exist in Commit.<br>
'''54011''' This code does not exist in Commit.<br>
'''54012''' This code does not exist in Commit.<br>
'''55000''' Illegal charge date.<br>
'''55001''' Illegal charge REC ID.<br>
'''55002''' Illegal start date.<br>
'''55003''' Illegal start time.<br>
'''55004''' Illegal amount entered for hours.<br>
'''55005''' Illegal quantity.<br>
'''55006''' Illegal price.<br>
'''55007''' Illegal total.<br>
'''55008''' Illegal value in the Adjust Amount field.<br>
'''55009''' Illegal value in the Adjust Percent.<br>
'''55010''' The Discount/Markup field has an illegal value.<br>
'''55011''' Illegal value in the Adjust Kind field.<br>
'''55012''' Illegal bill total.<br>
'''55013''' You can not create a charge for a suspended item.<br>
'''55014''' Item was not found in Commit.<br>
'''55015''' This code does not exist in Commit.<br>
'''55016''' This code does not exists in Commit.<br>
'''55017''' This Code does not exist in Commit.<br>
'''55018''' This Code does not exist in Commit.<br>
'''55019''' This Code does not exist in Commit.<br>
'''55020''' This Code does not exist in Commit.<br>
'''55021''' This Code does not exist in Commit.<br>
'''56000''' Illegal item code.<br>
'''56001''' The field that indicates the item group type has an illegal value.<br>
'''56002''' The field that indicates if the Item is suspended has an illegal value.<br>
'''56003''' Illegal value of The field that indicate if the item is suspended.<br>
'''56004''' Mismatch found between the fields price and price source.<br>
'''56005''' Illegal cost.<br>
'''56006''' Mismatch found between the fields cost and item group type.<br>
'''56007''' The field that indicates if the charge is by unit or by hours has an illegal value.<br>
'''56008''' Illegal value in the Description.<br>
'''56009''' The field that indicates the item type has an illegal value.<br>
'''57000''' This Code does not exist in Commit.<br>
'''58000''' Illegal date time.<br>
'''58001''' The Description field was not found.<br>
'''58002''' The field kind was not found.<br>
'''58003''' The Account member was not found.<br>
'''59000''' This code does not exists in Commit.<br>
'''59001''' This Code does not exist in Commit.<br>
'''59002''' This Code does not exist in Commit.<br>
'''59003''' This Code does not exist in Commit.<br>
'''59004''' This Code does not exist in Commit.<br>
'''59005''' This Code does not exist in Commit.<br>
'''60000''' Invalid web user record ID number.<br>
'''60001''' This customer web user is not active.<br>
'''60002''' This user is not a customer.<br>
 
==See Also==
*[[Email Connector|Commit Email Connector]]
*[[API by Email and MSP Integration]]
*[[API by Email and MSP Integration]]
*[[MSP Integration Setup]]
*[[MSP Integration Setup]]
*[[Commit SQL Database]]
*[[API Code Samples|Low-Level API Code Samples]]
*[[API Reference Manual]]
*[http://{{SERVERNAME}}/products/sql-database/ RangerMSP SQL Database (CSD)]
*[[SQL Database Installation Guide | RangerMSP SQL Database (CSD) Installation Guide]]
 


[[Category:User Manuals]]
[[Category:User Manuals]]
[[Category:Integration]]
[[Category:Integration]]

Latest revision as of 07:13, 8 July 2020

User Manuals > API Developers Guide

Introduction

RangerMSP provides various tools in order to read/add/update information in the RangerMSP database.

These tools include:

  • Programming API (recommended)
    The RangerMSP Programming API provides developers with a set of API functions which can be used in CSharp, VB.NET and C++. The Programming API libraries provide easy-to-use classes and objects which make the development very simple and friendly.
  • Low-level Programming API
    Provides low-level functions for programmers using other languages, such as VB, Delphi or any other programming language that lets you use a standard Windows dll file. The Programming API includes two sets of functions: Data-Retrieval API and Data-Update API.
  • API by Email
    The API by Email allows you to send XML formatted emails which contain database transactions. RangerMSP Email Connector then pulls the incoming XML emails from your POP3 mail server, processes the email and performs the transactions in the XML transaction. XML formatted email gives you access to the Data-Update API, which allows you to perform many actions such as linking to external systems, receiving forms submitted from your web site, and more.
  • Web API
    The Web API allows you to interact with your RangerMSP server and data over the Web using HTTP.
  • ODBC Link
    In addition to the Data Retrieval API, there is an option of using ODBC to read data directly from the database. RangerMSP uses an open database structure and allows other applications to access the database using ODBC (Open Data Base Connectivity) for read-only purposes. The ODBC link should not be used from programs you develop (you should use the data retrieval API for this purpose). You can use ODBC Link in order to read data from the database and integrate it with an external system (i.e. Crystal reports, or any other application).


Glossary

  • RangerMSP API (Application Programming Interface) - RangerMSP provides an API which allows you to add and update records in the RangerMSP database. The API includes a list of possible actions and parameters.
  • ODBC Link (Open Data Base Connectivity) - ODBC is a function library which provides a common API for ODBC compliant databases. RangerMSP provides an open database and allows other applications to access the database using ODBC for read-only purposes.
  • Record - Each entity in the RangerMSP database (such as Ticket, Account, Asset, Item, Appointment, Task, etc.) is considered a "record".
  • Database fields - Each record contains a list of fields, each of which holds the record's data.
  • Transaction – All additions or updates to record in the database are done by using a transaction. Each transaction includes the operation you wish to perform, the data type you wish to add/update and the additional parameters (database fields and their values).
  • Transaction Parameters - Each transaction contains the parameters for performing the transaction: record type, list of database fields and a list of the values to be updated in these fields.
  • External Application - This refers to the external program which integrates with RangerMSP in order to update the database. This name should be passed when performing updates to the database, and it will be saved in the RangerMSP record to indicate who performed the changes.
  • Record ID (REC ID) - Each record in RangerMSP has a unique Record ID which is created when adding the record to the database. Every ID is 20 characters and should be transferred with the API transaction when you need to update an existing record.


Using API

Workflow

Following is a sample work-flow, which demonstrates the process of adding a new Account, and then adding a new Ticket to this Account, using the RangerMSP API.

Note that the API can return two parameters to the External Application:

  1. The RangerMSP REC ID - when adding new records to the database, this will contains the new record ID.
  2. The ExternalTransactionID (relevant for XML transaction only) - In case the external application passes a parameter to be returned with the response, the ExternalTransactionID will be returned as-is to in the response.

The External Application should keep the REC ID which is returned from the API response. This allows you to later update the existing records with new data or add records related to it (such as opening a Ticket under the Account).


Updating existing records

In order to update an already existing record in the database (e.g. add a Ticket to an Account, update an Account's phone number, add a new Charge to an existing Ticket, etc.), you should pass the record's unique identifier to the API so it will update the existing record rather than create a new Account. The record's unique identifier is referred to as the Record ID (REC ID).

The Record ID can be obtained in the following ways:

  1. API Response (as in the flow above) - You can extract the newly created Record ID from the Email Response when adding new records with the API. This requires the developer to process the API responses, and extract the returning REC ID for each newly added record.
  2. Data Retrieval API - Use the Data Retrieval API functions to find relevant records (Accounts, Tickets, etc.), and read all information from the database, including the unique Record ID.
  3. Manually - from the Account's Notes tab, at the bottom, right-click the REC ID field and copy it.

Once you have obtained the Record ID you can pass the Record ID as a parameter for the API and update this record.


Programming API

The Programming API allows you access the RangerMSP database and perform transactions from within a program (using various programming language). This means you can embed code which accesses the RangerMSP database from within your own application, and add your own functionality which updates the database.

The RangerMSP Programming API provides developers with a set of API functions which can be used in CSharp, VB.NET and C++. The Programming API libraries provide easy-to-use classes and objects which make the development very simple and friendly.

See more details and samples about each programming environments in the following links:



Low Level Programming API

The Low-level programming API provides a way to use the API from development languages which are not supported by the main Programming API.

The Low-level programming API executes database transactions. The low-evel API provides two separate dll programs, one for adding/updating data from the database, and one for retrieving data from the database.


For the full list of API functions go to API Functions.
For samples go to API Code Samples.

Note: Retrieving data can be performed either by the API (recommended) or using ODBC when needed. You can read more about it in the Data Retrieval section.

Adding and Updating Data

RangerMSP API allows you to add and update records in the RangerMSP database, such as Accounts, Tickets, Assets, Items, Appointments, Tasks and more.

The updates are performed using transactions, where each transaction includes the operation you wish to perform, the data type you wish to add/update, and any additional parameters (i.e. record type, database fields and their values).

Every record added to the system is assigned a unique Record ID (REC ID) which is the database identifier for this record.

The RangerMSP API allows you to perform the following operations.

  • Add new records - if no Record ID is passed in the transaction, the API assumes that this is a new record, adds it to the system and creates a new Record ID for it.
  • Update existing records - if the record ID is passed in the transaction, and the record exists, the system will update the record with the information in the transaction.
  • Retrieve records - The Data Retrieval API allows you to perform an SQL Query to get a list of record IDs and retrieve the details for a single record according to a REC ID.

Note that in order to retrieve data using ODBC (e.g. when linking to Crystal Reports), use the ODBC Link, which provides a read-only link for the RangerMSP database. See more details in Retrieving Data.

Data Retrieval

RangerMSP uses an open database and the RangerMSP API provides the ability to retrieve data using standard API functions which let you define queries and retrieve data.

In addition to the Data Retrieval API, there is an option of using ODBC to read data directly from the database. The ODBC link should not be used from programs you develop (you should use the data retrieval API for this purpose). Use the ODBC link only when you need to access the database from an external program, such as external report application (i.e. Crystal reports, or any other application).


API by Email (XML transaction)

The API by Email operates under the RangerMSP Email Connector module, which automatically processes incoming emails arriving at a defined public email address. The Email may contain XML formatted messages which contain API transactions, and provides a full data update API to RangerMSP.

The Email Connector pulls incoming emails from your POP3 mail server, and processes the email. When an email containing XML formatted message is detected, the system analyzes the XML content of the email and performs the transactions written in the XML. You may set the Email Connector to send automatic replies in response to XML formatted email.

The API by Email supported only the Data Update API (Data Retrieval API is not supported via emails). The API by Email executes database the transactions using the functions provided by the API dll file which is located in the RangerMSP installation. Both the Programming API and the API by Email use the same dll for performing the transactions.

Note that the API by Mail is supported only for the Data Update API, allowing you to add and update data. In order to retrieve data, you should use the Data Retrieval Programming API (recommended) or use ODBC, both methods do not support API by Email. You can read more about it in the Data Retrieval section.

  • Learn more about using API by Email.
  • Learn more about building the XML transactions for the API by Email in XML samples.


Web API

The Web API allows you to build applications or addons which interact with your RangerMSP server remotely over the Web. You get access to all the API functions and can query the data or add/edit data (or both) giving you unparallelled control over your data. To use the Web API you need to have the RangerMSP Server service, which is also used by the Email Connector and the Alerts Server modules, installed and running and be using the Programming API.

You can find details on connecting remotely using various programming environments here:


For instructions on how to activate the Web API, go to Web API Server Configuration

Data Retrieval API

The Data Retrieval API provides API functions which help you execute database queries and receive the results. Each function uses API functions provided by the Retrieval API dll file which is located in the RangerMSP installation. The Data Retrieval API is available only via the Programming API; no API by Email is available for data retrieval.

The Data Retrieval API provides the following abilities:

  • Execute a database query and receive a result records list.
  • Read each record with its fields.
  • Find out field properties.

See low-level programming API information in Low Level API Data Retrieval.
See the Data Retrieval API Reference Manual for detailed usage description.

ODBC Data Retrieval

RangerMSP uses an open database and allows other applications to access it using ODBC (Open Data Base Connectivity) for read-only purposes. While the API provides the means for adding and updating information in the database, it is preferred to use ODBC to read information from the database.

You can use ODBC Link to read data from the database and integrate it with an external system (i.e. Crystal reports, or any other application). You may also use the ODBC Link in order to read the Database Record ID and update existing records (see Updating existing records).

Activation Notes:

  • The ODBC drivers are well tested and work well, however, please note that the RangerMSP Support team doesn't provide "pure ODBC" support.
  • NEVER use ODBC to modify or delete data; use it for READ purposes only. Modifying data should be done using the RangerMSP API.
  • The ODBC Link can be used with your installed version of RangerMSP, and only requires installing an external driver. Before working with the API we recommend that you backup the database.


Below are the database table names and their meaning:

RangerMSP Record Database Table Name
Accounts Cards
Tickets Tickets
Charges Slips
Assets Assets
Appointments Events
Tasks Events
History Notes NoteBook
Opportunities Opps
Documents Docs
Knowledge Base KBArticles

For the database fields list, please refer to API Reference Manual section. You can find detailed instructions for using the ODBC Link in the Installing ODBC Driver section.


Installing ODBC Driver

Product Overview
The Advantage ODBC Driver is an ODBC version 3 driver based on the Advantage Client Engine that provides SQL access to the Advantage Database Server. The driver provides full support for the "Minimum" ODBC SQL grammar specification, as well as many functions included in the "Core" and "Extended" grammar specifications. When used with the Advantage Database Server, ODBC users can have the application stability, performance and reduced network traffic benefits of client/server architecture.

Installation on Windows
Like other ODBC drivers, the Advantage ODBC Driver is installed and managed using the ODBC Administrator Utility. This utility works with the ODBC Driver Manager to configure ODBC data sources. At runtime, the ODBC Driver Manager works with available drivers and their configured data sources. If you have previously installed ODBC drivers, the ODBC Administrator may already be installed on your workstation. The icon for the Administrator is usually found in the Control Panel.

To install the Advantage ODBC Driver:

  1. Download the ODBC driver version that corresponds with your Advantage SQL Database Server version from the following links: (The Advantage Version number can be found in the Advantage Configuration Utility located on the RangerMSP Server)
    ODBC Driver Version 11.10 – 64 bit
    ODBC Driver Version 11.10 – 32 bit
    ODBC Driver Version 10.10 – 32 bit
    ODBC Driver Version 10.0 – 32 bit
    ODBC Driver Version 9.0 – 32 bit
    ODBC Driver Version 8.1 – 32 bit (**Also for systems that do not use the RangerMSP SQL Database)
  2. Run the Setup program.
  3. Proceed through the setup windows to complete installation.

**DISCLAIMER: Using the ODBC connector without the RangerMSP SQL Database is not recommended, since the chances for Database Corruption would be elevated.

Data Source Setup for Windows
Once the Advantage ODBC Driver is installed, a data source needs to be configured to use the Advantage ODBC Driver. The data source is an entry in the Windows Registry. When a data source is defined for the Advantage Driver, all information specific to the Advantage Driver and database files is stored under the Data Source entry in the Windows 95/98/ME/ NT/2000/2003/XP Registry.
The database files and indexes must be stored on your file server, and the Advantage Database Server must be loaded in order to access the files.

The Data Source settings may be modified at any time. Using the ODBC Administrator, you may modify the Data Source and Option settings. For specific information about the screen fields see the Data Source Setup Screen.

To Setup the Data Source:

  1. From the ODBC Administrator, click Add.
  2. Highlight the Advantage SQL ODBC line, and click OK.
  3. Type a unique data source name. For example, type RangerMSPData. This name is used by applications to reference the data source.
  4. Specify the path to the database - point to folder: \RangerMSP\Db (do not use the data dictionary option). Click Browse to select a database path. Note Multiple Advantage data sources may need to be defined for your environment. If different settings are needed for ODBC connections in one application, separate data sources may be required.
  5. When using RangerMSP SQL Database select the Remote Server option and unselect the Local and Internet ones.
  6. Review the options and change them to your desired setup.
  7. Once the Options are reviewed and/or altered, click OK to exit and save the settings. The new data source is displayed.
  8. Click Close to exit the ODBC Administrator.

ODBC Data Source Entries for Windows
In Microsoft Windows, the entries are registry settings found on HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ (your unique data source name) or HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI (your unique data source name). Unless specified otherwise, all registry entries can be setup by the Advantage ODBC Driver setup utility. See Data Source Setup for Windows and Data Source Setup Screen for more information. ODBC Data Source Keys.

ODBC Data Source Keys
The following ODBC registry is required for the driver to load:

Registry Entry Comments
DataDirectory=data path 'data path' should be a valid path name for files locations (e.g., x:\data). This path is used to automatically select all tables in the specified directory.
DefaultType=Advantage Sets a certain type of database files to use Advantageproprietary ADT/ADI/ADM files.
ServerTypes=3 Allows the Driver to use the remote or local server

The following ODBC registry keys are optional:

Registry Entry Comments
AdvantageLocking=ON \ OFF The default is ON to use the Advantage proprietary locking.
CharSet=OEM \ ANSI The default character collation setting is ANSI. If OEM is specified, Language must be indicated as well.
Language=USA Used if CharSet=OEM.
Description=String This is provided for easier administration.
Locking=RECORD \ FILE Indicates whether updates lock the entire file or the individual records that are updated. The default is RECORD.
MaxTableCloseCache=n N is the number of tables to hold in cache when cursors are opened and closed. The default is 25.
MemoBlockSize=n N is the size of the Advantage memo blocks in tables that are created by the ODBC driver. The default value is 8 for Advantage proprietary table (ADT/ADM).
Rows=TRUE \ FALSE Select whether deleted rows are displayed. If True, deleted rows are displayed. The default is False.
TrimTrailingSpaces=TRUE \ FALSE The default is False. If True is specified, trailing spaces in character fields will be removed prior to returning the values to the application.

Troubleshooting

In case when using applications you developed with ODBC you receive one of the following errors: 

Error 6420:  The 'discovery' process for the Advantage Database Server failed. Unable to connect to the Advantage Database Server.  axServerConnect

or 

Error 5033:  No connected server was found for the given drive letter.

You should perform the following:

1. Configure the ADS.ini file

2. Copy the ADS.ini file you prepared from the RangerMSP server folder into the following folder on each the affected workstation:

  • %Windir%\system32

This folder usually translates to: C:\Windows\system32

Note: To open these folders on your PC you can paste the paths listed above into a Windows Run dialog box, or into any Windows Explorer path.

3. Change the database path configured for ODBC connection to include the server IP address and port used by Advantage Database Server, for example: 

\\192.168.0.1:6262\RangerMSP\Db

Troubleshooting ODBC in 64 Bit Operating Systems

The RangerMSP ODBC drivers are mainly distributed for 32-bit operating systems; however, the same drivers are supported on the 64-bit operating systems (I.e. Windows 7 x64), and can be used to retrieve data from the RangerMSP database.


Configuring Data Source in 64-Bit Systems

When installing the ODBC drivers on 64-bit operating systems, the ODBC drivers may not be displayed in the default ODBC manager in windows control panel. In order to view the 32-bit ODBC manager in a 64-bit operating system, you’ll need to browse to %windir%\SysWOW64\odbcad32.exe and run the 32 bit ODBC Administrator manually. Once the data source has been configured there, you should be able to select the data source in your 3rd party ODBC programs.


Samples

For basic samples that provide an easy starting point see the following:


For Low-Level API and XML samples see:

API Reference Manual

Find a detailed listing of the database fields in the API Reference Manual.

See Also

Retrieved from "https://www.rangermsp.com/w/index.php?title=API_Developers_Guide&oldid=8369"