×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Note

   

This documentation supports the 20.22.01 version of BMC Helix Remedyforce.

To view an earlier version, select the version from the Product version menu.

BMC Helix Remedyforce 20.22.01 ... Integrating Integrating BMC Helix Remedyforce with BMC Client Management

Importing data from BMC Client Management by using the REST Web API

You can import data from BMC Client Management (known before version 12.0 as BMC FootPrints Asset Core) into BMC Remedyforce CMDB 2.0 by using the Pentaho Data Integration tool. The Pentaho packages for importing data from BMC Client Management are available on the BMC Communities website. For information about how configuration items (CIs) are imported and relationships are created in BMC Remedyforce CMDB 2.0, see Overview of how data is imported into BMC Remedyforce.

The following topics provide information about the Pentaho package for importing data by using the Representational State Transfer (REST) web API. For information about the REST web API, see the BMC Client Management Help.

For information about importing data by accessing the BMC Client Management database, see Importing data from BMC Client Management by accessing the database.

Note

The Pentaho package for importing data by using the REST web API supports BMC Client Management and BMC Client Management On-demand versions 12.0 and later. If you integrate Remedyforce with BMC Client Management On-demand 12.0 or later, you must import data by using the FootPrints Asset Core WebServices Integration Package CMDB 2.0 only.

However, if you integrate by using Remedyforce agentless discovery and/or own the Premium and Premium Plus license, you are provided with a new inbuilt integration method that does not use Pentaho packages. Note that when you use any one of the two integration methods, the other method will be disabled.  

For more information about the integration methods and BMC Client Management versions that BMC Helix Remedyforce supports, see Remedyforce and Client Management - Original vs. Newer Integrations Open link and Supported browsers, mobile devices, and integrations.

Before you begin

Before you can import data from BMC Client Management by using the REST web API, you must perform the following tasks:

To import data from BMC Client Management

Important

The job (KJB) files in the Pentaho package send a REST web API request to the BMC Client Management server to initiate the export of data to a .csv file. Each job file contains the list of BMC Client Management fields that are available by default in the .csv file.

