Validating SysOperationDataContract using a pop up box for a batch job

(0) Share

Report

Posted on by 0993BV

Hi all,

I am not sure if it is even possible, but I think I have seen some standard AX batch job doing the same. I have a query on my data contract class that I use in my service class to loop and do stuff in batch.

I want to give users a pop up to say, the query has "10000000" records, you want to continue?

I tried putting the following in my contract class but the pop up doesnt appear (because it is a batch) and returns it as false. Is there any way to achieve it?

public boolean validate()
{
boolean isValid = false;

QueryRun queryRun = new QueryRun(this.getQuery());
int totalRecords = SysQuery::countTotal(queryRun);

if (totalRecords)
{
if(Box::yesNo(strFmt("This process will work on %1 records, do you want to continue?",totalRecords),DialogButton::No) == DialogButton::Yes)
{
isValid = true;
}
}

return isValid;
}

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

The batch framework cannot interact with users. Why do you want to display this message? Using a task in the batch assumes that it should be run anyway. If you notice some performance issues, you can review the process and possibly split the work into multiple threads or see if index changes can improve the performance.

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

You would have to calculate the number of records and show the message already when scheduling the batch, not during its execution. If it's suitable for you, let your data contract class implement SysOperationValidatable interface and put your logic into validate() method. You can find details in documentation: How to: Add Validation to a Data Contract Class.

Was this reply helpful? Yes No
0993BV on at

Like (0)

Report

Hi Andre,

I am running the process in multiple threads, but I feel some users can still empty my query and run it for everything (even when it is designed to not be run for that). Just want another failsafe to make sure user knows when they are going to attempt something stupid.

Was this reply helpful? Yes No
0993BV on at

Like (0)

Report

Hi Martin,

The validate method example above is only after implementing SysOperationValidatable interface. But of course, it doesnt give a pop up when running as a batch. I will display the message when scheduling (in the main method, before the startoperation method).

Thanks,

Vib

Was this reply helpful? Yes No