Not to include details, but some quick notes for future reference.

  • If you are using a web activity to retrieve token, and the api requires Content-Type to be application/x-www-form-urlencoded, that means the username and password and some other parameters need to be passed in as key value pairs. Which is not supported in the ADF UI out of the box.

It’s relatively easy to find out that it needs to be passed in as Body, but the usual JSON format wont work. Follow this instead.

  • When you need to retrieve values from some of the response headers, and the header name contains a special chat like a hyphen -, Dot ., or question ?

Your expression editor screen wont be happy if you chose a header in a usual way like

--

--

--

--

I am not sure why I skipped this post for a while?? Maybe because I wasn’t reading much :(

But Let me resume it now!

By the way, I have moved mostly on Audible for all my reading (listening!) and do very little Kindle and Physical Book.

6. Grinding it out — by Ray Kroc, Robert Anderson

--

--

If you try to call a SOAP service via Postman, you may see an error “415 Unsupported Media Type”.

Usually, considering that it’s a SOAP Service, when you set Body type as XML, Postman automatically adds “Content-Type=application/xml” in the header.

That is the problem.

Go to headers from the request section, and uncheck the box in front of Content-Type. Then manually add another entry for Content-type and select text/xml as its value.

This should resolve the issue.

--

--

Mayur Macwan

Mayur Macwan

88 Followers

Sr. Consultant @ Cluster Reply, UK. ex. Founder & Product Manager @crawdedindia