Troubleshooting Guide

Body

Overview

This guide is designed to help you diagnose and resolve common issues you may encounter. If your issue persists after trying the troubleshooting steps, contact Customer Support.

Note: This article is updated when issues are identified.

1099
Banking
Financial Master Data
Large Data Optimizer
Clone a Record
Revenues
Expenses
Software Upgrade/Install issues and resolution

1099

Winter ‘26 Release Issue

Is my 1099 filing is affected by this issue?

Determine which Category your org falls in:

Category A: If you're on Winter '26 version 3.362 or a later version like 3.363 and have created Cash Disbursements after upgrading then your 1099 File needs to be reviewed.
Next Steps.

Category B: If you're on a release prior to Winter '26 (for example, Winter '26 Preview 3.348, Summer '25 3.346, Spring '25 3.326, etc.) and you have Excess Golden Parachute Payments then you need to take steps to ensure your filing is correct.
Next Steps.

Category C: If you're on a release prior to Winter '26 (for example, Winter '26 Preview 3.348, Summer '25 3.346, Spring '25 3.326, etc.) and you don’t have any Excess Golden Parachute Payments then your Cash Disbursements and 1099 File are not affected.

Next steps for Category A

Navigate to Accounting Home > Create Entries> Expenses > Cash Disbursements.

Create a list view/s so you can run the update for Cash Disbursements with a filter Created Date greater or equal to the date of your upgrade. If you’re not sure, use 11/23/25 (this is the sandbox push date and the earliest you could have upgraded your production instance).

If you use both 1099-MISC and 1099-NEC, set up different list views to filter on each form type with the same Created Date filter.

Choose the list view to update, select all the Cash Disbursements, then click the Update 1099 Info button.

On the next screen, select the 1099 Form Type and the Form 1099 Box.
If you see a list index error, dismiss it.

Click Save.

Repeat steps 3, 4 and 5 for any other 1099 list views you need to update.

Click the Create 1099 File button to regenerate the report. Any previously missing Cash Disbursements should now be included.

Reconcile your 1099 report with your Cash Disbursements.

Next steps for Category B

If you want to stay on the same release and version, take the Excess Golden Parachute Payments out of the 1099-MISC export file and move them into the 1099-NEC file. These Excess Golden Parachute Payments should be reported on the Form 1099-NEC, in Box 3.

Reconcile your 1099 report with your Cash Disbursements.

Reconcile 2025 Cash Disbursements with 1099 File

Reconcile your 1099 report with your Cash Disbursements by creating a Salesforce report: App Launcher > Reports.
Click the New Report button.

Set Category to All, then search for Cash Disbursement Batches with Cash Disbursements.
Click Start Report.
Set Filters:
1. 1099 Year contains 2025
2. 1099 Vendor = Yes
Group Rows:
1. Ledger (or filter if you would like to focus on one at a time)
2. Vendor
Group Columns: Form1099 Box
Add Columns: Amount

Run the report: you should see each vendor, separated by ledger, with their 1099 amounts per box.
Compare the 1099 amounts from this report to the CSV export created from the Create 1099 File button on the Cash Disbursements list view.

Return to top

Banking

Problem: Unable to register Salt Edge - Error 137 received in sandbox or production environment.

Resolution: Install Spring '25 Preview 1 release (or higher).

Problem: Bank Reconciliation cannot complete because it is stuck in "Working" status

Resolution:

Click the Gear icon and select Developer Console.
Click the Query Editor tab. Then, copy/paste the following query into the textbox.
select id, name, ACCTSEED__STATUS__C
from AcctSeed__Bank_Reconciliation2__c
Where ACCTSEED__STATUS__C = 'Working'
Note: The ID is the Salesforce ID for the Bank Reconciliation.
Click the Debug drop-down list at the top, and then select Open Execute Anonymous Window.
Copy/paste the below query into the Execute Anonymous window.
AcctSeed__AS_Immediate_Event__e event = new AcctSeed__AS_Immediate_Event__e(
AcctSeed__Type__c = 'BANK_RECONCILIATION_CLEAR_ITEMS',
AcctSeed__Request_Id__c = 'a4O2s000000518uEAA',
AcctSeed__Payload__c = null
); EventBus.publish(event);
Change the Salesforce ID on the line "AcctSeed__Request_Id__c = 'a4O2s000000518uEAA'," to the record ID of the Bank Reconciliation that is stuck in "Working."
Click Execute. This will reset the Bank Reconciliation.
Return the Bank Reconciliation and refresh the page.

Note: If your org is on the Winter '25 release or higher, the likelihood of a Bank Reconciliation getting stuck in "Working" Status has been reduced.

Return to top

Financial Master Data

Problem: Accounting Period attempting to close gets stuck in "Close in Progress."

Resolution: Re-open the period and ensure all Ledgers have Default GL Accounts. Then, close again.

Large Data Optimizer

Problem: With the Large Data Optimizer feature enabled, a Billing Cash Receipt (BCR) and/or AP Disbursement (APD) record is stuck in Posting in Progress status when a Cash Receipt and/or Cash Disbursement is unapplied and applied at the same time.

Resolution: The Billing Cash Receipt (BCR) and/or AP Disbursement (APD) record that is stuck can be deleted and applied again.
Note: If your org is on the Winter '25 release or higher, this issue has been corrected.

Problem: With the Large Data Optimizer feature enabled, on a Refund Cash Receipt, when reviewing the Billing Cash Receipt (BCR) that applied the negative Cash Receipt to the Credit Memo, the Posting Status is Approved (it has not been posted).

Resolution:
In the Defaults GL Account screen, review the Cash Basis Accounting section to determine if the Unapplied Revenue GL Account and Unapplied Expense GL Account fields are blank. If these GL Accounts are blank, do the following:

1. Contact Customer Support to have the Large Data Optimizer feature temporary disabled.
2. Delete the Refund Cash Receipt that did not work correctly.
3. Add the Unapplied Revenue GL Account and Unapplied Expense GL Account in the Defaults GL Account screen.
4. Contact Customer Support to Re-enable the Large Data Optimizer feature.
5. Recreate the Refund Cash Receipt.

Return to top

Clone a Record

Problem: When attempting to clone a record such as a Billing, Payable, or Journal Entry, if the original record owner is inactive, the "Error: Operation with inactive user" message displays, and the record cannot be cloned.

Resolution: Change the original record owner to an active user. Then, try to clone the record.

Revenues

Problem: When attempting to clone a Billing with lines, "The user does not have enough rights to perform the Clone w/Lines operation on Billings or an Insufficient Privileges" error message displays.

Resolution: Review the Billing fields to Clone field set, and remove Owner from the field set. Then, clone the Billing with lines.

Expenses

Problem: You have a Payable for any amount, such as $1000.00. The Payable is paid (a Cash Disbursement was created). The Balance on the Payable and the related Cash Disbursement is 0.00. Then you need to do a return and ask the Vendor for a refund. You record this in Accounting Seed by cloning the Payable as a Credit Memo. The Balance on the Credit Memo is $-1000.00. Then, the Vendor issues a refund. What should be done in Accounting Seed?

Resolution:

Deactivate the “Cash_Disbursement_must_be_positive” validation rule on the Cash Disbursement.
On the Cash Disbursement page layout, click the Related Lists, and select the Wrench icon on the Invoices Applied To related list. Click Buttons, and select the New checkbox to add the New button.
Create a negative Cash Disbursement for $-1000.00.
On the negative Cash Disbursement, click the Applied To tab. Then, on the Invoices Applied To related list, click New (displays on the right side of the screen on the related list).
Search for and select the original Payable, and enter $-1000.00 in the Applied Amount field. Then, save the new AP Disbursement record. This will set the Balance on the Payable back to $1,000.00.
Display the Credit Memo, and click Apply/Unapply Credit Memo.
Apply the Credit Memo to the original Payable. This will set the Balance on the original Payable and the Credit Memo to $0.00.

Software Upgrade/Install issues and resolution

There are several reasons why an upgrade could fail. Some of them are listed below with the steps to resolve them.

Update Lightning Web Security setting

Error message: "LWC1503: Dynamic imports are not allowed." when trying to upgrade to the Summer '26 release.

Steps to resolve this error and then upgrade:

1. Click the Gear icon, select Setup and search for "session" in the Quick find box; click Session Settings.
2. On the page, look for the "Lightning Web Security" section and check the box "Use Lightning Web Security for Lightning web components and Aura components."
3. Scroll down and click Save.
4. Retry upgrading your org with the release.

Update your GL Account Mapping object to Allow Activities and Track Field History

Error Message: GL_Account_Mappings_with_Activities when trying to upgrade to the Spring '26 release.

No such relationship Activities on object GL_Account_Mapping__c

Resolution: Enable Activities and History tracking on the GL Account Mapping object. Steps:

1. Click the Gear icon and select Setup and click Object Manager.
2. Type "Mapping" in the Quick Find search box.
3. Click GL Account Mapping in the search results.
4. On Details, click Edit.
5. Scroll down to the Optional Features section.
6. Check both check-boxes for Allow Activities and Track Field History.
7. Click Save.

Retry upgrading your org with the release.

Delete your Custom Automated Job Results tab (upgrade recreates it)

Error/Error Message: CustomTab(Automated_Job_Results__c)

Unmanaged custom object tab already exists, package upgrade cannot create another tab
Automated_Job_Results__c:
Unmanaged custom object tab already exists, package upgrade cannot create another tab

Resolution:
A custom tab is preventing the upgrade, since the package now has the same tab. To delete the tab, follow these steps, then try to reinstall the release:

1. Click the Gear icon and select Setup.
2. Type "Tabs" in the Quick Find search box.
3. Click Tabs in the search results.
4. Find Automated Job Results.
5. Click Del.

Retry upgrading your org with the release.

Error/Error Message: Deployment Failure

AcctSeed.ContentDocumentLink: execution of AfterInsert caused by: System.NullPointerException: Attempt to de-reference a null object Class.AcctSeed.ContentDocumentLinkActions.afterInsertHandler: line 5, column 1 Trigger.AcctSeed.ContentDocumentLink: line 3, column 1
image_1_1 contentassets/image_1_1.asset AcctSeed.ContentDocumentLink: execution of AfterInsert caused by: System.NullPointerException: Attempt to de-reference a null object Class.AcctSeed.ContentDocumentLinkActions.afterInsertHandler: line 5, column 1 Trigger.AcctSeed.ContentDocumentLink: line 3, column 1
image_1_11 contentassets/image_1_11.asset AcctSeed.ContentDocumentLink: execution of AfterInsert caused by: System.NullPointerException: Attempt to de-reference a null object Class.AcctSeed.ContentDocumentLinkActions.afterInsertHandler: line 5, column 1 Trigger.AcctSeed.ContentDocumentLink: line 3, column 1

Resolution:

Click the Gear icon, and select Setup.
From the Quick Find textbox, enter Salesforce Files.
Select General Settings. Then, click Edit.
Select the Skip triggers execution when deploying asset files checkbox.
Click Save.

Error/Error Message: Transaction__c.Description__c

The formula references fields across 16 unique relationships while only 15 are allowed. Please contact support at http://salesforce.com for more assistance.

Resolution:

Review custom formula fields, validation rules, workflow rules, etc. on the transaction object and remove one or more (not enough to disable).
Contact Salesforce support to request extending the limit (up to 20 are allowed).

Error/Error Message: Ledger__c.AP_Payment_Processor__c

You reached the maximum number of allowed active filtered lookups (5) on Ledger.

Resolution: Submit a support case to Salesforce to increase the number of active lookup filters. Refer to this Salesforce article for more information.

Error/Error Message: Account.Default_Payment_Processor__c

You reached the maximum number of allowed active filtered lookups (5) on Account.

Resolution: Submit a support case to Salesforce to increase the number of active lookup filters. Refer to this Salesforce article for more information.

Error/Error Message: Ineligible Upgrade

This package requires that a newer version of a dependent package be installed before the upgrade can proceed: Accounting Seed Financial Suite, Version Summer '23 Preview 1 3.154.

Resolution: This error can occur for the following reasons:

Your org is already upgraded to the current release
Your org edition is ineligible for installs

Error/Error Message: AP_Aging_History_with_Activities

No such relationship Activities on object AP_Aging_History__c

Resolution: Your current release is prior to Spring '23. There are specific configuration changes that will need to be made in your org before upgrading. Click here to view the related article.

Error/Error Message: Uncleared_Bank_Reconciliation_Line_With_Activities

No such relationship Activities on object Uncleared_Bank_Reconciliation_Line__c

Resolution: Your current release is prior to Spring '23. There are specific configuration changes that will need to be made in your org before upgrading. Click here to view the related article.

Error/Error Message: Accounting_Reports/Exceptions_AP_Aging_History_Deletion_Job

Invalid report type

Resolution: Your current release is prior to Spring '23. There are specific configuration changes that will need to be made in your org before upgrading. Click here to view the related article.

Error/Error Message: Accounting_Reports/Exceptions_Uncleared_Bank_Rec_Line_Deletion_Job

Invalid report type

Resolution: Your current release is prior to Spring '23. There are specific configuration changes that will need to be made in your org before upgrading. Click here to view the related article.

Error/Error Message: Accounting_Reports/Exceptions_Merchant_Download_Job

Invalid report type

Resolution: Your current release is prior to Spring '23. There are specific configuration changes that will need to be made in your org before upgrading. Click here to view the related article.

Error/Error Message: Billing_c.Payment_Processor_c

You have reached the maximum number of allowed active filtered lookups (5) on Billing.

Resolution: Submit a support case to Salesforce to increase the number of active lookup filters. Refer to this Salesforce article for more information.

Error/Error Message: Ineligible Upgrade

This package requires that a newer version of a dependent package be installed before the upgrade can proceed: Accounting Seed Financial Suite, Version Summer '23

Resolution: In most cases involving Orders & Inventory, you are required to upgrade your Financial Suite package to the latest release before proceeding with the upgrade to the latest version of the Orders & Inventory release.

Error/Error Message: No clean data columns available for custom fields

(Error Title and Error Message are the same)

Resolution: For more information, click here to access the Salesforce help page.

Problem: UnclassifiedError

Salesforce has blocked this package upgrade because the new package version removes some Apex code that one or more Visualforce pages or global Visualforce components need in order to function. Please contact your partner with this error information. Provide these component names to your partner. Visualforce Pages: OpportunitySalesAvaTax, AccountingSetttingsAddressValidator.

Resolution: You need to upgrade to Spring '23 before you can upgrade to a newer release. There are specific configuration changes that will need to be made in your org before upgrading. Click here to view the related article.

Error/Error Message: Fixed_Asset_Record_Home

Component [force:relatedListSingleContainer] attribute [relatedListApiName]: Could not find related list [Histories] for entity [AcctSeed__Fixed_Asset__c]

Resolution: You must enable history on the Fixed Asset object.

Error/Error Message: Unexpected Error

AcctSeed.PostInstallActions.PostInstallException: Last failure block: Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []Class.AcctSeed.SFDCSecurityUtils.ProxyDMLHelper.updateByProxy: line 747, column 1Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 534, column 1Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 529, column 1Class.AcctSeed.PostInstallActions.setAutoPostSourceDocsFields: line 149, column 1Class.AcctSeed.PostInstallActions.onInstall: line 86, column 1Class.AcctSeed.PostInstallActions.setAutoPostSourceDocsFields: line 152, column 1Class.AcctSeed.PostInstallActions.onInstall: line 86, column 1Caused byClass.AcctSeed.SFDCSecurityUtils.ProxyDMLHelper.updateByProxy: line 747, column 1Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 534, column 1Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 529, column 1Class.AcctSeed.PostInstallActions.setAutoPostSourceDocsFields: line 149, column 1Class.AcctSeed.PostInstallActions.onInstall: line 86, column 1

Resolution: Your username does not have access permission to the Accounting Settings object.

Error/Error Message: Deployment Failure

Dependent class is invalid and needs recompilation: Class AcctSeed.RecurringPayableSchedulableBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountPayableFromRecrAccountPayable : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountPayablePostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteService : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractSourceRecordPostBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.TestDataSuite : Dependent class is invalid and needs recompilation: Class AcctSeed.BillingPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxService : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxHelper : Variable does not exist: Line_Origin_Address_Override__r

Resolution: For more information, click here to view the Salesforce help page.

Error/Error Message: Deployment Failure

Dependent class is invalid and needs recompilation: Class AcctSeed.TestDataSuite : Dependent class is invalid and needs recompilation: Class AcctSeed.BillingPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxService : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxHelper : Variable does not exist: Line_Origin_Address_Override__r

Resolution: For more information, click here to view the Salesforce help page.

Error/Error Message: Deployment Failure

Dependent class is invalid and needs recompilation: Class AcctSeed.SObjectActionsTest : Dependent class is invalid and needs recompilation: Class AcctSeed.LedgerActions : Dependent class is invalid and needs recompilation: Class AcctSeed.SObjectActions : Dependent class is invalid and needs recompilation: Class AcctSeed.BankTransactionsHelper : Dependent class is invalid and needs recompilation: Class AcctSeed.ImportFileWizardHelper : Dependent class is invalid and needs recompilation: Class AcctSeed.GLAccountMappingActions : Dependent class is invalid and needs recompilation: Class AcctSeed.BankSettingsHelper : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingSettingsHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingSettingsActions : Dependent class is invalid and needs recompilation: Class AcctSeed.DomainUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodOpenCloseUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodDeleteEarningsCubesBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseBatchProcessor : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseRetainedEarnings : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseBillingAging : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseAPAging : Dependent class is invalid and needs recompilation: Class AcctSeed.AgingHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriod : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodActions : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteService : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractSourceRecordPostBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.TestDataSuite : Dependent class is invalid and needs recompilation: Class AcctSeed.BillingPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxService : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxHelper : Variable does not exist: Line_Origin_Address_Override__r

Resolution: For more information, click here to view the Salesforce help page.

Error/Error Message: Deployment Failure

Dependent class is invalid and needs recompilation: Class AcctSeed.DomainUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodOpenCloseUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodDeleteEarningsCubesBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseBatchProcessor : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseRetainedEarnings : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseBillingAging : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseAPAging : Dependent class is invalid and needs recompilation: Class AcctSeed.AgingHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriod : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodActions : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteService : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractSourceRecordPostBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.TestDataSuite : Dependent class is invalid and needs recompilation: Class AcctSeed.BillingPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxService : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxHelper : Variable does not exist: Line_Origin_Address_Override__r

Resolution: For more information, click here to view the Salesforce help page.

Error/Error Message: Deployment Failure

Dependent class is invalid and needs recompilation: Class AcctSeed.MultiCurrencyHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.LedgerHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.LedgerActions : Dependent class is invalid and needs recompilation: Class AcctSeed.SObjectActions : Dependent class is invalid and needs recompilation: Class AcctSeed.BankTransactionsHelper : Dependent class is invalid and needs recompilation: Class AcctSeed.ImportFileWizardHelper : Dependent class is invalid and needs recompilation: Class AcctSeed.GLAccountMappingActions : Dependent class is invalid and needs recompilation: Class AcctSeed.BankSettingsHelper : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingSettingsHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingSettingsActions : Dependent class is invalid and needs recompilation: Class AcctSeed.DomainUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodOpenCloseUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodDeleteEarningsCubesBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseBatchProcessor : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseRetainedEarnings : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseBillingAging : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodCloseAPAging : Dependent class is invalid and needs recompilation: Class AcctSeed.AgingHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriod : Dependent class is invalid and needs recompilation: Class AcctSeed.AccountingPeriodActions : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteService : Dependent class is invalid and needs recompilation: Class AcctSeed.AbstractSourceRecordPostBatch : Dependent class is invalid and needs recompilation: Class AcctSeed.FinancialSuiteUtils : Dependent class is invalid and needs recompilation: Class AcctSeed.TestDataSuite : Dependent class is invalid and needs recompilation: Class AcctSeed.BillingPostHandler : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxService : Dependent class is invalid and needs recompilation: Class AcctSeed.AvaTaxHelper : Variable does not exist: Line_Origin_Address_Override__r

Resolution: For more information, click here to view the Salesforce help page.

Error/Error Message: Deployment Failure (Sandbox)

AcctSeed.PostInstallActions.PostInstallException: Last failure block: Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: [] Class.AcctSeed.SFDCSecurityUtils.ProxyDMLHelper.updateByProxy: line 747, column 1 Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 534, column 1 Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 529, column 1 Class.AcctSeed.PostInstallActions.setAutoPostSourceDocsFields: line 149, column 1 Class.AcctSeed.PostInstallActions.onInstall: line 86, column 1 Class.AcctSeed.PostInstallActions.setAutoPostSourceDocsFields: line 152, column 1 Class.AcctSeed.PostInstallActions.onInstall: line 86, column 1 Caused by Class.AcctSeed.SFDCSecurityUtils.ProxyDMLHelper.updateByProxy: line 747, column 1 Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 534, column 1 Class.AcctSeed.SFDCSecurityUtils.updateProxy: line 529, column 1 Class.AcctSeed.PostInstallActions.setAutoPostSourceDocsFields: line 149, column 1 Class.AcctSeed.PostInstallActions.onInstall: line 86, column 1

Resolution: The error is with updating the Auto Post Source Doc fields on the Accounting Settings record. The specific error is usually when there is no actual record, in this case no Accounting Settings record. This happens with partial or developer sandboxes where the Accounting Settings record has not been copied over from the main production org. To prevent this issue, ensure that the Accounting Settings object is included when creating a partial copy sandbox. For a developer sandbox, the best solution would be to uninstall and re-install the package.

Error/Error Message: Deployment Failure

An unexpected error occurred. Please include this ErrorId if you contact support: 1219498375-289540 (-342026457)

Resolution: Salesforce error, contact Salesforce support for assistance.

Error/Error Message: Deployment Failure

The data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our <A href="{0}" title="support{1}">support</a> page.

Resolution: Salesforce error, contact Salesforce support for assistance.

Error/Error Message: Deployment Failure

The following feature must be enabled by the subscriber to proceed with the upgrade: EnhancedEmail. Not all features are available in all Salesforce Editions. To determine if this feature is included in an edition, for the feature in the online help and review the documentation. The subscriber may need to upgrade their Salesforce Edition or purchase the feature as an add-on (if available).

Resolution: Salesforce error, contact Salesforce support for assistance.

Error/Error Message: Data Storage Limits Exceeded

Your company currently has exceeded its data storage limits including an extra overflow buffer. Per our terms and conditions, we cannot permit additional data creation within our system until your company first reduces its current data storage. Please contact your company's Salesforce: The Customer Company administrator to resolve this. We apologize for any inconvenience this may cause.

Resolution: Contact Salesforce to address data storage limits.

Error/Error Message: Labor_Cost_Rate_Record_Home

Component [force:relatedListSingleContainer] attribute [relatedListApiName]: Could not find related list [OpenActivities] for entity [AcctSeed__Cost_Rates__c]

Resolution: Turn on Track Activities for this field.

Error/Error Message: Project_Record_Home

Component [force:relatedListSingleContainer] attribute [relatedListApiName]: Could not find related list [OpenActivities] for entity [AcctSeed__Project__c]

Resolution: Turn on Track Activities for this field.

Return to top

Title

Troubleshooting Guide

URL Name

1083031607