- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hello Jonas,
I'm sorry, but when I check the same code is OK for me.
The only problem I had was the 'webapp' account were not allowed to use the method, but if I add the "content" right to the 'webapp' operator, it works.
First, you can check if the webapp has the 'content' right.
The error 'XFR-180000' you have only appears when I put a wrong schema in the third parameter (for example, I put 'rbe:bloContent|89480') but it shows the wrong name in the path "XFR-180000 The file '/usr/local/neolane/nl6/datakit/rbe/eng/schema/bloContent.xml' does not exist".
Also, I confirm the (undocumented...) format of the third parameter is "ns:schema|id" (tryied with id only and it failed with XFR-180000 error). To get this information, I caught how the console request the server via SOAP and saw that format (and I agree, there is very few documentation about it).
If you have access to a Windows Adobe Campaign Server version (be sure the build is the same of your console), you will find "bin/tools/traceview.exe" program. This local tools allows you to see the request/response between your console and the server (you have to enable the trace by pressing SHIFT+F3 in the console, 'Traces ON/OFF' will swicth on the bottom bar).
Cedric
Views
Replies
Total Likes