If you add, delete, or change the order of fields in the .csv file, you must update the Pentaho jobs and map the fields and the order in which they are listed to the .csv file. Otherwise, the data that you import might be corrupted or the import might not complete successfully. For more information, see Data that is imported from BMC Client Management is corrupted.

  1. To launch the Pentaho Data Integration tool, perform the following actions:

    1. Navigate to the location where you downloaded and unzipped the Pentaho Data Integration tool.

    2. Navigate to the data-integration folder and double-click the Spoon.bat file.

  2. In Pentaho Spoon, select File > Open, navigate to the folder where you downloaded the Pentaho package, and open the KJB (job) file for the CI type that you want to import.
    For example, to import computer system CIs, open the TransferAssetCoreCSinfotoCMDB.kjb file.
  3. From the Edit menu, select Settings.

  4. In the Job properties window, click the Parameters tab.

  5. Modify the Default value column for the different parameters.

    Parameter
    Action to be performed
    AC_DOWNLOADURL

    Perform the following actions:

    • Specify the BMC Client Management server name on which the .zip file that contains the data to be imported is stored.
    • Specify the BMC Client Management server port that is configured for downloading the .zip file that contains the data to be imported.

    You must enter the URL in the following format:
    https://    BCMServerName:Port

    In this URL, you must replace BCMServerName with the actual BMC Client Management server name and Port with the actual port from which the .zip file must be downloaded.

    AC_ENDPOINT
    		Perform the following actions:
    • Specify the BMC Client Management server name from which you are importing data.
    • Specify the BMC Client Management server port that is configured for the BMC Remedyforce external integration.

    You must enter the URL in the following format:
    https://    BCMServerName:Port/api/1

    In this URL, you must replace BCMServerName with the actual BMC Client Management server name to which the Pentaho job sends the REST request and port with the actual port that is configured for sending the REST request.

    Note: If you provide a secure URL, ensure that the SSL certificate that is installed on the port is certified by a Certificate Authority (CA).

    AC_USERNAME

    Specify the user name of the BMC Client Management administrator that you have configured for the BMC Remedyforce external integration.

    For more information, see Configuring the BMC Remedyforce external integration on the BMC Client Management server.

    AC_PASSWORD

    Specify the password of the BMC Client Management administrator that you have configured for the BMC Remedyforce external integration.

    For more information, see Configuring the BMC Remedyforce external integration on the BMC Client Management server.

    AC_LANGUAGE

    (Optional) Specify the language into which the internal BMC Client Management keywords must be translated for the import.

    The default value for this parameter is English. You can change the value to American, Francais, Deutsch, Japanese, Espanol or Brasileiro.

    AC_NUMBEROFTRY

    (Optional) Specify the number of times the job must check for the availability of the file that contains data to be imported from BMC Client Management.

    The default value for this parameter is 3.

    AC_WAIT

    (Optional) Specify the time interval (in seconds) after which the job must check for the availability of the file that contains data to be imported.

    The default value for this parameter is 10.

    SFDC_URL

    Confirm that the URL to access Salesforce is specified in this parameter.

    Best practice

    We recommend that you do not change the default API version in the Salesforce Webservice URL.
    SFDC_USER
    Specify the login ID of the Salesforce account that you will use to upload the imported data.
    SFDC_PASSWORD

    Specify the password of the Salesforce account that you will use to upload the imported data.

    Important: If you have enabled the setting to access your Salesforce organization from limited IP addresses, you must append the security token to your Salesforce organization password. For example, if the password for your Salesforce organization is mypassword and your security token is XXXXXXXXX, specify mypasswordXXXXXXXXX in the Password fields.

    The various transformations and steps in the job use the values that you specify on the Parameters tab. If you do not specify values for the SFDC_USER and SFDC_PASSWORD parameters, you must provide the user name and password of your Salesforce organization in the Salesforce Input[CMDB_Class] and Upsert Into Class <CI type name> steps.

    To access these steps, in the job (KJB) file, right-click the Import Records in Remedyforce CMDB step, and select Open Referenced Object> Transformation.

    Note

    If you are running a combined job, you can specify the parameter values only in the combined job (for example, TransferAssetCoreComputerSystemAndProductinfotoCMDB.kjb). Each job that is included in the combined job uses the parameter values that you specify in the combined job. However, if you specify parameter values in the combined and individual jobs, values specified in the individual jobs take precedence.

  6. (Optional) Update the mapping between the data from BMC Client Management and BMC Remedyforce CMDB (fields in the Base Element object).

    1. Double-click the Upsert Into Class <CI type name> step.
    2. (Optional) In the Salesforce Upsert window, enter the user name and password of your Salesforce organization.
      Based on your requirements, you can replace the Salesforce user name and password with the SFDC_USER and SFDC_PASSWORD parameters.
    3. In the Fields area, click Edit Mapping.
    4. In the Enter Mapping window, update mappings for fields based on your requirements.
      For information about updating the out-of-the-box mapping, see Field mapping in CMDB 2.0.
    5. To save your settings and close the Enter Mapping window, click OK.
    6. To save your changes and close the Salesforce Upsert window, click OK.
  7. To save the KTR and KJB files, click Save.
  8. In the KJB file tab, click Run this job.

  9. Perform one of the following actions based on the Pentaho version that you are using:

    Pentaho versionAction
    6.1In the Run Options window, click Run.
    6.0In the Execute a job window, click Launch.

    Data is imported into the appropriate CMDB class. The first time you run the job, all CIs are imported into the appropriate CMDB class. When you rerun the job, only the new and modified CIs are imported into the CMDB class.

    Transformation status is depicted by using the following icons:

    • — Complete
    •   — Running
    • — Unsuccessful
  10. (Optional) To view logs, in the Execution results section, click the Logging tab.
    All the errors are displayed in red.
    For the imported records, the Source field is set to BCM. You can use the Source field to generate reports and also when you enable and configure reconciliation. 

