[Sourabh]

Hi Utsav,

It seems to be working fine for me. Can you please explain exactly what problem you are facing?

[Sourabh]

`Hi shubham hope it will work for you :-

-------- visualforce page --------------

<script>
function scriptcalling()
{
alert('I am here');
}
</script>

&nbsp;

-------- apex class --------------
public class calljavascript
{
public string callscript{get;set;}
public calljavascript()
{
callscript='<script> scriptcalling(); </script>';
}
}

• This reply was modified 8 years, 7 months ago by  Sourabh.
• This reply was modified 3 years, 5 months ago by  Forcetalks.
• This reply was modified 3 years, 5 months ago by  Forcetalks.
• This reply was modified 3 years, 5 months ago by  Forcetalks.
• This reply was modified 3 years, 5 months ago by  Forcetalks.
• This reply was modified 3 years, 5 months ago by  Forcetalks.
• This reply was modified 3 years, 5 months ago by  Forcetalks.

[Sourabh]

Hello Shubham,
The order of event execution is like this:-

Note:- Salesforce runs user-defined validation rules if multiline items were created, such as quote line items and opportunity line items.

1.Executes all before triggers.
2.Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
3.Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record is not saved and no further steps, such as after triggers and workflow rules, are taken.
4.Saves the record to the database, but doesn't commit yet.
5.Executes all after triggers.
6.Executes assignment rules.
7.Executes auto-response rules.
8.Executes workflow rules.
9.If there are workflow field updates, updates the record again.
10.If the record was updated with workflow field updates, fires before update triggers and after update triggers one more time (and only one more time), in addition to standard validations. Custom validation rules, duplicate rules, and escalation rules are not run again.
11.Executes processes.
12.If there are workflow flow triggers, executes the flows.

13.The Process Builder has superseded flow trigger workflow actions, formerly available in a pilot program. Organizations that are using flow trigger workflow actions can continue to create and edit them, but flow trigger workflow actions aren’t available for new organizations.

14.Executes escalation rules.
15.Executes entitlement rules.
16.If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
17.If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
18.Executes Criteria Based Sharing evaluation.
19.Commits all DML operations to the database.
20.Executes post-commit logic, such as sending email.

• This reply was modified 8 years, 8 months ago by  Sourabh.
• This reply was modified 8 years, 8 months ago by  Sourabh.

[Sourabh]

You can create a custom field named Email(text) and make it "UNIQUE" as well as "EXTERNAL ID". Now while importing Data through Data import wizard map the custom
Email field with the Email present in csv. This will remove the duplicacy problem.
The records having different Email will be inserted also the records having same Email will insert but only one record from different data having same Email will be inserted.

For example suppose you have 4 records which have same email then while importing only one record from all 4 will be insert on priority basis which will come first while importing data.

Hopefully it will resolve your issue.
Thanks