Got Error "Cannot edit a record in Batch transactions (Batch). The corresponding AOS validation failed" when adding a new email address in Batch Tasks > Parameters >Destinations >E-mail

(0) Share

Report

Posted on by Community Member

I need to add one more person to receive this report. This report was scheduled to run as a batch job. I found the batch job in System Administration >Inquiries >Batch jobs. I have set the status of this batch job to 'Withhold'. Then click 'View Tasks' > click Parameters >click Destinations...>Click E-mail > add a new email address in the To: textbox >click Ok >click Close then I got error "Cannot edit a record in Batch transactions (Batch). The corresponding AOS validation failed"

Does that mean I can't edit the batch job. The only way to do it is to create a new batch job?

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Iulian Cordobin 8,201 on at

Like (1)

Report

Looking at the method aosValidateUpdate in the Batch table it seems you will have to meet several condition to change the values in a batch job. I think you might be falling into one of these cases that do not allow you to update a batch. They are:

        // quit if the user is not a batch-operator or if it's not the AOs
        changecompany(this.Company)
        {
            if (!Batch::isPrivilegedUser(this.CreatedBy))
            {
                return false;
            }
        }

        // ensure not to update the following column
        if (this.Company != this.orig().Company ||
            this.BatchJobId != this.orig().BatchJobId
            || this.DataPartition != this.orig().DataPartition
            )
        {
            return false;
        }

        if (currentUser != this.CreatedBy &&
            (this.Parameters != this.orig().Parameters ||
            this.ClassNumber != this.orig().ClassNumber))

        {
            return false;
        }

Was this reply helpful? Yes No
Verified answer

Tim Schofield on at

Like (0)

Report

Hi Anna, Julian's correct. To edit the parameters of a batch job you have to be the user that created the batch job and the batch job status has to be 'Withhold'. So it's maybe not the best idea to setup production batch jobs from a normal user log-in. If that user leaves ( and you disable the user) the batch job stops, and as discussed, you have to be logged on as that user to change the parameters. So may be best to use a service account type log in to setup production batch jobs - but maybe that requires another licence?

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Please consider following steps

Refresh the cache

Perform Full compilation and CIL compilation

please verify and update us with your findings

Was this reply helpful? Yes No