function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
gbrowngbrown 

Deployment Error - CancelEdit is not a standard action and cannot be overridden.

I am receiving this error on a custom object that is preventing the validation from passing.

 

Any ideas what could be done to fix this?

 

 

Type - Custom Object Definition

Problem - CancelEdit is not a standard action and cannot be overridden.

 

Best Answer chosen by Admin (Salesforce Developers) 
Rakesh BoddepalliRakesh Boddepalli

I was able to fix this issue.

If you are using Changesets then I'm not sure about the solution in that case.

 

As part of winter '14 salesforce.com had introduced 3 new action overrides

 

CancelEdit

Follow

SaveEdit

 

You need to remove all these from the  object's XML file . if you are porting from Winter '14 org to Summer '13 org.

 

Once you retrieve the package

go to the Objects folder and edit the object file with notepad and remove the sections

 

<actionOverrides>
<actionName>CancelEdit</actionName>
<type>Default</type>
</actionOverrides>

 

<actionOverrides>
<actionName>Follow</actionName>
<type>Default</type>
</actionOverrides>

 

<actionOverrides>
<actionName>SaveEdit</actionName>
<type>Default</type>
</actionOverrides>

 

Please mark it as solution if this fixed your issue.

All Answers

marioluiscitadinmarioluiscitadin

Hi

 

I am getting the same issue.

 

I guess action "cancelEdit" was created ion Winter 14 release.And it is occurring because that our Sandbox is in Winter 14 and Production org is not in Winter 14 yet.

 

If you are on eclipse, remove 

<actionOverrides>
<actionName>CancelEdit</actionName>
<type>Default</type>
</actionOverrides>

 

from Object metadata.

 

 

Best Regards,

 

 
Kevin DesaiKevin Desai

Same error! No luck yet! 
Rakesh BoddepalliRakesh Boddepalli

I was able to fix this issue.

If you are using Changesets then I'm not sure about the solution in that case.

 

As part of winter '14 salesforce.com had introduced 3 new action overrides

 

CancelEdit

Follow

SaveEdit

 

You need to remove all these from the  object's XML file . if you are porting from Winter '14 org to Summer '13 org.

 

Once you retrieve the package

go to the Objects folder and edit the object file with notepad and remove the sections

 

<actionOverrides>
<actionName>CancelEdit</actionName>
<type>Default</type>
</actionOverrides>

 

<actionOverrides>
<actionName>Follow</actionName>
<type>Default</type>
</actionOverrides>

 

<actionOverrides>
<actionName>SaveEdit</actionName>
<type>Default</type>
</actionOverrides>

 

Please mark it as solution if this fixed your issue.

This was selected as the best answer
NewLenDevNewLenDev

We tried this fix but after we ran the Mavensmate to update the DB from the server, the deleted data was placed back into the script. Is there some other step that we missed that would not allow saving the change?
Rakesh BoddepalliRakesh Boddepalli

oh! Not sure about the functionality of the mavensmate.

 

But, I was using the Force.com Ant deployment tool and was successfully able to port the package after the removing those XML attribs from the objects file.
gbrowngbrown

I had the same problem as NewLenDev, after I deployed with the FDC IDE it pulled the old data back in...

 
comictommycomictommy

I am using the Change Sets and getting the same problem.  I am not able to edi tthe XML data.
gbrowngbrown
Are you getting the custom object definition problem that I was
getting? If so, a quick work around...

Create the object in production, leave it out of the change set and
everything else will deploy.

Sent from my iPhone
comictommycomictommy
Nice idea. I will try it tonight. 
gbrowngbrown
Good luck

Sent from my iPhone
ryanhca123ryanhca123

Right... the IDE will pull the server back in after saving. So you need to make the change while in offline mode and then push it to prod.
cloudlesscloudless

This is reported on the known issues page - please flag that "this issue affects me"

 

https://success.salesforce.com/issues_view?id=a1p30000000T08NAAS
comictommycomictommy
Thank you Gbrown! This worked perfectly today. I am deploying another change set before the upgrade to Winter 14 so I will use the same process then! Thank you! Thank you!
gbrowngbrown

ComicTommy - glad the suggestion worked for you as well.  Click kudos next to my name :)

 
petyrgcpetyrgc

I tried the solution of creating the object in our PROD instance, leaving out the objects in the Change set and trying to deploy but did not work. I got a new set of error messages. Failure Message: "System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY