Major issue - batches of

RocketRod

I believe I have found a major issue with batches of command when working with groups in new version 5.8.

It only processes every second group of records. In other words if you say

IN BATCHES OF 1 then every second record is skipped.

IN BATCHES OF 5 then every second group of 5 records is skipped.

Can support please confirm ASAP if I'm right or not as this would be a major issue if I am correct. I have sent short excerpt from log showing id numbers being missed. Have already deployed to customer so I'm very concerned.

I'm hoping I'm wrong but I'm sure my apps were working ok before the upgrade.

There are two BO's in the group so I'm not sure if that relates to the issue. Have not tried with three BO's to see if every third group is missed.

Cheers Rod

rocketman

Any news from support on this Rod as I'm delaying going live with 5.8

RocketRod

Have sent sample bsv to Support and am awaiting their response. I'm still not sure if it's me or a bug.

Cheers Rod

RocketRod

Update rocketman.

Support have reproduced the problem and are working on it.

Cheers Rod

rocketman

Thanks Rod. Did they request the BSV or I did you just send it. I haven't had any comeback on my calendar drag and drop big at

RocketRod

They requested BSV.

If you can build a simple one quickly, I think it helps them a lot.

Cheers Rod

hpl123

Support,
Whats best and what do you want?: Create sample bsvs for all/most bugs or only if you ask for it?
Thanks

tford

Henrik,

Support has stated in the past that creating a "mini-bsv" that isolates and demonstrates is always very helpful. Along with the mini-bsv, specific steps should be outlines to reproduce the issue as well as screen shots where applicable.

hpl123

Ok Tom. Thanks for the comment. I have posted quite a few bug reports in the past and never done this but will start now 🙂.

RocketRod

It has been found that this is NOT an issue related to the recent upgrade and is related solely to working with Groups. It also occurs infrequently but is still an issue nevertheless. It may also only be related to SQL server DB's but that is not confirmed. So to avoid it in a process I suggest that you split out your process statements and work on each member of the group individually.

For example:

Instead of

FIND ALL BOGROUP in batches of 1
Subprocess

Use

FIND ALL BO1 in batches of 1
Subprocess
FIND ALL BO2 in batches of 1
Subprocess

This works ok. Finally sometimes placing an ORDER BY clause in the Group Find does also fix the issue but for me as it is not a 100% cure I am falling back to the above solution. So you can try

FIND ALL BOGROUP ORDER BY BOGROUP.ID in batches of 1
Subprocess

Cheers Rod