Super Clone Archives - LuminosityCRM

March 4, 2017

How do I work around the ‘An internal server error has occurred’ when cloning an Opportunity?

Cloning an Opportunity that has Quote Syncing turned on may cause ‘An internal server error has occurred’ type of error. The Salesforce platform gets confused because the new cloned Opportunity has a field that references a Quote on the original Opportunity. The field that holds the record id of the synced Quote will need to be cleared. On the clone configuration, set the ‘SyncedQuoteId’ action to ‘Leave Empty’.

March 4, 2017

How do I work around the ‘Maximum view state size limit (135KB) exceeded.’ error on the Configuration Page?

This error occurs when an object has a significant number of fields and/or child relationships. Modifications were made to the Configuration page that improve its ability to mange information about the objects in recent versions of Super Clone. Here is a list of potential workarounds. Non-profit companies may upgrade to the latest version of Super Clone. For-profit companies are encouraged to upgrade to Super Clone Pro. The workaround for this […]

March 4, 2017

How do I fix the error ‘Sales Price: field integrity exception: UnitPrice (only one of unit price or total price may be specified)’ when cloning an opportunity?

There is a restriction that only the Unit Price or Total Price is present when creating an Opportunity or Quote line. The default clone configuration action for all fields is to clone them, so one of the field’s configuration actions must be set to clear the value. Try setting the configuration action for the Total Price(totalprice) field as ‘Leave Empty’, and leave the Unit Price(unitprice) configuration action as ‘Clone’.

March 4, 2017

How To: Load the Super Clone Copy page after the native record creation page

Copying child relationships from an existing record that acts as a template can save users a lot of time. A custom button can show the native record creation page, and then prompt the user to copy child records from an existing record when the new record is saved. For example, this could be used when creating a new opportunity, and after the opportunity is saved a page displays child relationship […]

March 4, 2017

How To: Reference the original record in a new cloned record

Super Clone Field values on the primary object can be set using URL parameters. First, change the configuration action for the field to ‘Set Value’. Then set a URL parameter that has the name of the field equaling a value. /apex/dh_superclone__superclone?rid={!Case.Id}&cfg=MyConfig&ParentId={!Case.Id} Super Clone Pro Field values on both the primary object and child objects can reference the record that they were cloned from . Super Clone Pro has a field […]

March 4, 2017

How To: Load the native edit page after cloning a record

Use the URL parameter ‘saveURL2’ to redirect the user to the native edit page. This parameter accepts a URL encoded string of the native edit page, and ‘newid’ will be replaced with the created record’s Id. The value of the saveURL2 parameter below ‘%2F%5Bnewid%5D%2Fe%3FretURL%3D%2F%5Bnewid%5D’ is a URL encoded string of ‘/[newid]/e?retURL=/[newid]’. On saving the new cloned record, the ‘[newid]’ value will be replaced with the new record id, and the […]

March 4, 2017

How To: Load a Salesforce or Visualforce page after saving on the Clone, Copy or Edit Super Clone pages

Add a URL parameter called ‘saveURL2’ to the custom button’s URL string. This parameter should equal a URL encoded text string that is the URL of the page you want to be redirect to after the operation. /apex/dh_superclone__superclone?rid={!YourObject.Id}&cfg=YourConfig&saveURL2=%2Fapex%2FMyOtherPage

March 4, 2017

How do I resolve the error that says I’m not being ‘recognized as a SysAdmin’ when trying to install the app?

This error can happen when trying to install an AppExchange package into an environment that you have logged into using Environment Hub’s SSO authentication. Try using the credentials of the Environment Hub org when a login is requested in the AppExchange’s install process.