To schedule jobs to import data

On the BMC Communities website, the Pentaho packages for importing data from external data sources into BMC Remedyforce page contain a SchedulingFiles folder. This folder contains a sample batch file that you can use as a base to create your batch files for scheduling data import. For more information about scheduling a job, see http://wiki.Pentaho.com/display/EAI/Kitchen+User+Documentation.

Note

To understand the job scheduling process, refer to the following procedure. This procedure is an example to be used as a reference for all other packages.

To schedule the Remedyforce LDAP Pentaho package to import users, perform the following steps:

(For all other required packages, perform these steps by using the respective batch files.)

  1. Navigate to the Remedyforce Package folder.
  2. Rename your extracted package folder to SchedulingFiles.
  3. Open the folder where you have installed the Pentaho Data Integration tool and minimize this folder.
  4. Open the SchedulingFiles folder.
    The folder contains two .bat files.
  5. To create a copy of the batch file, copy SchedulingTransferLDAPInfo.bat file and paste it in the same folder.

  6. Right-click the SchedulingTransferLDAPInfo.bat file and click Edit.
    The SchedulingTransferLDAPInfo.bat notepad opens.

  7. Minimize the notepad and open the Pentaho data-integration folder as mentioned in Step 3.

  8. Copy the data-integration folder address and navigate to the notepad as mentioned in Step 6.

    The following figure shows an example of the updated SchedulingTransferLDAPInfo.bat file.

  9. Before the first line of the notepad, type cd and paste the copied data-integration folder address . (Make sure to add a space betweeen cd and the folder address).
  10. Paste the data-integration folder address in the Kettle Home folder address and remove the double quotes ("").
  11. Paste the data-integration folder address in the kitchen.bat file address by replacing only the part before \kitchen.bat.
  12. Navigate to the Remedyforce Package folder and copy the address for TransferLDAPInfo.kjb.
  13. Paste the TransferLDAPInfo.kjb address in between \kitchen.bat /file: and /level:Detailed. Remove the double quotes ("") and any additional spaces between the address.
  14. Save the notepad.

  1. Open the Command Prompt as an administrator.
  2. Type cd and then paste the SchedulingFiles folder address with a space in between the two. 
  3. Copy and paste the .bat file name (SchedulingTransferLDAPInfo.bat).
    The job starts running.
  1. Go to Start > Control Panel > Administrative Tools > Task Scheduler.
  2. In the Actions section, click Create Task.
  3. In the General tab, enter the name and description.
  4. Select the Run with highest privileges check box, and click OK.
  5. On the Triggers tab, click New, select the appropriate option for starting the task, and click OK.
    For example, you can select Daily or When the computer starts as the option for starting the task.
  6. On the Actions tab, click New.
  7. Click Browse, select SchedulingTransferLDAPInfo.bat, and click OK.

KJB files for importing data from BMC Client Management


The Pentaho package contains job (KJB) and transformation (KTR) files that are created in the Pentaho Data Integration tool. The KJB files (jobs) and KTR files (transformations) store metadata in XML format. A KJB file contains a series of transformations that are run in a sequence. A KTR file contains a single transformation. The KJB (job) files retrieve data from external sources into BMC Remedyforce CMDB.

For more information, see KJB files in the Pentaho package and Steps in the KJB files for importing data from BMC Client Management.

KJB files in the Pentaho package

Each Pentaho package includes different KJB (job) files for importing different types of configuration items (CIs), such as computer systems and LAN endpoints. These job files are bundled with related files and provided to you in folders. The folder names correspond to CI types in BMC Remedyforce CMDB.

The following table provides information about the job files that you must run to import specific CI types into BMC Remedyforce CMDB:

Folder name

