How to Refresh Page using Lightning Web Component

 eval("$A.get('e.force:refreshView').fire();");

Comments

Post a Comment

Popular posts from this blog

Adding a red asterisk to required fields using label in LWC

Image
I am trying to add a double or single asterisk to lightning: input tags in LWC, by using "required" tag inside the tag I am able to see the asterisk, but two issues with this are I have to show a red asterisk to some conditionally mandatory issues. Solution -  You can use  label-hidden  variant and put a label. <template> <label>Middle Name</label> <abbr title="required" class="slds-required">**</abbr> <lightning-input label="Middle Name" variant="label-hidden" aria-required="true" maxlength="80"></lightning-input> </template>
Read more

The Developer Console didn't set the DEVELOPER_LOG trace flag on your user. Having an active trace flag triggers debug logging. You have 1,978 MB of the maximum 1,000 MB of debug logs. Before you can edit trace flags, delete some debug logs.

1. In developer console, Select tab "Query Editor" at the bottom of the console. 2. Select check box "Use Tooling API". 3. Execute the below query: SELECT Id FROM ApexLog   4. Select All Rows. Click the first row and then press Shift button and click last row to select all the rows. Delete all rows using Delete button. https://help.salesforce.com/articleView?id=code_debug_log_delete.htm&type=5
Read more

Troubleshoot 'System.LimitException: Batchable instance is too big' error

If a batch apex class implements Database.Stateful, the instance state is stored in the database.  At this time we do a check against the size of the instance state and t he exception is thrown when the Apex Heap Size limit is exceeded. For synchronous Apex the heap size limit is 6 MB and for asynchronous Apex the limit is 12 MB.  This exception can obviously occur in a scenario where large collections are persistently maintained. Even if some chunks fail with this error, the batch job is completed. As per below lines in  Batch Apex Developer Guide   "If the first transaction succeeds but the second fails, the database updates made in the first transaction are not rolled back." To work around this issue, you can use the following steps: 1. Avoid using Database.Stateful 2. Reduce the amount of persistent data 3. Process less records per batch   In some cases Database.Stateful isn't being implemented or the steps above are not helpful in working around this e...
Read more