It really is not that complicated indeed ....had to figure it out the hard way back then lol , I for one am interested with dimensions :) , many thanks hougaard !
I am trying to do this but with lines where I apply customer ledger entries using the apply to field on the journal lines. Then I run into an error caused by the suppressCommit in Codeunit 426 "Payment Tolerance Management". Do you have any idea how I can come around this? I do not find a way to set that in codeunit 12.
Hi Erik, If we have many lines in the journal and some of them have errors. Can we post only those that have no errors. It is a matter of posting already created lines through an automatic procedure.
in microsoft business central if i posted sales invoice and i used the same GL with two separate lines but when i checked the GL report it merged there as one amount instead of two, is it possible to solve it?
This video was just with default fields and explained very well, thanks for that. I think demo for, the new Fields that are required to be created in GL Entry table and passing value into it that too for e. g. just for sales related transactions would be a good one. Isn't it? Or may be it's silly🙄.
The challenge is, that several onValidate triggers on table 81 are expecting the record to exist (or the journal/batch), so as soon as you start validating in this scenario you'll run into a game of wack-a-mole. I suspect that's the reason Microsoft is not validating either.
@@Hougaard I guess Microsoft is not validating due to the following reasons: - TRANSFERFIELDS (legacy from PCC Navigator) - Validation might be different from the posting function or system-generated entries - Any code change in the GenJnlLine-validation might destroy the posting - Microsoft is carefully considering all the fields - Microsoft remembers to do VAT Personally I would prefer to insert a GenJnlLine because the posting is locking anyway. If Microsoft adds a field assignment in Codeunit 80, you better remember to include it in your code. With validation you might get a free lunch. When checking the code, please look at all fields in the posted records and not only the ones visible to the user.
Hi Erik, thanks for sharing! A video about dimensions would be great.
Great video! This enables us to use the standard functions without copying them.
It really is not that complicated indeed ....had to figure it out the hard way back then lol , I for one am interested with dimensions :) , many thanks hougaard !
I am trying to do this but with lines where I apply customer ledger entries using the apply to field on the journal lines. Then I run into an error caused by the suppressCommit in Codeunit 426 "Payment Tolerance Management". Do you have any idea how I can come around this? I do not find a way to set that in codeunit 12.
How to use Codeunit 90, " Purch.-Post" ? in order to post "Purchase Journal Line" .
How to post Purchase Journal via Custom Web Api ? How to write Code Unit and Page extension ?
Dimension sets would be a welcome topic :)
Great video as always, but it could be nice with a video on the consistent function.
Hi Erik,
If we have many lines in the journal and some of them have errors. Can we post only those that have no errors. It is a matter of posting already created lines through an automatic procedure.
Should like you need multiple journals to separate auto-created lines from the manual ones.
in microsoft business central if i posted sales invoice and i used the same GL with two separate lines but when i checked the GL report it merged there as one amount instead of two, is it possible to solve it?
ua-cam.com/video/Js3F0DNCkcQ/v-deo.html
Nice, easy and straight forward
Great one. Dimensions +
Hello, excellent video. What is the name of the extension that you use in Visual Studio to see the .app? Thank you.
AZ AL tools
great ..thanks. dimensions please :)
This video was just with default fields and explained very well, thanks for that. I think demo for, the new Fields that are required to be created in GL Entry table and passing value into it that too for e. g. just for sales related transactions would be a good one. Isn't it? Or may be it's silly🙄.
I gotta start somewhere, cannot go straight to the advanced stuff :)
Thakyou Sir
VALIDATE(please) - even with the ending cliffhanger ad :-)
The challenge is, that several onValidate triggers on table 81 are expecting the record to exist (or the journal/batch), so as soon as you start validating in this scenario you'll run into a game of wack-a-mole. I suspect that's the reason Microsoft is not validating either.
@@Hougaard
I guess Microsoft is not validating due to the following reasons:
- TRANSFERFIELDS (legacy from PCC Navigator)
- Validation might be different from the posting function or system-generated entries
- Any code change in the GenJnlLine-validation might destroy the posting
- Microsoft is carefully considering all the fields
- Microsoft remembers to do VAT
Personally I would prefer to insert a GenJnlLine because the posting is locking anyway.
If Microsoft adds a field assignment in Codeunit 80, you better remember to include it in your code. With validation you might get a free lunch.
When checking the code, please look at all fields in the posted records and not only the ones visible to the user.