- Series: Developer's Library
- Paperback: 496 pages
- Publisher: Addison-Wesley Professional; 2 edition (July 11, 2011)
- Language: English
- ISBN-10: 0321767357
- ISBN-13: 978-0321767356
- Product Dimensions: 7 x 1.1 x 9 inches
- Shipping Weight: 1.9 pounds (View shipping rates and policies)
- Average Customer Review: 20 customer reviews
Amazon Best Sellers Rank:
#579,598 in Books (See Top 100 in Books)
- #193 in Books > Computers & Technology > Networking & Cloud Computing > Data in the Enterprise > Client-Server Systems
- #213 in Books > Computers & Technology > Networking & Cloud Computing > Cloud Computing
- #317 in Books > Computers & Technology > Networking & Cloud Computing > Networks, Protocols & APIs > Networks
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Development with the Force.com Platform: Building Business Applications in the Cloud (2nd Edition) (Developer's Library) 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
About the Author
Jason Ouellette led the development of popular AppExchange applications such as Appirio Cloud Sync, CloudWorks, and Professional Services Enterprise. He is an independent technology consultant with deep experience in cloud and enterprise integration. He has been inventing cutting-edge enterprise software for more than 15 years at Appirio, Composite Software, and webMethods. He was recognized by Salesforce as a Force.com MVP in 2011 and Force.com Developer Hero in 2009.
He lives with his wife and two geriatric cats in San Francisco, California.
Top customer reviews
You will find that you're going to need more detailed information such as, the specifics of the Apex language, Visualforce and DML. However, as I continue to learn these more advanced/detailed topics, I am extremely prepared to absorb their contents because this book has given me a great foundation.
Just after finishing the book, I had a task at work to connect to a Salesforce Apex web service after having authenticated with OAUTH authorization. I set aside Mon and Tue to get that don , yet by Mon afternoon, I was rocking and rolling.
While the book had very good coverage, this version didn't talk at all about packaging and deployment, which I was so curious about. But, no big deal because all of that stuff is available in other places.
The authors writing isn't always perfect. I'm big on that stuff when it comes to technical stuff.
The book is written as a tutorial with examples to follow and implement.
The first, somewhat minor, issue I have is that the book goes into a lot of detail before going through the example. I find this kind of annoying because a feature is being discussed that hasn't really been introduced. (It feels a little like Ira Glass on this American life. Let's give you a lot of detail, but not the reason why someone ended up this way ;) )
Second, I found some of the detail difficult to follow because it was presented in sentences, rather than a more simple form, like a chart. So for example, it has a section on building tables and describes in text how to build the table e.g. "Billable hours is a Number with a length of 7 and 0 decimal places. Currency fields (Budget, Expense Budget) have a length of 16, with 2 decimal places." The book is supposedly for developers. Put this detail in a chart, e.g. "Field Name, Data Type, Validation" it will be much easier to follow.
This brings me to the third and perhaps most significant issue. There are charts earlier in the chapter that seem to show the table layout, so I figured, I'll just follow those, right? Well, yes, most of the time, but there is a lot of inconsistency between the charts and the text further on in the chapter. I don't think I'm being too picky here. Every table has at least one error, so you have to jump back an forth, multiple times, between the text and the chart to build the tables.
-Multiple times the chart says the field is boolean. Unfortunately, there isn't a boolean data type in force.com, or at least one that is easy to get your hands on (please correct me if I'm mistaken} and the examples in the text will either specify a different data type or use a formula that evaluates to text.
-The text will use a formula that relies on a field that it never asks you to create. So you have to go back to the chart to figure out the details of that field.
-The field type on the charts often differ from the text. So the chart will have type "Text" and the description further in the chapter will say create a pick list.
Frustration aside, I think I am learning the basics of force.com from this book and will continue to slog through it.
In fact, most of the book isn't about classical development at all: it's really a guide to how to *think about* applications in the context of Salesforce.com, how to configure the system, and how to understand its object model. All good things, but when it comes to coding it felt like there was maybe 40 pages -- 10% of the book.
The important things you will understand when you read the book carefully:
* The object model
* Their MVC model
* The model for API and web services calls
* When to use which language (VisualForce, APEX, etc.)
* What tools are available for developers and administrators
* SFDC's jargon
* SFDC's commercial ecosystem
The important things you won't get from this book:
* Significant code samples
* An understanding of important tricks (such as remoting, encapsulation,
cross-language references, etc.)
* Coding patterns or common use cases
Unfortunately, I don't believe these topics are available in any book. If they were, I'd buy it immediately.
But this one just left me hungry for more.
Most recent customer reviews
I don't remember why I bought this. I think I am getting it confused with another book. I will have to re-edit again.