Okay, I’m new at this stuff, but I have done my homework on this one and I can’t find out why… I’ve got the following code: CurrReport.CREATETOTALS(TaxLiable,AmountExclInvDisc,TempSalesInvoiceLine.Amount,TempSalesInvoiceLine.“Amount Including Tax”); I’m in Debug on Version 3.6 and I want to set a watch for TempSalesInvoiceLine.Amount. But when I do, it comes up and tells me: Error: Symbol “Amount” was not found. So, what am I doing wrong? I’m honing in on the fact that I think[?] it’s occurring when it’s a field from a table (temp or otherwise). Can anyone verify this? Am I only able to watch true variables? ALL help is appreciated.

Yes, I think you have to call this variable in the watch : TempSalesInvoiceLine.Zoom.Amount I think it’s case sensitive

Well, guess what! I tried just keying it into the watch field, and it wouldn’t work. Then I tried to copy it in from the actual code section (drag - where you get the little hovering box). Still - no go. But I went to the Variable section, zoomed down onto the field, and copied it over to the watch window, and guess what - I’m seeing data now. So it seems just keying it in won’t work - I have to get it from the actual variable zoom??? Has anyone else encountered this? One more Debugger question: why can’t I set a breakpoint on these lines? Are their restrictions to where I can put a breakpoint? I just keep clicking the button and nothing!!! No red dot!!! [:(] TempSalesInvoiceLine := “Sales Invoice Line”; TempSalesInvoiceLine.INSERT; Thanks!

Hi Faithie, the possible positions of the breakpoints doesn’t sometimes (mostly) fit to sourcecode lines. try it one or more lines after that line you want to make the bareakpoint. In the old debugger (version 2.60) there were dots at the possible breakpoint positions. But now they made the debugger better !? br Josef Metz

It should be able to enter the variable in the watch manualy. But it’s case sensitive. Maybe you made a typo? if not… It must be that new debugger, which sux…

As a newbie to Nav, I’m falling in [:D]love[:D] with the Debugger. See, I used the old one…not impressed…AT ALL. However, a little more documentation would have been very nice. I got a full 3 pages from the Application Designer’s guide - most of which any programmer would already know (what’s a break point, what’s a call stack). It seems to be written from the standpoint that only folks who’ve cut their teeth on Navision are using it. What about us folks that are trying to learn it off the shelf??? I don’t want to see negative [:)] but the biggest downfall of Navision is the poor documentation. I’d like to see something on the lines of what MAPICS or CMS or even the other MSoft products have. Hopefully, MSoft will see this need too. And they need to be written by trainer-type folks!!! They know what the questions are! Here’s another question…is there any way to have Code Coverage also show the value of my variables as it’s processed??? I’m dreaming, right?

Hi Faithie, YES, you’re dreaming! And I’m dreaming of a Code Log, similar to Code Coverage, which will log each line of code in the order of execution, and there would the output of values of changed variables a clever extension. br Josef

Well, since we’re dreaming… 1. A debugger function that will allow you to Break When Variable = Value. 2. In Debugger - commented out sections don’t even show up on screen. 3. A history log of all operations the user started that day, the filters for those operations, and any errors encountered (they’re so good at pointing them out…ha). 4. The ability for all code errors to send a notification to a log so we can see and fix the problem. Oh - and how about we even tell the processing code unit, and log the data variables at that time. 5. A REAL error code list that explains what went wrong. All I have is a list of numbers and a 2-3 word title for the error. 6. A table guide. It would explain where the tables are populated, what the different pieces of data really are, and so forth. 7. Starting Navision would produce the aroma of cotton candy throughout the room.[^] Okay, maybe the last one was pushing it, but I’ve got a good feeling I’ll get that one as quickly as any of the others. Does anyone out there hear us? When I develop an application, I take most of my design from what the user’s needs are. Shouldn’t Navision do the same???

Hi Sorry for jumping in [:)].


Originally posted by faithiejlewis
… When I develop an application, I take most of my design from what the user’s needs are. Shouldn’t Navision do the same??? …

100% agree with that! You can do this if you develop for one customer (user). You should see my Navision enhancements for our company [:D] But - IMHO you have to go another way while coding a software for a wide range of customers. You have the decide what is the best for most of your customers. And from Navision point of view I think the designer mode for users is not the part of the application they always improve at first [xx(]. They want earning money for coding …[;)] But dreaming is always allowed … bye André

Hi Can Any body explain me the all the feature of debuger.

Well, keep in mind I’m VERY new to this…so what I offer may not be ALL of the debugger, but I’ll gladly share what I know.[:)] TO start it, from Object Designer - TOOLS - DEBUGGER - ACTIVE. (Be sure the ‘Breakpoint on Triggers’ is clicked. Start your job you want to debug as you would normally. (Note: if you want to bypass Debugging your request form and filter setting - don’ t turn on debugger until you’ve done these steps - turn it on right before it starts it’s processing - like before you push OK or PRINT or PREVIEW). Debugger at version 3.6 will then come up with three sections (unless you’ve got one of the VIEW’s turned off). At the top you’ll see the current code being processed. In the windows below you’ll have three different views (unless, again, you turned one off). One will show you variables (including current data item fields if you click the tree and go past ZOOM). Another has tabs for WATCHING certain variables. To do this the only way I’ve had any luck is to copy the variable from the variable window into the watch field. You have three tabs in the watch field in case you want to watch variables in groups (like some from a header table, some from a line table, some from another table, or even by codeunit being processed). Another window will show you the call stack - the objects being processed as they are called - with the highest being most current. If you want to break at one particular line, first set the breakpoint at that line (there’s a button on the toolbar). Then click DEBUG - BREAK ON TRIGGERS - to turn off breaking on every trigger in every object. This will cause it’s next break to be your breakpoint. F8 will process each line. F5 will run to the next breakpoint. Would anyone like to add to that?