Job file

Description

Computer System

TransferAssetCoreCSinfotoCMDB.kjb

Transfers information about the
BMC_ComputerSystem CI type

LANEndPoints

TransferAssetCoreLANEndPointInfoto
CMDB.kjb

Transfers information about the
BMC_LANEndpoint CI type

OS

TransferAssetCoreOSinfotoCMDB.kjb

Transfers information about the
BMC_OperatingSystem CI type

Processor

TransferAssetCoreProcessorInfoto
CMDB.kjb

Transfers information about the
BMC_Processor CI type

Product

TransferAssetCoreProductInfotoCMDB.kjb

Transfers information about the
BMC_Product CI type.

Note: Depending on the organization size,
running the Product job transfers large amounts
of data to the Salesforce organization, which
might lead to exceeding the organization storage limit.

Combined Jobs

  • TransferAdvancedAssetCoreinfo
    toCMDB.kjb
  • TransferAssetCoreComputerSystemAnd
    ProductinfotoCMDB.kjb

The Combined Jobs folder contains the following job files:

  • TransferAdvancedAssetCoreinfo
    toCMDB.kjb
    The job file transfers information related to the following CI types:
    • BMC_ComputerSystem
    • BMC_OperatingSystem
    • BMC_Processor
    • BMC_LANEndpoint
  • TransferAssetCoreComputer
    SystemAnd    ProductinfotoCMDB.kjb
    This job file transfers information related to the following CI types:
    • BMC_ComputerSystem
    • BMC_Product CI

Steps in the KJB files for importing data from BMC Client Management

All job (KJB) files for importing data from specific CI types include the series of steps and transformations that are listed in the following table.

Step
Description
Start
Starts the job to import data from BMC Client Management by using the REST web API.
Check If Delta Timestamp File exists

Checks for a time stamp file.

The Pentaho package utilizes a time stamp file to determine which records have been added or modified since the last time the job was run.

This step is used for incremental import. If a time stamp file does not exist, the Create the initial timestamp file step is run. Otherwise, the Send Request for Export step is run.

Create the initial timestamp file

Creates the time stamp file to record the time of import.

This step is run only if you are importing for the first time or have deleted the existing time stamp file.

Send Request For Export

Sends a REST web API request to the BMC Client Management server to initiate the export of data to a .zip file.

The response from the BMC Client Management server provides either the location and name of the .zip file or an error code.

Check Request REST Response

Checks whether the request for export was successful.

If the request for export was successful, the Download File step is run. Otherwise, the Log Request Error from AC step is run.

Log Request Error From AC
Logs an error if the response from the BMC Client Management server includes an error code.
Download File

Downloads the .zip file that is stored on the BMC Client Management server. This file contains the data to be imported in BMC Remedyforce and is downloaded to the folder where you have saved the KJB files.

If the .zip file is not available, this step is run again after the specified time interval, which is 10 seconds by default. The default number of times this step is rerun is 3. You can change the default values based on your requirements.

Is File Downloaded
Checks whether the .zip file is downloaded to the computer on which the Pentaho package is running.
Write File Not Available
Creates an error message file if the .zip file is not available for download even after the final run of the Download File step.
Check Download REST Response

Checks for an error in downloading the file from the BMC Client Management server.

If the file is successfully downloaded, the Import Records in Remedyforce CMDB step is run. Otherwise, the Log Download Error From AC step is run.

Log Download Error From AC
Logs an error if the file is not downloaded successfully from the BMC Client Management server.
Import Records In Remedyforce CMDB
Extracts records from the .zip file and imports data in BMC Remedyforce CMDB based on the specified mapping.
Delete File From Server
Sends a request to the BMC Client Management server to delete the .zip file.
Check Delete REST Response

Checks whether the file has been deleted successfully from the BMC Client Management server.

If the file is not deleted successfully, the Log Download Error From AC step is run.

