Resources - Page 3 of 5 - LuminosityCRM

March 31, 2017

How To: Use conditional logic to control the logic of the Custom Button

Conditional logic in the custom button provides control and flexibility for the Super Clone and Super Clone Pro custom buttons. All of the URL parameters that get passed into the Super Clone and Super Clone Pages can be surrounded by Salesforce’s formula logic. Here is an example of using a different configuration based on an Opportunity’s stage. Similar conditional logic could be used for record types or any other field […]

April 2, 2017

How To: Clone an Opportunity with Quote and Quote Line Items in Salesforce

New Opportunities and Quotes in Salesforce are often similar to ones that already exist. Salesforce has the ability to clone an existing Opportunity with Products, but the ability to set values or include other relationships is missing. Super Clone Pro excels in this area because it gives you the ability to set field values and clone multiple relationships up to four levels deep. You have control of the cloning process […]

May 25, 2017

How To: Clone a Parent Object and Move Child Records to the New Parent Object

This post will show you how to clone a record and move child records from the original record to the new cloned record. To do this we use a combination of Super Clone Pro and Process Builder. Two very simple objects will be used in this example to illustrate the concept. However, this can be applied to any two objects that have a lookup relationship or master-detail relationship that can be reparented. […]

December 16, 2017

How To: Filter Records in Related Lists With Super Clone Pro

Some Super Clone Pro cloning and editing use cases require filtering out records from child relationships. Filtering child relationship records can be accomplished in two ways. First, the configuration can use a checkbox field to filter records from an object. Second, a ‘selectwhere’ parameter can be used to pass selection criteria to a page, process builder or API. Checkbox Filtering URL Parameter Filtering Checkbox Filtering In the field section […]

February 7, 2018

How do I style Super Clone Pro for Lightning Experience (LEX)

The clone, copy, and edit pages are built with Salesforce’s Visualforce technology, and by default the pages inherit the Classic page style. There are two ways to apply Lightning styles. The easiest way is to add the URL parameter “lss=1”. Super Clone Pro looks for this parameter, and it will turn on the Visualforce lightningStylesheets tag to true. Here is an example of the custom button. /lcrm-scp__scpClone?lss=1&rid={!MyObject__c.Id}&cfg=MyConfig The second way […]

February 19, 2018

How To: Clone a Hierarchy of Records Asynchronously with Super Clone Pro

Cloning large and complex hierarchies of records can run into platform limits. Salesforce’s governor limits for CPU time limit, heap size, and view state can prevent successfully cloning a hierarchy. Factors that impact this include a large numbers of records, lots of data in the records, or a significant amount of custom Apex/Workflow/Formula logic. One solution is to run the Super Clone Pro process asynchronously. This provides higher limits to […]

April 25, 2018

How To: Clone a record and delete the original record in Salesforce

Deleting the original record after successfully cloning it can be accomplished with a combination of Apex, a custom field, a Process Builder, and Super Clone Pro configurations. This sounds like a lot, but I promise that it will be easy. These directions will give you the Apex code that lets a Process Builder delete records, and they will illustrate all of the other settings you’ll need. Fist we will get […]

June 24, 2018

How To: Increment a sequence in a text field when cloning a record in Salesforce

Super Clone Pro is a flexible tool that lets you set field values for your cloned records. However, one feature that it doesn’t contain is the ability to set an incremented sequence number in a name or text field when a record is cloned. Super Clone Pro doesn’t contain the feature because it requires querying other existing records to find the next highest sequence number. Depending on the environment, processing […]