update z table in background

[Former Member]

hello all,

we are having problems on updating a custom table in background. the situation is that when we run a background job with different variants, all the entries in the table is updated, which is wrong. If the first variant is executed, that line should be updated, but if the second variant is executed, the entries for the first variant should not be updated.

is there a way where we can check the entries? we are using UPDATE <table> in our program.

thanks a lot in advance

[former_member226234]

Hi,

Are you updating the table in a loop at variant?

Regards,

Sandeep

[Former Member]

Hi,

Have you tried to run the program in foreground and debugged through to see what is happening?

Do that and then come back with some more specific questions - no-one on here knows what your program is doing so won't be able to help much without more information.

Gareth.

[Former Member]

hello,

yes, the program runs correctly in foreground, but after doing some testing, the problem was found only in background processing.

updating the table is not in a loop. the functionality of the table is basically just for the logs of the program, the variant name, the date and time when the program was executed using the specific variants.

the problem is when we have multiple variants, the entire table is updated, which is wrong. it shouldn't update the previous entries and should only update the specific record based on the variant.

[Former Member]

Hi,

Does it run correctly in the foreground if yuo use the different variants? I can't think of a way for the data updates to be affected by foreground/background mode other than if the data selections are different.

Gareth.

[Former Member]

in foreground, we are only executing single variant at a time and we are getting the correct update in the table.

but in background, we can execute multiple variants and the problem is the entire table is being updated, not with the entries based on the variant.

[Former Member]

Hi,

You need to run it in the foreground exactly how it is being run in the background and debug through to see what is happening. It's hard to help you otherwise as no-one can guess what is happening (although no doubt lots of people will.)

Gareth.