Salesforce Administration
Resolving "Access to entity 'AggregateResult' denied" Error for Asperato Repeat Payment Job
Some Salesforce organisations may encounter the error message "Access to entity 'AggregateResult' denied: Entity is not api accessible" when the daily Asperato Repeat Payment job runs. This typically occurs due to insufficient permissions on the user account running the job.
- In Salesforce, navigate to Setup > Environments > Jobs > Scheduled Jobs.
- Locate the Asperato Repeat Payment job. Note its start time.
- Delete the job.
- Navigate to Setup > Custom Code > Apex Classes.
- Click the Schedule Apex button.
- Configure the new job as follows:
- Job Name: Asperato Repeat Payment (recommended)
- Apex Class: Click the magnifying glass and select BatchProcessPaymentSchedules.
- Schedule Apex Execution:
- Frequency: "Weekly"
- Recurs every week on: Select all checkboxes.
- Start Date: Choose a date (defaults to today).
- End Date: Set a date far in the future (e.g., 12/31/2050).
- Preferred Start Time: Set a time (e.g., 04:00 or 05:00).
- Click Save to finish.
Ensure that the user account you use to recreate the scheduled job has the System Administrator profile. This is necessary to grant the job the required permissions to access the AggregateResult entity.
Salesforce failed to accept data from Asperato error
If you receive a Salesforce error notification with the subject Courtesy notification from Asperato: Salesforce failed to accept data from Asperato, it indicates a problem with the FinancialForce/Certinia Asperato Integration package.
Error example
Cause and results
This error is caused by the FinancialForce Asperato Integration package exceeding the SOQL query limit (101 queries) when attempting to update the Sales Invoice to "Paid" while creating the Cash Entry. As a result, Unaric Payments cannot update the Payment Record in Salesforce, even if the payment was successfully collected from the customer. When this occurs, you will need to manually update your Payment Record. Contact Unaric Payments support at [email protected] for the details required to perform this manual update.
Certinia is planning a fix for this issue in a future version of their package. Contact Certinia support directly to inquire about the release date for this fix.