Maximum of total Receipt line

[DnD_IT_Solution]

Hi,
May i know any limitation of the receipt line while performance Batch Create?
As i face an issue while i using Batch create for total 1067 record, the last 186++ record it will not be able to retrieve the invoice but become “Suspense”.
I can confirm those invoice is created in system and if i manually add, it is success to be added.
Batch Create result:-

Manually add the invoice, it is successful add to the receipt.

[eko]

Yes as maually you would have provided an account (accounts receivable) which you didn’t do for batch create (hence all in suspense account).

[DnD_IT_Solution]

Hi @eko ,
All the line have the account UID while i create the batch. Hence you may see at the top those able to link with the account receivable, however at the bottom around 186++ order it is not able to link with the correct invoice, even the invoice UID is correct.
below with the batch create i use.

[eko]

The edit screens are more insightful than the view screens, please provide for both scenarios.

[Ealfardan]

That sounds like a bug. 186 appears to be an arbitrary limitation on batch create lines.

I will try to replicate this and let you know

[eko]

Good lateral thinking. It would be useful to know the Manager version and installation (Server, Cloud, Desktop Windows / macOS / Linux) and memory settings (RAM) of the computer it is installed on. I am not sure if for example the batch create function creates a multi dimensional array first (in memory) and then carries out a single database call with batch_insert. This is for @lubos to further explore.

[Ealfardan]

Update: I failed to replicate this behavior using Cloud Edition, MS Edge on Windows 10.

I was able to successfully create a single receipt and a single sales invoice with 885 lines each containing account UUID and nothing else.

I was also able to update the invoice, however when I tried to update the receipt I found out that it wasn’t assigned a UUID (which may be related or could be something completely different).

It seems that there isn’t any official limits but many other factors could force practical limits. My guess is that it’s something similar or related to this past bug:

@MarkLL

Morning @Tut, let me see if I can help…

I definitely fails once you select the 250 of more row indicators. And here is the reason.
The Javascript code that handles this process simply joins all the keys (uuids) together to create a url. Unfortunately, the length of the url is too long. So for 250 items the length is 9,292 characters.

xhr.open("POST", batchDeleteUrl+'&Keys=' + keys.join(','));

Edit: Actually my original suggestion will never scale for large numbers of items so…
I suggest that lubos change it so the keys are split up into blocks of 100 or so and process that way.

The following is a StackOverflow response to the google search “maximum length of post data to html”

The POST method allows sending far more data than the GET method, which is limited by the URL length - about 2KB. The HTTP client (browser or other user agent) can have its own limitations. Therefore, the maximum POST body request size is min(serverMaximumSize, clientMaximumSize)

@DnD_IT_Solution could you re-examine this using less text and see if it’s some sort of text length limit. If it’s not then maybe you can share the following information – at minimum:

• Your edition and version
• Your OS and browser details
• Sample batch create/update data which caused the error.

[DnD_IT_Solution]

Hi @Ealfardan ,

I have try to re-examine it with less records, which I split my template to multiple receipt, and it is running perfectly. It seem like this issue is happen when i running it with record more than 1k line.

Btw, below with my version.

• Cloud Edition
• Window 10 Enterprise
• Google Chrome