I've seen a lot of coders put the following into their custom Visualforce controllers: I've decided that I don't like this approach. It feels too much like a URL hack, and though I'm sure that it will always work (meaning that salesforce.com will never change its way of referring to a record by /<recordID>), I'd like to suggest a different method that may use more resources, but will leverage standard controllers, possibly future-proofing the application: What do you think? Does anyone have coding-style tips to share?
Archives for May 2011
Yesterday, I used Content Delivery to send a pdf to a client. Simple, right? Upload the Word document to Content, associate it with a record, and deliver the content. Surely if I upload a new version, the delivery will refer to the latest version, right? There’s no place to select that option, so I can assume, right? Wrong. This is the screen I see when I choose to deliver a given file. Note that I can choose whether to allow access to the original file or only to a pdf… but nothing about which version to deliver. (There are 4 versions right now.) The document in question needed some changes, so I uploaded a new version and told the client that the old link would still work. Oops. By default, Content Deliveries are set to refer to one specific version of a Content file. I can understand this, but surely […]