Introduction

When making use of the SmartObject Service Tester Tool to update the K2 connect Service Instance, some of the settings are not updated and causes SmartObject property inconsistencies.  This is due to the TypeMapping data not being populated, as the SmartObject Service Tester Tool incorrectly handles the TypeMapping data as an object which then cannot be handled correctly.  This data is needed to correctly map SAP properties to SmartObject properties.

Example Scenario

 
An example of updating the K2 connect Service Instance using the SmartObject Service Tester tool is described below. 

  1. Create a K2 connect Service Object in Visual Studio.  Make use of the BAPI_EMPLOYEE_GETDATA.
  2. In the Function Interface select the following properties :

    'DATE0'
    'FSTNAME_M'
    'LASTNAME_M'
    'PERSONAL_DATA'
  3. Before publishing the Service Object, click on the ‘K2 blackpearl Settings’ button and ensure that the “Generate SmartObjects” checkbox is not selected.
  4. Publish the Service Object.
  5. Open the SmartObject Service Tester Tool and expand K2 connect Service > Connect Service for [server_name] > Connect Objects > [object_name] > Properties.  Note that the datatypes for the properties are correct.
  6. From the SmartObject Service Tester Tool, right- click on the “Connect Service for [server_name]” and click on Edit.
  7. Click Next, then Update.
  8. Note that the datatypes have incorrectly been changed to Memo.

Resolution

K2 recommends that the SmartObject Service Tester Tool is not used for updating or editing the K2 connect Service Instance.  The K2 connect Admin Tool should be used at all times.

Workaround

After updating the K2 connect Service Instance using the SmartObject Service Tester Tool, the TypeMapping data will be missing.  To fix this, delete the K2 connect Service Instance and register the K2 connect Service Instance again using the K2 connect Administration Tool.