Savon 2.3.0 causes "Requested value 'APIObject' was not found." error

[bbakersmith]

Savon 2.3.0 causes "Requested value 'APIObject' was not found." error

[MichaelAllenClark]

Would it be possible to share the entire output from running sample-dataextension.rb from the samples directory?

[bbakersmith]

Yep, it appears to fail on the very first post test:

">>> Get all of the DataExtensions in an Account"
"Retrieve Status: true"
"Code: 200"
"Message: OK"
"MoreResults: false"
"RequestID: 840e0263-5ad2-4ed8-9845-e86124825563"
"Results Length: 60"
">>> Create Data Extension"
"Post Status: false"
"Code: 200"
"Message: Error"
"Results: [{:status_code=>"Error", :status_message=>"Requested value 'APIObject' was not found.", :new_id=>"0"}]"
"Caught exception: Failure creating data extension"
["./samples/sample-dataextension.rb:41:in `

'"]

[MichaelAllenClark]

I am guessing that when FuelSDK gem was installed, it used the version from RubyGems.org which I haven't had a chance to update with the most recent changes. If you could build/install the gem from the source and give it one more try:
gem uninstall fuelsdk
gem build fuelsdk.gemspec
gem install fuelsdk-0.0.5.gem

[bbakersmith]

I tried this, but still get the same error both for the sample-dataextension.rb script and my own spec tests.

The sample-dataextension.rb output is identical to what I pasted above (but with a different RequestID).

I checked the version of the fuelsdk gem currently installed on my system and it shows up as 0.0.5

[MichaelAllenClark]

I was able to replicate the issue by updating savon to 2.3.0. It appears that it introduced a breaking change to the FuelSDK. When I reverted back to 2.2.0 the issue went away. Please confirm that you have savon 2.3.0. This would explain why you would receive the same error when using the master branch of the SDK and the Dot9Refactor branch.

[bbakersmith]

Ah yes, that did it, thanks for hunting that down!

FWIW, I don't think you have to specify the savon gem in the Gemfile since it's referred to in the gemspec.

[xjunior]

Have anybody figured why does this breaks with Savon 2.3 and above? Savon is already in 2.5 and is a really stable gem. The real issue should be addressed while we keep Savon 2.2 as a palliative solution only.

[xjunior]

Thanks for the reply, @ExactTarget. You're great at providing support.

[mikepcoke]

I am getting this same issue trying to create a new list. When I installed savon in my Gemfile it installed 2.11.1 by default. I also tried just installing savon 2.2 on the command line (after removing 2.11.1)

But I still get the same error about APIObject not found.

@Body=
{:create_response=>
{:results=>
{:status_code=>"Error", :status_message=>"Requested value 'APIObject' was not found.", :ordinal_id=>"0", :new_id=>"0", :object=>{:partner_key=>nil, :object_id=>nil}},
:request_id=>"ff4d2256-dc36-4fb3-a6a2-7ab05b3ef494",
:overall_status=>"Error",
:@xmlns=>"http://exacttarget.com/wsdl/partnerAPI"}},

Not sure if there is something else obviously potentially going on or if this might be Savon related?

[c4collins]

Hey there,

I don't know if this is still an issue, but I came across this problem and then fixed it today in my own implementation of the ExactTarget SOAP API (in Python, mind you).

The meaning of this error:
When you submit a request to ET's SOAP API you have to declare the type of the object and make sure it matches the expected format. In most cases, if you screw up that format, ET will be very explicit about what the expected object was (i.e. "Requested value 'RetrieveRequest' was not found.") , but there are a few methods that aren't as strict and will accept multiple object types (Delete is the one that caught me out today), and in that case it gives the generic error for the superclass APIObject - "Requested value 'APIObject' was not found."

The solution:
I have no idea where this would be cropping up in the SDK, because I'm building my own, but basically I just had to set up a switch to determine the type of the object (usually just by passing in an object_type value) and then ensure that the correct object is created and sent to the SDK for each different ObjectType.

[xjunior]

I had to deal with these guys on my previous job. It was horrible. I hope I never have to deal with ExactTarget or it's crappy and old SOAP API, along with their horrible support.

[dopstar]

@c4collins are you perhaps planning to share your own implementation in future?