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)

problem with Progress bar when businnes logic runs in CIL

(0) ShareShare
ReportReport
Posted on by

Hi! I work in ax not so long and have some problems.

I have to create a progress bar for procces of confirmation of purchase order.

When confirmation of purchase, from time to time because of the very large volume of purchases, have to wait for the confirmation process, while AX shows no sign of work, in addition to notification of the processing tray. I was asked to add to this effect the status bar, it must be a type not specified, only that workers have seen that something was happening.   I did this task via Sysoperationprogress, and it compile good and code performed, but Client doesn't see a progress bar. When client click on confirm button, AX only freezes until the operation to end, and that's all

I know that this operations work in CIL, namely FormLetterSrvice Class. Forms name is PurchTable

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,959 Most Valuable Professional on at

    I posted a trivial example of such a progress bar a few years ago in Runbase dialog event handling issue.

  • Community Member Profile Picture
    on at

    i didn' understand how it helps in my situaition

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

    As I understand, your problem is that you "have to create a progress bar" but Client doesn't see a progress bar".

    I gave you an example of a correctly implemented progress bar, so you can compare it with your implementation.

    I admit that I have no idea what you mean by "it must be a type not specified", therefore I ignored it. If it's important, please give us another explanation.

  • Community Member Profile Picture
    on at

    3603.Unbenannt.PNG

    I mean that in task not sayed about how it must be displayed on client. I  suppose something like standart progress bar would be ok

  • Community Member Profile Picture
    on at

    Is there a possability to display progress bar if code runs in CIL???

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

    Yes, it's possible to display a progress bar if code runs in CIL. I wouldn't give you code doing that if it wasn't possible. :-)

  • Community Member Profile Picture
    on at

    I can't really understand how can integrate it in FormLetter class, because it is my first experience with SysOperationServiceController. can you say in which order i have to integrate your solution?

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

    Well, can you try it first? Then we won't have to discuss again whether it's possible, how it looks and so on. Okay?

    You said that "you did this task via Sysoperationprogress, and it compile good and code performed". If you want to discuss your code, you'll have to show it. If you realized that your code was wrong, well, let's start from scratch.

    What exactly are you trying to achieve with FormLetter? If you merely won't to avoid freezing, did you consider use one of asynchronous execution modes (without any progress bar)?

  • Community Member Profile Picture
    on at

    The main problem is that the progress bar not displayed. When client want to confirm large volume of purchases. Sometimes the process takes very long, when confirming an purchase order. Some users just close and restart AX then, because they dont know if something is happening. And my task is that clients in procces of confirmation see what happenning

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

    If users have to wait before something is done, or if you have the problem that they close the client before it's completed, showing them a progress bar is no solution. They would still have to wait and they would still be able to close the client. A better solution may be simply adding the task to a queue and let users to continue with their work.

    You've reacted to my third paragraph only. Please make sure you haven't overlooked the other ones.

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