Dynamic SQL field mapper

This feature enables data from an external table to be populated in an Issue into one or more fields. The lookup is performed automatically when lookup key field is populated. The lookup key field may be something like "User ID", "Asset Name", etc.

One or more lookup key fields can be designated within a Workspace. The lookup key field can be either an Issue Information or Address Book field. Associated Issue Information or Address Book fields can then be designated to be populated with data from the external database. Allowed field types for lookup are character (single line), integer, mail, and drop-down.

Important

If a customer process has an Access database open, BMC FootPrints Service Core may not be able to read that Access database until the customer process closes.  If you encounter this situation, check the permissions for the folder in which the database (.mdb) file is located and make sure that the folder is enabled for read and write permissions for everyone.  When the folder is enabled with read and write permissions for everyone, the database should be available to BMC FootPrints Service Core and the customer process at the same time.

Supported Databases

  • Windows FootPrints versions—Can connect to MS SQL Server, Oracle, MySQL, Sybase, Postgres, Access, and DB2 for Windows.
  • UNIX/Linux Versions—Can connect to Oracle, MySQL, DB2 or Postgres.  If the external database is of a different type than the BMC FootPrints Service Core database, a DBD driver must be built.

Note

This feature is part of the Dynamic SQL Database Link add-on module and must be licensed. Please contact your salesperson for more information on obtaining a license to enable this feature.

Topics in this section:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*