Author: TomdeMan
Related Categories:
ColdFusion, SalesForce CFC
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:
(Comment Moderation is enabled. Your comment will not appear until approved.)
[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
Billy says:
First of all, thanks Tom for the Salesforce CFC. It has been very helpful to me in building an integration between Salesforce and our legacy system.
Do you plan to update SalesforceCFC to use API version 16 or higher? I keep bumping into the lack of JOIN functionality in SOQL for API version 11.1, but 'semi-join' is available with version 16 and higher.
Thanks again.
7/12/10 2:36 PM
Tom de Manincor says:
@Billy - I do plan on updating it for the new API. It's just a matter of finding some extra time to put into the project.
7/23/10 8:51 PM
Axel Schultze says:
I downloaded it in Feb/10 but never had the time to play with it. So not exactly a feature request but a gigantic help would be a few demo pages.
Like Get 20 contacts from SFDC with all the details on a page - edit contacts and push it back to SFDC. Maybe create custom field called __demo on SFDC and you write back only of the checkbox of that field is checked. - Oh well just a thought.
10/9/10 12:35 AM
[Add Comment]