<{{Subtitle_Weight}} class="prominent-subhead {{Show_Subtitle}}"> {{Header_Subtitle}}

K2 connect SmartObject returns "Input string was not in a correct format" error.

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


After transferring a K2 Connect service object from an older version to a new server using K2 connect 4.7.1, or after upgrading K2 connect to 4.7.1, K2 connect SmartObjects starts returning an "Input string was not in a correct format" error.



  • When testing the BAPI method in Test Cockpit, the same "Input string was not in a correct format" error appears
  • The error will not appear if you leave the input parameters empty
  • The error only appears for a method that accepts complex objects (eg. XML)
  • No such error occurs with previous versions of K2 Connect.


  1. Launch your K2 Connect Administration tool
  2. Click on Settings


  3. Click on Configure Destinations


  4. Right-click on your SAP destination, and select Destinations > Modify


  5. Add DELTA=0 in the connection string: e.g ASHOST= SYSNR=00 CLIENT=500 LANG=EN DELTA=0 USER=user PASSWD=pass


  6. Click OK to save the updated connection string
  7. Test your destination to make sure there are no errors in the connection string.