Perspectives on Salesforce.com

The Salesforce Analytics Blog has a good post on passing report criteria via the URL.

I posted about this a while ago, but their solution shows how you can pass field name, comparison operator and value via the URL. Mine only shows how to pass the value over, which required the report to already be setup with the criteria lines waiting for the value. This new solution allows a single report to exist with no criteria lines whereby you pass over those criteria lines via the URL. Pretty slick!

Part 3 of the the O’Reilly Network’s 3-part series about Salesforce.com was posted today. It’s called Packaging for Salesforce.com’s AppExchange.

I updated my original post with the a link to part 3. You can get to all of them from there.

This post only applies to relationship fields (lookup and master-detail) that went through the Winter ’07 upgrade.

If you plan to use SOQL relationships in queries that have custom relationships to other objects, you should go and edit your custom relationship fields to include a Child Relationship Name. This allows you to use a user-friendly name for the relationship when querying the master object.

Going forward, this field is set for you. However, after the Winter 07 upgrade, this field was left blank on all relationship fields. Without making this update, SOQL relationships will still work, but you will be forced to use an archaic value for the relationship name. That archaic value will look like a Salesforce ID.

The Salesforce online help has very good documentation on relationships, but here’s a quick example.

Suppose you had 2 custom objects before the Winter 07 upgrade: Quote and Quote Line. Quote Line has a relationship field called Quote, which sets a master-detail relationship between quote (master) and quote line (detail). After the Winter 07 upgrade, the Child Relationship Name on that relationship is null. You need to update it. To do so:

1. Go to your custom object (Quote Line in this example)
2. Edit the Quote relationship field
3. Provide a value in the Child Relationship Name field

Doing this allows you to make a query like:

Select q.Name, (Select Id, Name From Quote_Lines__r) From Quote__c q

To get this setup correctly in your org, you should go through each object and make sure this is set for all custom lookup and master-detail relationship fields. You’ll probably use SOQL relationships someday. May as well fix it now.

We have a new developer-focus Salesforce blog out there. It’s called Decoding Salesforce . According to the About page on the site:

The decoding salesforce blog is developed as a way for Eoin and Ale to talk about the development of scripts/formulas and customization for the salesforce.com application.

We both work with salesforce on a daily basis as administrators and have extensively customized our applications to serve our business purposes. Please feel free to add comments/questions to the posts as we go along and we’ll do our best to answer them.

Finally if you have any ideas or would like to contribute to this site please let us know at team(at)salesforce(dot)phollaio(dot)com

This project, and the associated code, are developed by us, and are not officially supported, associated or endorsed by Salesforce.com.

There are a bunch of interesting posts so far, but an interesting idea is their set of bookmarklets called SFDCMe.

The goal of SFDCMe is to implement a few, useful bookmarklets to avoid Salesforce.com Support Reps spending a ridiculous amount of time clicking here, there

Nice to see more Salesforce developer-focused blogs out there.

In case you don’t already subscribe to Simon Fell’s pocketsoap blog , he just posted a couple items relevant to the new Winter 07 functionality.

• Apex Web Services: Explains how you can expose your Apex code as a Web Service available to any web application.
• SOQL-R: A 101 on the new SOQL’s support for relationships (joins).