Log Download Error From AC
Logs an error if the file is not deleted successfully from the BMC Client Management server.
Store the current time stamp
If the data is successfully imported, stores the time at which the data was imported to BMC Remedyforce.

Troubleshooting

The following topics provide troubleshooting tips to resolve issues that might occur when you import data from BMC Client Management:

Mappings cannot be updated from the Salesforce Upsert window

In the Salesforce Upsert window, the drop-down fields listed in the Module field column in the Fields area might not display any values. In this case, you must update the mapping between the data from BMC Client Management and BMC Remedyforce CMDB by using the Edit Mapping option.

Data that is imported from BMC Client Management is corrupted

The job (KJB) files in the Pentaho package send a REST web API request to the BMC Client Management server to initiate the export of data to a .csv file. Each job file contains the list of BMC Client Management fields that are available by default in the .csv file.

If the data imported from BMC Client Management is corrupted or the import does not complete successfully, the .csv file that contains the data exported by BMC Client Management might have been modified. You might have added, deleted, or changed the order of fields in the .csv file. To resolve this issue, you must update the Pentaho jobs and map the fields and the order in which they are listed to the .csv file.

Perform the following actions to fix the corrupted data that is imported from BMC Client Management:

  1. Navigate to the location where you downloaded and unzipped the Pentaho Data Integration tool.
  2. To launch the Pentaho Data Integration tool, navigate to the data-integration folder.
  3. Double-click the Spoon.bat file and open the job (KJB) file that corresponds to the .csv file that you have updated.
    For example, if you have updated fields in the .csv file for computer system CIs, open the TransferAssetCoreCSinfotoCMDB.kjb file.
  4. In the job (KJB) file, right-click the Import Records in Remedyforce CMDB step, and select Open Referenced Object > Transformation.
  5. In the transformation (KTR) file that is opened, double-click the CSV file input step.
  6. In the CSV Input window, map the fields and the order in which they are listed to the .csv file that contains data from the BMC Client Management server.
  7. You can right-click a field and select an option such as Move up and Insert before this row.
  8. To save your changes, click OK.
  9. To save the KTR and KJB files, click .

Troubleshooting common issues when importing data

The following table describes the troubleshooting tips that you can use to resolve common issues that you might face when importing data.

 Error or issueApplies to the Pentaho package forDescription or procedure
Viewing logs of the import jobsAll

Log files are created in the folder where you have saved the KJB files. Success and failure rows files are also created in the same folder.

If a failure occurs, the error code and its description are provided in the failure row file. You can also use the failure row file to import data to Salesforce.

Not all records are importedAllDelete the delta time stamp file of the job that you ran, and run the job again.
Import failsAllIf you have upgraded to BMC Remedyforce Winter 17 (20.17.01), either you use the latest Pentaho packages updated on the BMC Communities or map a value to the Source field of the Base Element object. Also, ensure that you have Edit permission on the Source field of the Base Element object.
An "out of memory" error occursAll

While importing a large number of records, if you get the OutofMemoryError or Java heap size error message, increase the heap size in the Spoon.bat file.

  1. Navigate to the location where you downloaded and unzipped the Pentaho Data Integration tool.
  2. Navigate to the data-integration folder.
  3. Right-click the Spoon.bat file, and select Edit.
  4. Locate the following line and replace 512 with a higher value:
    If "%PENTAHO_DI_JAVA_OPTIONS%"==""
    set PENTAHO_DI_JAVA_OPTIONS=
    "-Xmx512m" "-XX:MaxPermSize=256m"
  5. Click Save.
  6. Relaunch the Spoon.bat file and rerun the job file.
A "too many script statements" error occursAllWhen you run an import, if you receive "Too many script statements" as an onscreen Apex error message or in an email, reduce the batch size by 10 in the Batch Size field in the Settings section on the Salesforce Upsert window.
Records are not being to your CMDB.AllRaise a case with Salesforce to create a custom index on the Assembly ID field of the Base Element object.
Importing users by using the failure rows file for LDAPLDAP server

