We have a site that have large volumes of data being processed including grouped cashbook transactions but sage limitations mean 1000 records will not post due to out of memory errors, they have to do it in batches of 500 instead.
joanne scott
| Idea Benefit | allow sites that have large volumes of data to process transactions correctly so they match their bank account |
| How do you solve for this problem today? | post in 2 batches instead |
Our technical support team have contacted the person who raised this idea.
The site has bespoke work written by their business partner that performs the import, and the issue cannot be recreated on other sites therefore its a site specific issue.
For now this is not an idea and should be discussed via the support case.