You need to sign in to do that
Don't have an account?
Chris Berg 6
.NET Sample code for SOAP API out of sync with the WSDL
None of the sample code I tried for .NET using the Enterprise WSDL would work until I modified it for an explicit "out" parameter. Every .NET programmer that tries the sample code will hit this problem. Example:
// Call describeSObjects() passing in an array with one object type name
DescribeSObjectResult[] dsrArray;
client.describeSObjects(
header, // session header
null, // package version header
null, // locale options
new string[] { entityName }, // object name array
out dsrArray
);
Please SF, sync up your samples with the changes to your WSDL for a better .NET experience. =)
// Call describeSObjects() passing in an array with one object type name
DescribeSObjectResult[] dsrArray;
client.describeSObjects(
header, // session header
null, // package version header
null, // locale options
new string[] { entityName }, // object name array
out dsrArray
);
Please SF, sync up your samples with the changes to your WSDL for a better .NET experience. =)
I will validate this and forward to the appropriate team to get the changes made.
https://developer.salesforce.com/page/Consuming_Force.com_SOAP_and_REST_Web_Services_from_.NET_Applications
My developer cannot get the enterprise Query example to work - keeps getting "not enough parameters" error message (as per Chris Berg suggestion above).