July 2, 2014
We're wrapping up a Workday integration via their web services. The objects we're dealing with in the web services calls to Workday contain a lot of information in very deep object graphs that are not necessarily initialized. I learned a couple of new tricks this time around with web services that makes the consumption and related testing of these objects relatively painless. To be clear, you'll likely run into this scenario working with any web services in .NET. I just happened to be working with Workday web services when I decided to write this post. The first thing I need to do is get the Workday web services response object mapped to a type for all of my code to consume. I don't have any interest at all in writing a ton of left / right code that looks like this: public…
Workday Integration via web services: Dealing with deep object graphs
July 2, 2014
We're wrapping up a Workday integration via their web services. The objects we're dealing with in the web services calls to Workday contain a lot of information in very deep object graphs that are not necessarily initialized. I learned a couple of new tricks this time around with web services that makes the consumption and related testing of these objects relatively painless. To be clear, you'll likely run into this scenario working with any web services in .NET. I just happened to be working with Workday web services when I decided to write this post. The first thing I need to do is get the Workday web services response object mapped to a type for all of my code to consume. I don't have any interest at all in writing a ton of left / right code that looks like this: public…