A failure row file is a text file that is saved in the folder where you have saved your KJB files. Perform the necessary steps to remove the error provided for the failure rows in the failure rows file, and then import the data by using the following steps.

The following Pentaho package provides a transformation file in the FailureRowsInput folder. You can use this transformation file for importing users from the failure rows file to the Salesforce organization:

LDAP integration with BMC Remedyforce (assign permission sets and Remedyforce managed package license): https://community.bmc.com/s/news/aA33n000000TPBRCA4/importing-users-from-an-ldap-server

To import data from the failure rows file

  1. Double-click and open the FailureRowsInput folder.
  2. Double-click and open the LDAP_FAILURE_ROWS_
    <YYYYMMDDHHMMSS>     file.
    Where YYYYMMDDHHMMSS is the time stamp of the file.
    The first line in the file displays the header row and from the second line onward details of the failed import are displayed. 
  3. For each failed import record:
    1. Read the information under the headings Error Description, Error Fields, and Error Codes.
    2. Resolve the error.
  4. Open the FailureLDAP transformation file with the Spoon batch file of the Pentaho Data Integration tool.
  5. Double-click the Salesforce Upsert step, and enter your Salesforce organization username and password in the Connection section.
  6. (Optional) To verify the connection, click Test connection.
  7. Click OK.
  8. To save the FailureLDAP transformation file, click .
  9. Click .
  10. In the Execute a transformation window, click Launch.
Failed in writeToSalesForce: java.lang.IllegalArgumentException: The char '0x0' after 'Print' is not a valid XML characterAllSome unicode characters that cannot be parsed by the XML parser are present in any of the mapped fields. Either delete these characters in data or delete the mapping of such fields.
Unable to query SalesforceAllCheck your Salesforce organization credentials in the Salesforce Upsert and Salesforce Input(CMDB_Classes) steps.
The job does not appear in Atrium Integrator.BMC Atrium CMDBEnsure that you have saved your KTR and KJB files in a folder in Atrium Integrator.
Error setting value #2 [ARDelta_1 Integer] on prepared statement (Integer)BMC Atrium CMDBThis error is generated if multiple records are created in the BMC Remedy AR System NGIE:Delta form for the running transformation. Delete the additional ARDelta entries that are created for the error transformation file by deleting the records. To find the duplicate records for a transformation file, open the NGIE:Delta form in BMC Remedy AR System. In the TransName field, enter the transformation file name, and click Search.
Did not find Remedy Application Service password for server<server name> in UDM:RAppPassword Form on server <server name>BMC Atrium CMDBCheck your Atrium Server Connection credentials in the ARInput step.
'Oracle Database Server 10g Release 2' is not valid for the type xsd: <data type >BMC Atrium CMDBCheck the data type of the mapped fields in the Salesforce Upsert step.
Duplicate LAN Endpoint entries are created in BMC Remedyforce CMDB.BMC Client Management

In BMC Remedyforce Summer 15 Patch 1 and earlier versions, when you imported LAN Endpoint data from BMC Client Management, duplicate LAN endpoint entries might have been created in BMC Remedyforce CMDB. This duplicate data was created because of the following factors:

  • In BMC Client Management, a LAN endpoint could periodically obtain multiple IP addresses using DHCP.
  • In BMC Remedyforce Summer 15 and earlier, the Network Interface IP address was used as the unique source identifier for LAN endpoints imported from BMC Client Management.

In BMC Remedyforce Summer 15 Patch 1 and later versions, instead of the Network Interface IP address, the MAC address is used as the unique source identifier for the LAN endpoints imported from BMC Client Management, and new duplicate LAN endpoint entries are not created in BMC Remedyforce CMDB.

To resolve this issue, you must install the latest Pentaho package for BMC Client Management released with BMC Remedyforce Summer 15 Patch 1 or later. Also, you must manually delete any existing duplicate LAN endpoint entry on the Remedyforce CMDB. For more information, see Deleting configuration items.

