Comment 4 for bug 1210775

Hi Grzegorz,

I can't reproduce your issue with a standard Magento 1.7 and the last revisions of the connector.

I also tested a simple XML/RPC call against Magento 1.7 with Ruby (using [0]) which show that the nil/None value is correct to return 'all the fields'. (contrarily to the false value which is not used by the connector here.)
>> m.call('customer.info', 1, nil)
=> {"customer_id"=>"1", "created_at"=>"2007-08-30 23:23:13", "updated_at"=>"2008-08-08 12:28:24", "increment_id"=>"000000001", "store_id"=>"1", "website_id"=>"1", "confirmation"=>nil, "created_in"=>nil, "default_billing"=>"274", "default_shipping"=>"274", "disable_auto_group_change"=>"0", "dob"=>nil, "email"=>"<email address hidden>", "firstname"=>"John", "gender"=>nil, "group_id"=>"1", "lastname"=>"Doe", "middlename"=>"", "password_hash"=>"2049484a4020ed15d0e4238db22977d5:eg", "prefix"=>"", "rp_token"=>nil, "rp_token_created_at"=>nil, "suffix"=>"", "taxvat"=>""}
>> m.call('customer.info', 1, false)
=> {"customer_id"=>"1", "updated_at"=>"2008-08-08 12:28:24", "increment_id"=>"000000001"}

This thing questions me about the integrity of the data on your Magento instance unfortunately:
api.call(customer.info, [656, None]) returned {'customer_id': '656', 'updated_at': '2013-02-01 13:20:57', 'increment_id': ''}
As you can see, the 'increment_id' is empty. It should have returned a value, as you can see in my example call above.

Do you have any custom modules on Magento which could alter the normal behavior of the API?
Can you open the customer 656 on the Magento admin panel and see how it looks, if it looks normal?

[0] https://gist.github.com/guewen/1875404