web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

cannot see parameters on batch job task when added manually - sysoperation batch job

(0) ShareShare
ReportReport
Posted on by 4,359

Dear all,

I have created few of the batch jobs with the sysoperation framework in AX 2012.

when I run these jobs from the menu items in a batch and then go the batch job form and look for the parameters, I could see the parameters.

But if I try to add these jobs manually, as in when I create a new batch job and select the class and then try to look for the parameters I could not see it. I could not find out the reason behind this. If anyone have any idea, please share.

Thanks.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Mea_ Profile Picture
    60,284 on at

    Hi ARPIT CHAVHAN,

    Did you try to click on "Parameters" button on action pane of you batch job task ? It should open you a dialog to setup parameters.

  • ARPIT CHAVHAN Profile Picture
    4,359 on at

    yes from there itself we can see the parameters. It opens the dialog but with yes and cancel option. I have other parameters like journal name parameter, but can not see this.

    And this is happening in every other sysoperation batch job.

  • Martin Dráb Profile Picture
    237,898 Most Valuable Professional on at

    I'm not sure what you mean when you say that "from there itself we can see the parameters, [...] but can not see this". Does it mean that you see the dialog, but you actually don't see any parameters (despite of saying that you "can see the parameters")?

    Anyway, is your controller decorated with SysOperationJournaledParametersAttribute? Are you using the default UI builder, or something custom?

  • ARPIT CHAVHAN Profile Picture
    4,359 on at

    Hi Martin,

    yes, I see the dialog but not parameters.

    My controller is decorated with [SysOperationJournaledParametersAttribute(true)].

    And I am using custom UI builder.

  • Martin Dráb Profile Picture
    237,898 Most Valuable Professional on at

    Isn't the problem in your UI builder, then? Have you tried to debug it?

  • ARPIT CHAVHAN Profile Picture
    4,359 on at

    Hi Martin,

    when I run the batch job from the menu item and then check the task in batch job form then I am able to see the parameters as well,

    But when I try to add that job manually in batch job form and then try to check the parameters I cannot see the parameters.

    This is the issue.

  • ARPIT CHAVHAN Profile Picture
    4,359 on at

    by manually I mean, I create a new record and add the class which I created for the batch job and saves the record.

  • Martin Dráb Profile Picture
    237,898 Most Valuable Professional on at

    Yes, I know, and what? There must be that works differently, which is either the UI builder or something providing data for it.

    If I was you, I would be debugging the UI builder instead of asking in forums. You're free to ask here if you prefer, but it can't replace debugging. We can't debug your system for you.

  • ARPIT CHAVHAN Profile Picture
    4,359 on at

    Hi Martin,

    Its not that, I have not tried debugging it. I could not find the solution that's why I asked in forum.

    Thank you for your time.

  • Martin Dráb Profile Picture
    237,898 Most Valuable Professional on at

    Finding a solution without systematically debugging the problem and isolating the cause isn't actually very likely. And strangers in forums that never saw your code nor can look at what's going on in your system are actually in an even worse position.

    The process of finding and removing bugs ("debugging") is not very easy and if you consider your program a black box and you don't at how it works internally, you won't be able to understand and fix a majority of problems. Fortunately you have tools that will help you, most importantly the debugger.

    You can start by replacing your custom UI builder with the standard one (don't forget to delete usage data after that), which will either tell you that the problem indeed is there, or it will simplify the situation because you'll know that the problem isn't in your UI builder and you'll be able to ignore it completely. Then you will either debug your custom UI builder, or the automatic UI builder.

    It doesn't mean that you're on your own, but it means that you have to collect more information before we can help you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans