Skip to Content

Tracing / Debugging for Web Service Calls in C4C

Dear Experts,

are there any possibilities to trace / debug code in events (like after-modify) that are triggered for incoming web service calls in C4C?

Starting tracing in Cloud Applications Studio or setting breakpoints has no effect. An error is returned to the web service consumer, but the debugger does not stop at the defined breakpoint and the local traces are empty.

Thank you for your advice!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 28, 2017 at 06:42 AM

    Hello Florian,

    maybe the code doesnt even get to the point where the breakpoint is set.

    I would suggest you to set the breakpoint at the first line of code in the script you need to debug.

    In that way you make sure that the code does get triggered in the first place and if you need to jump to the next breakpoint you can do that via SHIFT+F11.

    Kind Regards,

    Johannes

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 28, 2017 at 11:46 AM

    Thank you for your reply. Actually the breakpoint is already at the first line of code. I have also tried to add a "Trace"-Statement as the first line of code.

    Could it be the case that the debugging / tracing is only done for the technical user that is currently logged on? Actually the web service call if course is using the user as specified in the communication arrangement.

    Thanks!

    Add comment
    10|10000 characters needed characters exceeded