Hi, For efficiency I need to gather all with a single SOQL; however can someone point me how to achive a lookup type scenario with a single SOQL; Some snippet I have:

for(Contact cnt_old:oldContacts) { List cnt = [select email from Contact where id =: cnt_old.masterrecordid];

I need to use masterrecordid due to delete happens from a merge action and get other cols of the winning records.

After getting winning records/cols I then need to relate to oldContacts....both queries are on same contact obj

So, now I have select within For loop, which I need to avoid, thanks!

Hi, Experts - 

Where can I find out what objects are used to store view hierarchy shown in Account page; or they are stored in memory. I need to flag records when decoupled from a hierarchy relationship, thanks!

Hi, Experts - 

How can apex:chart be inside as apex:outputpanel tag. Once placed charts are not generated, however when place outside

outputpanel, all works. But I need to get charts within panel, Any ideas ?

Thanks,

Hi, experts - 

Reletively new to SF, I got  a standard controller on contact and thru extension I am trying to save records to a custom

object. Records are retrived on a VF page. It is not saving. Snippet:

List<customobj__c> cp =
 [select id from customobj__c limit 1
];

public void save() {update cp; }

save is called as

<apex:commandButton id="update" action="{!save}" value="Save"

If it is an invalid design, how can I write to another object when controller is on contact object ?

Thanks!

Hi, Experts -

In SalesForce Limits Quick Ref middle of page 16 states:

The number of posts, comments, and tracked field changes available in the Chatter feed. Currently tracked fields without

likes or comments are deleted after 90 days.

We needed clarifications on deletes; what records are getting deleted after 90-days i.e. posts w/o likes, comments on tracked fields ?

Thanks,

Hi, Experts - 

Could some one please drop a few snippets on how it would look to have a after delete trigger, so when a row is deleted on the triggered object deleted row gets archived (inserted) into another custom object ?

Thanks,

Hi, experts - 

Reletively new to SF, I got  a standard controller on contact and thru extension I am trying to save records to a custom

object. Records are retrived on a VF page. It is not saving. Snippet:

List<customobj__c> cp =
 [select id from customobj__c limit 1
];

public void save() {update cp; }

save is called as

<apex:commandButton id="update" action="{!save}" value="Save"

If it is an invalid design, how can I write to another object when controller is on contact object ?

Thanks!

Hi, Experts - 

Could some one please drop a few snippets on how it would look to have a after delete trigger, so when a row is deleted on the triggered object deleted row gets archived (inserted) into another custom object ?

Thanks,

We have a beta version of a functional equivalent of TRUNCATE SQL available on Sandbox organizations. Please open a case with support if you would like to try it out.  We will make a decision on when to GA based on adoption and feedback.

Truncating a custom object does the following:

• Permanently disassociates ALL the object's data records from the object. You will not be able to operate on them using this object and they will not be recoverable from the Recycle Bin.
• Recalculates values in Roll Up Summary Fields in parent objects that reference the object. You will not be able to recover the values that existed prior to the truncate. 
• Creates a "shadow" custom object . This is a deleted custom object  associated with the truncated data records. Its name consists of the truncated object's name suffixed by "_trunc_n" where n is the number of times the object has been truncated. Like any deleted object, the shadow object will appear in the deleted objects list until you permanently erase the object and its data, or 45 days have passed. While it is in the deleted objects list  you can undelete the "shadow" and the data stored in it to create a new custom object. An undeleted  "shadow" custom object will not be a clone of the truncated table. It will not have any of the truncated object's :

• relationships with other objects. Any foreign key fields will be converted to read-only text fields.
• Autonumbers. AutoNumber fields  will be converted to read-only text fields
• workflow rules or actions 
• reports
• formula fields
• roll-up summary fields
• validation rules or approval processes
• Apex Code triggers
• translations
• field history