[Vikas Kumar]

Hi sushant,

ETL

Traditionally, ETL refers to the process of moving data from source systems into a data warehouse. The data is:

Extracted – copied from the source system to a staging area
Transformed – reformatted for the warehouse with business calculations applied
Loaded – copied from the staging area into the warehouse
How these steps are performed varies widely between warehouses based on requirements. Typically, however, data is temporarily stored in at least one set of staging tables as part of the process. The extract step might copy data to tables as quickly as possible in order to minimize time spent querying the source system, or the transform step might place data in tables that are copies of the warehouse tables for ease of loading (to enable partition swapping, for example), but the general process stays the same despite these variations.

ELT

ELT is a different way of looking at the tool approach to data movement. Instead of transforming the data before it’s written, ELT leverages the target system to do the transformation. The data is copied to the target and then transformed in place.

ELT makes sense when the target is a high-end data engine, such as a data appliance, Hadoop cluster, or cloud installation to name three examples.

 

[Vikas Kumar]

Hi Sushant ,

yes there are many tools similar to talend like

1.JitterBit

2.Pentaho

3.Skyvia

4.Apatar

5.ql.io

 

[Vikas Kumar]

Hi Sushant

Check out the Link for setup

https://trailhead.salesforce.com/en/lightning_connect/lightning_connect_setup

Hope it may help

[Vikas Kumar]

Hi Mohit,

To find out if a particular user has Edit access to a record, use the UserRecordAccess object. This object is available in API version 24.0 and later. You can use SOQL to query this object to find out if the user has edit access to the record in question.

SELECT RecordId, HasEditAccess FROM UserRecordAccess WHERE UserId = [single ID] AND RecordId = [single ID]

If you want to check a batch of records you can use

SELECT RecordId FROM UserRecordAccess WHERE UserId=:UserInfo.getUserId() AND HasReadAccess = true AND RecordId IN :allRecordIds LIMIT 200

Hope it may helps

[Vikas Kumar]

Hi Satyakam

Thanks for the Answer

[Vikas Kumar]

Hi Ajit,

Thanks for the Answer

[Vikas Kumar]

Hi Satyakam,

thanks for the answer

[Vikas Kumar]

Hi Satyakam,

thanks for the Link

[Vikas Kumar]

Hi Satyakam,

Thanks for the answer

[Vikas Kumar]

Hi Pranav ,

Thanks for describing the difference between database.query() and database.getQueryLocator()

• This reply was modified 6 years, 12 months ago by  Forcetalks.

[Vikas Kumar]

Hi Pranav,

Thanks for the Answer 🙂

 

[Vikas Kumar]

Hi kumar

Yes it differs, if the edition is Professional Edition. PE doesn't have Triggers.

UE- Unilimited Edition EE - Enterprise Edition

Old record loaded from database (or initialized for new inserts)
New record values overwrite old values
System Validation Rules (If inserting Opportunity Products, Custom Validation Rules will also fire in addition to System Validation Rules)
All Apex before triggers (EE / UE only)
Custom Validation Rules
Record saved to database (but not committed)
Record reloaded from database
All Apex after triggers (EE / UE only)
Assignment rules
Auto-response rules
Workflow rules
Processes
Escalation rules
Parent Rollup Summary Formula value updated (if present)
Database commit
Post-commit logic (sending email

[Vikas Kumar]

Hi Sushant

Trigger.new return the ordered list whereas trigger.newmap returns a map which is unordered

In other ways

Trigger.new
Returns a list of the new versions of the sObject records. Note that this sObject list is only available in insert and update triggers, and the records can only be modified in before triggers.

Trigger.NewMap
A map of IDs to the new versions of the sObject records, this map is only available in before update, after insert, and after update triggers.

hope it may help

• This reply was modified 5 years, 12 months ago by  Forcetalks.

[Vikas Kumar]

Hi sushant,

Triggers fire before workflows and

It is always suggestable to use the SF functionality in the first hand if it serves all our purposes. If the requirement or the functionality needs to handle some logic that the workflow rules cannot achieve, only then we should go for writing a custom trigger.

[Vikas Kumar]

hi sushant

there will be some correction in your code you need to specify your sobject  because it create some ambiguity becz

a.name can be either auto number or string so its create a situation which throws error. so if you wanted to update some fields of your object using batch you can call another batch class in ur class.

you can do something like this

global class SearchAndReplace implements Database.Batchable<sobject>{
global String Query;
global List<id>allObjIds ;
global SearchAndReplace(List<id>allObjectIds){
allObjIds=allObjectIds;
}
global Database.QueryLocator Start(Database.BatchableContext BC){
query='SELECT Id,Name FROM Account WHERE Id in:allObjIds';
return Database.getQueryLocator(query);
}
global void execute (Database.BatchableContext BC,List<Account>scope){
for(Account obj:scope){
obj.Name='Algoworks';
}
update scope;
}
global void finish (Database.BatchableContext BC){
SearchAndReplaceContact objc = new SearchAndReplaceContact(allObjIds);

}

another class get called inside above class

global class SearchAndReplaceContact implements Database.Batchable<sobject> {
global String Query;
global List<id>allObjIds ;
global SearchAndReplaceContact(List<id>allObjectIds){
allObjIds=allObjectIds;
}
global Database.QueryLocator Start(Database.BatchableContext BC){
query='SELECT Id,Name FROM Contact WHERE Id in:allObjIds';
return Database.getQueryLocator(query);
}
global void execute (Database.BatchableContext BC,List<Contact>scope){
for(Contact obj:scope){
obj.lastname='Algoworks';
}
update scope;
}
global void finish (Database.BatchableContext BC){
}

}

 

 

[Vikas Kumar]

Thanks Shekhar Gadewar!!

[Vikas Kumar]

Hi Sushant

This is the modified version of your code it works fine . you need to change sObject to Sobject ur code will work fine

global class TestBatch implements
Database.Batchable<Sobject>, Database.Stateful {
list<id> useridlist = new list<id>();
global TestBatch(list<id> idforlist){

useridlist=idforlist;
}

global Database.QueryLocator start(Database.BatchableContext bc) {
return Database.getQueryLocator('SELECT id,name FROM Sobject WHERE id IN :useridlist' );
}

global void execute(Database.BatchableContext bc, List<Sobject> scope){

for(Sobject a: scope)
{
a.put( 'name','Algo');
}
update scope;
}

global void finish(Database.BatchableContext bc){

}

}

Hope it Helps

[Vikas Kumar]

Thanks Pranav !!