Ajit Kumar
IndividualForum Replies Created
-
You have to create a wrapper class for that, and the variables in the fields must be same as the objects in the JSON, and after that use this syntax.
list<WrapperClass>responseList = (WrapperClass)System.JSON.deserialize(jsonResponse,MailgunParser.class)
If you provide your code then I can provide you a complete solution.
-
Normal puzzle quesions that somebody thinks is tricky can post here, So that somebody else can answer it
-
You can go to
Permission set >> Manage Assignement>> Select Users >> Assign to assign permission set to multiple users.Take help from this link :
-
We can not delete custom object using apex, bit if you want to delete a custom object we have to use Meta Data api.
-
Hi Hazel
There are two ways that you can suspend a batch job.
- go to setup > Search apex jobs and click abort on the desired batch job
2.
for(CronTrigger ct : [SELECT Id, CronJobDetail.Name, CronJobDetail.JobType
FROM CronTrigger
WHERE CronJobDetail.Name like 'Work Order%']){// abort the job, try/catch because the job might not exist
// if it's being aborted manually or from another execution
try{
system.abortJob(ct.id);
} catch (exception e) {}
} -
You can use the lightning app directly by exposing your lightning component to a Visualforce page.
You can follow this link
http://www.forcewizard.com/blog/expose-your-lightning-components-visualforce-page
-
Refer this link it could help you a lot :
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_query.htm
-
Thanx abhinav but at some stage offset pagination will also fail when there is large data, But after some research i found a solution in which I am using java script remoting, and in this no view state error is coming.
-
Salesforce does not provide any standard feature for history tracking on opportunity line items but through using a trigger we can get to this solution
trigger OpportunityProucttRACKING on Opportunity (After insert, After update) {
for(Opportunity t:trigger.new){
List<String> NewList= new List<String>();
if (t.HasOpportunityLineItem == true)
{
for(OpportunityLineItem OpLine: [SELECT CreatedBy.Name, Quantity, TotalPrice, LastModifiedDate, PriceBookEntry.Name, UnitPrice, ID FROM OpportunityLineItem WHERE OpportunityId =:t.Id] ) {
NewList.add(OpLine.CreatedBy.Name);
NewList.add(' on');
String str1 = '' + opLine.lastModifiedDate;
NewList.add(str1);
}}
}
} -
Merging two organisations is always a painful process, and you should be weary of couple of things and plan for them accordingly.
Object metadata - is it exactly the same? Especially around the fields that have the same name but have different semantics in each org.
Validation/Workflow rules - Does a workflow rule in one org conflict with another workflow rule in the other org.
Division is used to segment your data into different logical groups. The user will then have access to the data that belongs to the division that he is assigned to. If you do not have an existing role hierarchy to contend with, Divisions should work fine.
The following caveats apply to division though:
It is not recommended if data is shared across divisions
Shared accounts and shared opps cannot be assigned to more than one division
Each user can have only one default division. if you have numerous users that would own data in several divisions then divisions are not recommended.
Also, if security is a big concern, then you are out of luck, because users can always view records in all divisions. They do not provide the type of security that role hierarchy provides. Most importantly, if the Division field is added to their page layout, they can create records in other divisions.
Orphan records are automatically assigned to your "global" division
Records w/o parents that are created via the Force.com API are the given the default division of the API user who created them.
If you wish to use the Quotes feature in Salesforce.com, Divisions cannot be enabled. If Divisions was previously enabled, Quotes cannot be enabled. -
Thanx Abhinav, but when i performed the insert operation in my code then it was throwing the error that DML not allowed.
-
http://salesforce.stackexchange.com/questions/68171/running-metadata-api-in-apex-as-a-specific-user
Have a look on this link, hoping it will help you.
-
{!requireScript("/soap/ajax/20.0/connection.js")}
{!requireScript("/soap/ajax/20.0/apex.js")}retStr = sforce.apex.execute("Testapex", "method()",{});
the class which you are calling must be a global class
global Testapex{
global void method(){
}
} -
Please have a look into this link
https://help.salesforce.com/HTViewSolution?id=000182414&language=en_US