Hey guys,
I have a slightly lengthy project I've been tasked with, so I'll spare you the details, unless somebody is familiar with the factory coding and what everything does.
But essentially, I created a custom field on the "Sales Invoice Line" table and need to write to it. I'm trying to piggyback off of a process that happens at some stage during the posting of a sales order (which creates a sales invoice).
The most relevant thing I was able to find, after a lot of poking around in C/AL code, is codeunit 20. I tried entering some debug messages, simple things like "MESSAGE('NameOfFunction');" at the top of each function, and surely enough when I would post a test invoice it would pop up the message boxes. But as I checked the records during the process, it looks like there are other codeunits running besides just that one.
To avoid having to go deeper and deeper down the rabbit hole, I'm curious if there's some sort of a "debug mode" where I can see what codeunits it's running and at what part. Basically a "trace" mode where I can manually step it through its paces until the data I'm looking for is written.
Or if anybody here is proficient with the factory-written codeunits (as well as the C/AL code built into the RTC pages that calls said codeunits), I can explain what I'm trying to do. I just figured it would be better do to my own debugging to save others the effort.
I have a slightly lengthy project I've been tasked with, so I'll spare you the details, unless somebody is familiar with the factory coding and what everything does.
But essentially, I created a custom field on the "Sales Invoice Line" table and need to write to it. I'm trying to piggyback off of a process that happens at some stage during the posting of a sales order (which creates a sales invoice).
The most relevant thing I was able to find, after a lot of poking around in C/AL code, is codeunit 20. I tried entering some debug messages, simple things like "MESSAGE('NameOfFunction');" at the top of each function, and surely enough when I would post a test invoice it would pop up the message boxes. But as I checked the records during the process, it looks like there are other codeunits running besides just that one.
To avoid having to go deeper and deeper down the rabbit hole, I'm curious if there's some sort of a "debug mode" where I can see what codeunits it's running and at what part. Basically a "trace" mode where I can manually step it through its paces until the data I'm looking for is written.
Or if anybody here is proficient with the factory-written codeunits (as well as the C/AL code built into the RTC pages that calls said codeunits), I can explain what I'm trying to do. I just figured it would be better do to my own debugging to save others the effort.