• JohnRyder
  • NEWBIE
  • 0 Points
  • Member since 2013

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 4
    Questions
  • 4
    Replies

Hey Folks,

 

Is it possible to validate data in before insert trigger  instead of adding error?

 

Regards..

Hey,

 

I have object X AND Y.When a record is created in X,the trigger creates same record in Y also update,delete,undelete and viceversa.This cause infinite trigger for me.

 

I have seen a @future method in web and understood how its handle the problem but @future method works with static methods and " Methods with the future annotation cannot take sObjects or objects as arguments.

 

I pass trigger.new as argument and take it as a list to insert as a record in my method.In static @ future examples,I have seen that they pass trigger.new's id's as set<id> and do their job. @Future method accepts the sets as parameter.I don' t know the way of inserting a new record by passing trigger.new as id.I know that I have to pass it as an object.So I couldn't find the way of preventing infinite trigger.Can you help me with this?

 

Regards.

.........................................

Hi,I am new and prepearing  for DEV 401.

 

I have found some questions and wondering answers.

Q.1) Which statement is true regarding force.com domain name (3 answers):

A. It must be unique
B. It is usually the name of your company
C. it cannot be changed once it is registered to your organization
D. it cannot be mapped to your company's domain

 

 

 

Q.2) What is supported by the Force.com Data Loader? (3 answers)

A. perform a rollback of a transaction
B. insert records for two different objects in a single call
C. import data for custom objects
D. perform insert and update operations across a set of records
E. load more tha 50,000 records at a time

 

 

 

Thanks..

 

Greetings

Hey Folks,

 

Is it possible to validate data in before insert trigger  instead of adding error?

 

Regards..

Hey,

 

I have object X AND Y.When a record is created in X,the trigger creates same record in Y also update,delete,undelete and viceversa.This cause infinite trigger for me.

 

I have seen a @future method in web and understood how its handle the problem but @future method works with static methods and " Methods with the future annotation cannot take sObjects or objects as arguments.

 

I pass trigger.new as argument and take it as a list to insert as a record in my method.In static @ future examples,I have seen that they pass trigger.new's id's as set<id> and do their job. @Future method accepts the sets as parameter.I don' t know the way of inserting a new record by passing trigger.new as id.I know that I have to pass it as an object.So I couldn't find the way of preventing infinite trigger.Can you help me with this?

 

Regards.

.........................................

Hi,I am new and prepearing  for DEV 401.

 

I have found some questions and wondering answers.

Q.1) Which statement is true regarding force.com domain name (3 answers):

A. It must be unique
B. It is usually the name of your company
C. it cannot be changed once it is registered to your organization
D. it cannot be mapped to your company's domain

 

 

 

Q.2) What is supported by the Force.com Data Loader? (3 answers)

A. perform a rollback of a transaction
B. insert records for two different objects in a single call
C. import data for custom objects
D. perform insert and update operations across a set of records
E. load more tha 50,000 records at a time

 

 

 

Thanks..

 

Greetings