You need to sign in to do that
Don't have an account?

How can I active a trigger
I did a trigger on enterprise version sf with eclipse. which can't edit trigger on sfdc.
I can upload this trigger from eclipse to sfdc. but I can't upload the active config. I config the trigger.xml to <active>true<active> and upload it. but it doesn't work. In server the trigger is still deactive.
How can I active the trigger?
I can upload this trigger from eclipse to sfdc. but I can't upload the active config. I config the trigger.xml to <active>true<active> and upload it. but it doesn't work. In server the trigger is still deactive.
How can I active the trigger?
I was also facing the issue. what I did was went to the setup and then the Sobject where the trigger was made and then select the Active check box on edit and then save it. and then before deploying sync with the server. and then upload it... it helped for me... I think it will also help you.
Thanks and regards
Pallav
It's so bad......
you must have developed the trigger in the some dev or sandbox instance and then you are trying to deploy it on the enterprise instance. I was telling you to perform the steps in the dev or sandbox instance and then deploy the deactivated trigger in the enterprise instance.
Thanks and regards
pallav
Anyhow, in the Eclipse IDE, there should be an XML file that is associated with your trigger. If you open it, you will see a place where you can change active from false to true.
That should do it for you.
Mike
The only way to do it is by changing the XML in Eclipse prior to deploying it.
I don't have permission to add/edit any triggers. And my role is administrator.
I had set <active>true</active> in eclipse but always failed to upload it to server.
What error are you getting?
MikeD13 wrote:
If he can't edit the trigger through the Salesforce interface, he can't check the box. Salesforce graced all of us measly Enterprise users with the power to use Apex but not edit/delete anythiung through the Salesforce UI. I guess they had to leave something to the just Unlimited users.
The only way to do it is by changing the XML in Eclipse prior to deploying it.
That doesn't work either. I'm using enterprise and I can deactivate triggers in the sandbox by updating the xml, works fine there. But then deploying the trigger to production will not deactivate it, Eclipse, Ant, nothing does it. The only way I've been able to "deactivate" a trigger in production is to comment out the entire trigger body. Salesforce please fix this!
Mark
I'm going to keep asking this until someone in the know answers...
SALESFORCE: WHY CAN'T WE EDIT TRIGGERS/CLASSES THROUGH YOUR INTERFACE!?!?!
Message Edited by MikeD13 on 03-19-2008 01:31 PM
futhermore, this whole test-coverage thing is a bit shady. i run the tests in eclipse - 94% - great. I try to deploy to prod, and it tells me that my test coverage is only 14%. this is painful.
any insight is most welcome...
chris
1) I am rarely successfuly when dropping/deactivating triggers through these interfaces
2) Salesforce doesn't even support either of these products
This has been submitted as an idea in the Idea Exchange but it hardly has any points (Log in and promote it so they fix this issue.).
http://ideas.salesforce.com/article/show/100376/Allow_deactivation_of_Apex_triggers_in_production
It still irks me that we even need to ask for this feature... this should be a given. If you need a trigger deactivated/deleted due to some issue, the last thing you want to have to do is load up an IDE, make changes and then deploy it. Why not just let us uncheck the IsActive box?!?! Is it really that hard??!
There isn't a way to deactivate a trigger in production via any tool or the UI. Once you deploy, you have a permanently active trigger to deal with and that's a huge problem.
Mark
Do you mean this link?
http://ideas.salesforce.com/article/show/100376/Allow_deactivation_of_Apex_triggers_in_production
I open the link you provided, but still can't understand how to active it. I can't understand his meaning. Can you describe it in normal sentence?
Message Edited by Kunlun on 03-26-2008 05:02 PM
Why can't I create, edit or delete Apex triggers or classes in Salesforce?
Only Developer Edition, Sandbox, and Trial organizations have the ability to create, edit, and delete Apex classes and triggers directly in the Salesforce user interface. Unlimited Edition and Enterprise Edition production organizations can execute Apex and can view Apex in the user interface, but modifying Apex in the user interface is not allowed.
The Apex classes and triggers should first be written in a Developer Edition, Sandbox, or Trial organization along with the appropriate test methods that test at least 1% of triggers and 75% of classes. To deploy Apex into a production organization, a user with the Author Apex permission must deploy the triggers and classes using either the compileAndTest() or deploy() Metadata API methods which can be accessed with either the Apex Development Tool based on Apache ANT or the Force.com IDE based on Eclipse.
Both of these tools are available by going to Setup | Develop | Tools. For more information about Apex, please see the Apex Developer's Guide at http://www.salesforce.com/us/developer/docs/apexcode/index.htm
Why Cant I see the New Button in Apex Code Trigger section?
Sometimes, a customer might ask why they can not see the NEW button in Apex Code trigger section in Live Production.
You can add, edit or delete Apex using the Salesforce user interface only in a Developer Edition or sandbox organization.
To activate the Trigger Function in live production environment, you will need to use either the Salesforce ANT Tool or Apex Toolkit for Eclipse to deploy.
More Deployment instructions are in the attached Apex Developer's Guide
For the latest Apex Developer Guide go to http://www.salesforce.com/us/developer/docs/apexcode/salesforce_apex_language_reference.pdf
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------I tried eclipse to upload Apex code, but I failed again and again. I only can upload it with command out all code.
This kind of problem had involved me into a deep trap. I had spent too much time on that. It sucks so much.