The HTTP Status 404 error is displayed when trying to connect to Salesforce.All

Ensure that your Pentaho transformations connect to https://login.salesforce.com/services/Soap/u/<API version> instead of https://www.salesforce.com/services/Soap/u/<API version>.

Starting from January 1, 2016, Salesforce retired www.salesforce.com as an API endpoint. For more information, see the announcement on BMC Communities website. To view a video demonstration of how to update your Pentaho transformations, see Salesforce API Endpoint Retirement.

BMC Remedyforce has updated the API endpoint in the Pentaho packages that are currently available on the BMC Communities website.

Error connecting to your Salesforce organization when using version 5.4 of the Pentaho Data Integration Tool.All

Check whether the Require TLS 1.1 or higher for HTTPS connections Salesforce critical update is enabled in your organization.

Pentaho Data Integration Tool 5.4 does not support TLS 1.1 and cannot connect to your Salesforce organization if this Salesforce critical update is enabled in the organization.

To resolve this issue, perform one of the following actions:

  • Use version 6.1 of the Pentaho Data Integration Tool to import data from various data sources to BMC Remedyforce.
  • Deactivate the Require TLS 1.1 or higher for HTTPS connections Salesforce critical update in your Salesforce organization.
    For information about when the critical update will be automatically activated, see Salesforce Knowledge Article Number 000232871.

Error running the Pentaho packages.

In some cases, you might also not be able to open the Enter Mapping window by clicking Edit Mapping in the Salesforce Upsert window.

All

In the Pentaho packages provided by BMC Remedyforce, ensure that the API version in the Salesforce Webservice URL field in steps, such as Salesforce Upsert, is supported.

  • In the LDAP Pentaho packages, the default API version in the Salesforce Webservice URL field is 51 (https://login.salesforce.com/services/Soap/u/51).
  • In all other Pentaho packages, the default API version in the Salesforce Webservice URL field is 51 (https://login.salesforce.com/services/Soap/u/51).

In the Salesforce Upsert window, when you click Edit Mapping, the following error message is displayed:

Certain referenced fields were not found!

All

Perform the following steps to resolve this issue:

  1. In the Salesforce Upsert window, click Edit Mapping.
    The Certain referenced fields were not found! error message is displayed.
  2. To open the Enter Mapping window, click OK.
    The tool removes all referenced fields from the existing mappings. The Pentaho package provided by BMC Remedyforce includes only one referenced field, BMCServiceDesk__CMDB_Class__c. The CMDB_Class field is no longer available in the Mappings column.
  3. In the Source fields column, select CMDB_Class and click Add.
    When you move CMDB_Class from the Source field column to the Mappings column, the c in the field name is replaced with r. For example, BMCServiceDesk__CMDB_Class__c is replaced with BMCServiceDesk__CMDB_Class__r.
  4. (Optional) Update mappings for other fields based on your requirements.
    For information about updating the out-of-the-box mapping, see Field mapping in CMDB 2.0.
  5. To save your settings and close the Enter Mapping window, click OK.

  6. In the Salesforce Upsert window, in the Module field column in the Fields area, click BMCServiceDesk__CMDB_Class__r, and replace r with c.

  7. To save your changes and close the Salesforce Upsert window, click OK.

Related topics

Applying models while importing CIs and assets

Scheduling jobs to import data

Troubleshooting common issues when importing data

Troubleshooting issues when importing data from BMC Client Management

Known and corrected issues for Pentaho packages

Was this page helpful? Yes No Submitting... Thank you
Last modified by Tejas Andhare on Aug 25, 2020
importing bcm rest_web_api best_practices integrating

Comments

Log in or register to comment.

Creating SRDs that require operational-rule deployment
Importing data from BMC Client Management by accessing the database
© Copyright 2013 - 2022 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2023 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.