Author: TomdeMan
Related Categories:
SalesForce CFC, ColdFusion
January 29, 2010
SalesForceCFC has been stable, but there is always room for improvement. This version includes a few tweaks and clean up.
I would also like to put out a 'Call for Features' to put on the roadmap for 1.0
Some already suggested:
-support for SOQL sub/nested queries
-asynchronous HTTP calls
Please post your suggestions on the Forums @ RIAForge or just leave a comment here.
In addition, I will be including a base unit test collection to provide stability for future releases and customization. Along with improved documentation and code samples.
I'd like to thank Daniel Llewellyn and Pete Freitag for their contributions, as well.
0.7 -CHANGE LOG- 1/24/2009
- enhancement - added support for batch save
- enhancement - added support for AssignmentHeader
- enhancement - added support for EmailHeader
- enhancement - added result size to query return data
- enhancement - updated typing and case of component
- enhancement - increased default SOAP timeout
- deprecated - unnecessary setters (setServerURL,setSessionId,setLastLogin)
Comments:
[Add Comment]
Rober says:
Hey Tom,
I've just been commisioned to do a fairly large amount of work with the SalesForce API and have just this second downloaded your CFC to have a play with before even looking directly at the API itself.
Can uou tell me, what are the benefits of rolling your own SOAP reqiests and then using cfhttp rather than just using cfobject of createObject to interact with the services themselves and having CF do all the hard work of writing the SOAP requests?
Look forward to exploring and growing the project with you over the coming few months. :-)
Thanks,
Rob
2/2/10 3:37 PM
Tom de Manincor says:
@Rob - Using CF to create and work with the objects was my preference, as well. I had initially given it a try, but ran into some issues. I reached out to a few others and was advised that the manual creation of SOAP packets was going to be most flexible and efficient for the time line I was under.
If I remember correctly the issue arose when trying to manipulate the SOAP headers. For some reason the CF webservice objects would not generate the accepted SF format.
Let me know if you have any luck with that approach. The SF API was also at version 11, maybe things have changed since then.
2/3/10 7:25 AM
Rober says:
Yeah I figures something like that would be the issue, I've had similar issues with a lack of flexibility in the CF web services talking to other servers.
I've not made any attempts to connect using cfobject yet myself, I'll be playing a great deal more with this over the comming weeks to see how I get on, I'll of course keep uou up to date.
I'm sure i'll be able to contribute some time to this project and help grow the feature set you've started.
Rob
2/3/10 7:38 AM
[Add Comment]