Record Clone — Common Issues & Resolutions
Licensed User Count Exceeded
Verify whether the error is genuinely a licensing threshold breach by checking from two locations.
-
Record Clone Licensing is based on active users within your environment, specifically all System Users that meet the following criteria:
• Enabled (not disabled)
• Access Mode is not "Support User"
You can identify these users using the following FetchXML query against the systemuser entity.
<fetch> <entity name="systemuser"> <filter> <condition attribute="isdisabled" operator="eq" value="1" /> <condition attribute="accessmode" operator="ne" value="3" /> </filter> </entity> </fetch> -
Verify the count recognised by Record Clone itself.
Confirm the Actual user value shown here. -
If you are looking to reduce your licensed user count, one option worth exploring is restricting environment access via Security Groups.
This allows you to control which users in your tenant can access the environment, effectively limiting the active user count that licensing considers. You can find more details on this approach below
https://learn.microsoft.com/en-us/power-platform/admin/control-user-access
"Error Cloning Record" during the Clone Process
The root cause is one of two things: insufficient permissions on the logged-in user, or a conflicting synchronous plugin or workflow triggered by a field on the cloned entity.
Step 1 — Check for a permissions error
Search the trace log for the text permissions. If found, the error message will reference the specific missing privilege. Resolve it by updating the user's security role.
Step 2 — Isolate a conflicting field or relationship
If no permission reference is found, a custom plugin or sync workflow is likely the culprit. Use binary elimination to pinpoint it.
Isolation sequence
"Clone Button Access" error on Clone button click
Download & Install the latest version from the Record Clone from the link below
https://www.work365apps.com/record-clone-release-notes
Product bundles not Cloned or Cloned incorrectly
Cloning of product bundles is not supported in the current version of Record Clone.
There is no workaround at this time — bundle records must be recreated manually on the cloned entity.
Plugin error on cloning records with Retired Product Line Items
Cloning opportunities, quotes, orders, or invoices that contain line items associated with a retired product will result in a plugin error.
The current version does not support this scenario.
Before cloning, ensure all line item products are in an active state.
Attachment files corrupted on the cloned record
Record Clone only supports cloning of attachments stored directly within CRM (i.e. attached to a Note record).
Attachments stored in SharePoint, Azure Storage, or any other external location are not supported and will not clone correctly.
What doesn't: Cloning attachments backed by SharePoint Document Locations or Azure-hosted files.
Reading Plugin Trace Logs
DiagnosticTrace logs are the primary diagnostic tool for all Record Clone failures. Follow these steps to locate and read them.
Enable trace logging. Navigate to Settings › Administration › System Settings and set Plugin Trace Logging to All or Exception.
System Administrator role required.
If logging was previously off, you must re-run the clone operation to generate new log entries.
Run an Advanced Find against the Plug-in Trace Logs entity. Filter where Type Name contains RecordClone.
Sort by Executing Start Time (descending) to surface the most recent log entries first.
Open the relevant record and locate the error detail in the Message Block field. Scroll to the bottom of the message block for the most specific error text.
