New answers tagged

0

Note that sfdcfox is absolutely right about the fact that earlier DML transactions (from execute) have been fully committed so chunks of output from the batch may have already been saved to the database by the time you have execute fail for some reason. If your batch is updating existing objects, you're rather stuck unless you have a mechanism to undo your ...


1

Currently you are committing your work in the same transaction in which it is calculated. You don't specify, but I imagine it's something like start() { //zero out the Running Total field in all the records in some Summary-type object } execute() { //for each record in the querylocator //Add a number value in this record to the Running Total field ...


2

You can't rollback a fully completed transaction, which is why you get a SerializationException if you try to save a SavePoint. The start method, each call to execute, and the finish methods are all separate transactions. For example, with a batch size of 200, if you process 400 records, there are four total transactions: one start, two execute, and one ...


3

You can't upload files that large in Apex. Use lightning-file-upload to upload files up to 2GB in size.


0

You need to wait for the data to load. Something like this: <lightning-dual-listbox if:true={selectNotificationType} ...


0

I think your problem is similar to this one https://developer.salesforce.com/forums/?id=906F000000093fPIAQ so try this: go to Setup -> Manager Users -> Profiles, then select your profile type. From there, scroll all the way down to the Record Type Settings section and under the Standard Record Type Settings sub-section, Go to the Leads field and ensure ...


Top 50 recent answers are included