Skip to main content

Notifications

Finance | Project Operations, Human Resources, ...
Suggested answer

Need to replicate the OOTB workflow on journals from header to lines level

Posted on by 7
Hello,
 
I have a requirement to shift the OOTB workflow from General journals to line level,
 
 
there 
 
 I have achieved that by making the extension of LedgerJournalTransDaily form and add data source LedgerJournalTable in it join it with LedgerJournalTrans
and select the same workflow on LedgerJournalTransDaily that is using on LedgerJournalTable
 
Now its working and showing on lines level but the problem is the header workflow is only showing on lines level when i submit it the workflow on header level and than go back to the lines it will show but my requirement is to migrate/replicate or copy the header level workflow to the lines without going back to to header and just maked header one time and route to the lines level and just run workflow from there and post it.
 
Thank you soo much.
Categories:
  • HR-31101753-0 Profile Picture
    HR-31101753-0 7 on at
    Need to replicate the OOTB workflow on journals from header to lines level
     
    Quick update that this WF should work on header DS but i just need to show it on the lines level form and process it form lines
     
    thanks
  • HR-31101753-0 Profile Picture
    HR-31101753-0 7 on at
    Need to replicate the OOTB workflow on journals from header to lines level
     
    The requirement is to move the header level workflow to the line level and just run the workflow from that and post the lines ,the only problem i am facing according to the screen shots i have shared in the post is the workflow is only showing on lines form if its submitted from header level than its appearing on the lines level
  • Suggested answer
    t4m7 Profile Picture
    t4m7 20 on at
    Need to replicate the OOTB workflow on journals from header to lines level
    Hi - I understand the goal...depending on how complicated everything is, and also, i am not an X++ dev, i'm more architecture/process...but another lower dev option might be actually to continue to only use the header workflow, but change the procedure so that at submit (may need to add a custom submit button), maybe for certain named types of journal when there is more than one line, you take each line and make a new journal for each line, maybe using the original journal number with an -001, -002, -003 etc, and then submit those.  So, each journal only has the one line you need someone to look at individually. This would only work if each line is truly a separate decision and each line balances, so it depends on your journals.

    I suggest this because even in the OOTB places that support line-level workflow, we have seen that sometimes individual lines get stuck, or hold up the other lines, or a recall or reset is needed and everyone gets confused. Say, Person A approves line 1, Person B rejects line 2...meanwhile Line 1 is just waiting, line 2 gets adjusted or someone decides it was a mistake and says abandon it, etc, meanwhile line 1 is waiting, or is stuck having been approved and cannot be recalled.
     
    If each journal had only the one line, then the decision about each line wouldn't impact any other line...so if that is desired, maybe this could help you out.
  • Suggested answer
    Anton Venter Profile Picture
    Anton Venter 18,669 Super User 2024 Season 2 on at
    Need to replicate the OOTB workflow on journals from header to lines level
    Please tell us what the funtional requirements are for having this workflow on line level? Besides, you cannot change the standard workflow to line level because the standard workflow uses the header (LedgerJournalTable) and not the lines (LedgerJournalTrans).
     
    I don't think you should, but if you absolutely have to do this on line level, you will have to create a new workflow in Visual Studio using LedgerJournalTrans.
     

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Complete!

🔔 Be sure to subscribe to the new forums you are interested in to stay up to date! 🔔

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,900 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,275 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans