Overview
The Large Data Optimizer (LDO) feature provides the ability to post/unpost more lines on the following source documents:
- Billings
- Payables
- Journal Entries
Note: For some LDO issues that might occur, the Troubleshooting Guide in our Knowledge Base includes a workaround. For more information, refer to the Troubleshooting Guide article.
If you want to have the Large Data Optimizer (LDO) feature enabled, submit a case to our Customer Support team. Once the LDO feature has been enabled, when you post/unpost any of the above source documents from the detail page or the list view, the records will be posted/unposted asynchronously. Additionally, when cloning a Journal Entry with lines or auto reversing a Journal Entry will also be performed asynchronously.
Note: The Large Data Optimizer feature is not applicable when posting via the API. The Post/Unpost Limits remain in place when posting through the API.
Do you want to learn more about:
- Additional Posting Statues
- Automated Job Results and Exception Report
- Purge to Reset Posting Status
- Using Calc Tax button
- Billing PDF Files
The table below provides information about limits when the Large Data Optimizer feature is enabled.
Note: This is a living table. It will continue to be updated as additional information about the Large Data Optimizer limits become available.
Billing | |
Description | Line Limit |
Billing Create & Post with or without Products | 100,000 |
Billing Line from Mass Add/Edit Rows | 100,000 |
Billing Create & Save PDF | 10,000 |
Billing Email PDF | 10,000 |
Billing Clone w/Lines | 1,000 |
Billing Header Level Posting (HLP) with AvaTax when the Calc Tax button is clicked Billing HLP with AvaTax and clicking Post (without clicking the Calc Tax button) |
1,000 7,500 |
Billing Header Level Posting (HLP) with Native Tax | 100,000 |
Billing Line Level Posting (LLP) with AvaTax when the Calc Tax button is clicked Billing LLP with AvaTax and clicking Post (without clicking the Calc Tax button) |
2,000 8,000 |
Billing Line Level Posting (LLP) with Native Tax when the Calc Tax button is clicked | 4,000 |
Billing Batch Post from List view with AvaTax | Up to 200 records |
Billing Batch Post from List view | 10,000 |
Billing Delete (newly created and has not been posted) | 24,000* |
Recurring Billing | |
Description | Line Limit |
Recurring Billing Lines | 20,000 |
Create Billing – Avalara AvaTax | 500 |
Payable | |
Description | Line Limit |
Payable Create & Post with or without Products | 100,000 |
Payable Line from Mass Add/Edit Rows | 100,000 |
Payable with using Advanced Line Manager (ALM) | 50,000 |
Payable Header Level Posting (HLP) with Native Tax | 100,000 |
Payable Line Level Posting (LLP) with Native Tax when the Calc Tax button is clicked | 4,000 |
Recurring Payable | |
Description | Line Limit |
Recurring Payable Lines | 20,000 |
Journal Entry | |
Description | Line Limit |
Journal Entry Create & Post | 100,000 |
Journal Entry Clone w/Lines | 100,000 |
Journal Entry Auto Reverse Entry | 100,000 |
Journal Entry Batch Post from List view | 100,000 |
Recurring Journal Entry | |
Description | Line Limit |
Recurring Journal Entry Lines | 20,000 |
Create Journal Entry | 20,000 |
*Due to Salesforce delete limitations, this 24,000 line limit may vary. For more information, refer to this Salesforce article.
Additional Posting StatusesOne of two additional Posting Statuses (Posting in Progress or Unposting in Progress) will display while the posting job is running in the background. Once the background job is completed, an Automated Job Results record will be created, which you can review for details, as necessary. For more information, refer to the Automated Job Results article.
Note: Click here to view the above image in full screen.
When you click Post or Unpost, the “Note: The Large Data Optimizer feature is enabled. Selected source records will be posted/unposted and updated accordingly” message will display in the Post intermediate screen. If you accidentally clicked Post/Unpost while the background job is processing, the “Posting/Unposting is in progress and once complete, the Posting Status for all selected records will be updated to Posted/Approved” message will display.
Note: If you have the Large Data Optimizer feature enabled, you should wait until posting is completed before attempting to perform another action on the record.
Important: If you have source documents with either of these two Posting Statuses (Posting in Progress or Unposting in Progress), the Accounting Period cannot be closed. An error message will display, which prevents closing while source documents are in these statuses.
Automated Job Results and Exceptions Report
If you have the Large Data Optimizer (LDO) feature enabled, an Automated Job Results record (Large Data Optimizer Post or Unpost for Billings, Payables, and/or Journal Entries) will be created from the automated jobs, as well as when you manually post one or more Billings, Payables, and/or Journal Entries. Additionally, if records fail to post/unpost, an Exceptions Report for LDO records will be available. You can view the Exceptions Report by clicking the hyperlink on the related Automated Job Results record.
Purge to reset Posting Status
If the asynchronous posting job is no longer running or has been aborted, and a record(s) is stuck in the “Posting in Progress or Unposting in Progress” status, you can run a purge to reset the Posting Status (move back to “Approved”) on the stuck record(s). For more information, refer to the Purge Source Documents stuck in interim Posting Status section of the Purge Data article.
Using Calc Tax button
If Avalara’s AvaTax is you tax method, and you are using Line Level Posting, when you click Calc Tax to calculate tax on a Billing, if there are more than 2,000 lines, an error message displays to indicate that you will need to post the record in order to see the tax line.
Note: For Header Level Posting (HLP), this is based upon more than 1,000 lines.
If AS Native Tax is your tax method, and you are using Line Level Posting, when you click Calc Tax on Billings/Payables with more than 4,000 lines, an error message will display to indicate that you cannot calculate tax with more than 4,000 lines.
Billing PDF Files
With the Large Data Optimizer feature enabled, you might encounter Billing PDF files with more than the line limit, which is 10,000 lines. If a Billing has more than 10,000 lines, the “Correction size XX,XXX exceeds maximum size of 10,000” message will display. The PDF file will not be created. Additionally, the size of the Billing PDF file will determine whether your customer receives the PDF as an attachment to the email or a clickable hyperlink. The size is determined by the below Salesforce Email Attachments setting, which you can access by clicking the Gear icon, selecting Setup, and then searching for Email Attachments.
If you select the second radio button, and the Billing PDF file is 3 MB or less, the customer will receive an actual PDF file attached to the email. However, if the second option is selected and the file exceeds 3 MB, the customer will receive a link in the email to click for viewing the file. If you select the third radio button, the customer will always receive the Billing PDF file as an attachment regardless of the file size.
Note: Click here to view the above image in full screen.
____________________
Winter '25 Release
If you have source documents with either of these two Posting Statuses (Posting in Progress or Unposting in Progress), the Accounting Period cannot be closed. An error message will display, which prevents closing while source documents are in these statuses.
____________________
Spring '24 Release
This article was new with the Spring '24 release.
Comments
0 comments
Please sign in to leave a comment.