<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Salesforce Admin and Developer Blog</title><link>http://www.interactiveties.com/blog</link><description>Salesforce and Force.com Platform Administrator and Developer blog by Interactive Ties.</description><lastBuildDate>Tue, 09 Feb 2016 21:25:12 +0000</lastBuildDate><language>en-us</language><image><url>http://www.interactiveties.com/img/ilikecows_greghacic.png</url><width>73</width><height>73</height><link>http://www.interactiveties.com/blog</link><title>Salesforce Admin and Developer Blog</title></image><pubDate>Tue, 09 Feb 2016 21:25:12 +0000</pubDate><managingEditor>greg@interactiveties.com (Greg Hacic)</managingEditor><atom:link href="http://interactiveties.com/incl/blog.xml" rel="self" type="application/rss+xml"/><item><title>Pass Values to New Opportunity Using Apex</title><link>http://interactiveties.com/blog/2016/opportunity-values-via-apex.php</link><description><![CDATA[Last year I wrote a post describing how to pass values to a new opportunity using the URL. This post is simply an alternative to accomplish the same goal of auto-populating values to a new record except using Visualforce and an Apex Class controller. For the purposes of our demonstration we will make some general assumptions about the values we want to pass to the new record. To keep it simple we plan on populating the Name, Stage and Close Date of the new opportunity. We will also make the logic flexible enough so that if Salesforce happens to pass additional information we will be able to include those key value pairs as well.[<a href="http://interactiveties.com/blog/2016/opportunity-values-via-apex.php">Read More...</a>]]]></description><pubDate>Tue, 09 Feb 2016 03:37:17 -0500</pubDate><guid isPermaLink="true">http://interactiveties.com/blog/2016/opportunity-values-via-apex.php</guid><author>greg@interactiveties.com (Greg Hacic)</author></item><item><title>Locale Aware DateTime Component</title><link>http://interactiveties.com/blog/2016/locale-aware-datetime-component.php</link><description><![CDATA[I am working with a client that is deploying some existing Visualforce pages to international Users. The Visualforce includes some Date and DateTime values so I checked them to make sure they would render appropriately for people accessing the logic internationally. It turns out that the original Visualforce code uses the &lt;apex:outputText&gt; tag to drive formatting for much of the Date/DateTime values within the pages. Therefore, I am converting the occurrences of each &lt;apex:outputText&gt; tag to the Visualforce component I built for rendering.[<a href="http://interactiveties.com/blog/2016/locale-aware-datetime-component.php">Read More...</a>]]]></description><pubDate>Thu, 28 Jan 2016 09:26:31 -0500</pubDate><guid isPermaLink="true">http://interactiveties.com/blog/2016/locale-aware-datetime-component.php</guid><author>greg@interactiveties.com (Greg Hacic)</author></item><item><title>UNABLE_TO_LOCK_ROW Error Message</title><link>http://interactiveties.com/blog/2016/unable-to-lock-row.php</link><description><![CDATA[I was recently developing some Apex logic and encountered the UNABLE_TO_LOCK_ROW error while running my Apex unit tests for the new code. This UNABLE_TO_LOCK_ROW error message can happen when unit tests update the same record(s) at the same time or when unit tests try to create records with duplicate index field values. One way to avoid this UNABLE_TO_LOCK_ROW error is to simply turn off parallel test execution. This can be accomplished via Setup > Develop > Apex Test Execution.[<a href="http://interactiveties.com/blog/2016/unable-to-lock-row.php">Read More...</a>]]]></description><pubDate>Wed, 27 Jan 2016 03:40:22 -0500</pubDate><guid isPermaLink="true">http://interactiveties.com/blog/2016/unable-to-lock-row.php</guid><author>greg@interactiveties.com (Greg Hacic)</author></item><item><title>Edit Link Override Visualforce Page</title><link>http://interactiveties.com/blog/2015/edit-link-override-visualforce.php</link><description><![CDATA[I just built a Visualforce application that people can use to associate a number of "child" records to a single "parent" record. Let's say that the application uses the Account object as the standard controller and then we extend the logic so that we can find, manipulate and link many Contact records. The functionality of the application is not important for this post but how we access the application is important.[<a href="http://interactiveties.com/blog/2015/edit-link-override-visualforce.php">Read More...</a>]]]></description><pubDate>Wed, 30 Sep 2015 05:30:20 -0400</pubDate><guid isPermaLink="true">http://interactiveties.com/blog/2015/edit-link-override-visualforce.php</guid><author>greg@interactiveties.com (Greg Hacic)</author></item><item><title>Custom Error Handling in Visualforce</title><link>http://interactiveties.com/blog/2015/visualforce-custom-error.php</link><description><![CDATA[I am a big fan of developing Visualforce pages that are useful to humans. This means providing helpful feedback to the person interacting with the application in order to limit User frustration. In some circumstances this means providing clearer error messaging rather than simply outputting any system generated errors.[<a href="http://interactiveties.com/blog/2015/visualforce-custom-error.php">Read More...</a>]]]></description><pubDate>Mon, 31 Aug 2015 05:03:36 -0400</pubDate><guid isPermaLink="true">http://interactiveties.com/blog/2015/visualforce-custom-error.php</guid><author>greg@interactiveties.com (Greg Hacic)</author></item></channel></rss>
