Save C/AL Code directly in a table

Roger

Hello,

I'm looking for a possibilty to save C/AL Code in a specified table. I want to do the same as Code Coverage does. But I want to have the control, from which object I read the source.

Does anybody know if it's possible? If the answer is yes, how can I do that?

Thanks for all hints,
Roger

Miklos_Hollender

Sure. Just look up CODECOVERAGELOG in the help. You gotta insert turning it on and off into each piece of code you want to log.

Roger

Thanks for the answer.

But it's not exaclty what I want. Mybe, my explanation was'nt clear enough.

I want to read the complete source code of an object (for example Table 36) for save the source, or parts of it, in a own table. I'm looking for a way to create a documentation of changes in the standard source.

ara3n

you can export it as text. and use the developertoolkit or text compare software.

Savatage

You can to export the object as text file & view it notepad

you'll see everything

here's a download you might be interested in
http://www.mibuso.com/dlinfo.asp?FileID=205

Roger

There is no way to do some things with C/SIDE functionalitys? It's possible to run the object export as text files from a codunit?

ara3n

You could do it. This way. Create a new codeunit Turn on codecoverage in the codeunit, and call every single codeunit. then stop codecoverage. and export the data from code coverage table to a text file and you have all the code from all the codeunits. You could do the same thing for forms, tables and reports.

Navision doesn't give you access to the blob where the compiled code resides. It's probably encrypted.

Roger

Thanks for the very good hint. On this way, it's possible to transfer the records from the code coverage table to another table directly in navision.

But, how can I run a table from a codeunit?

Miklos_Hollender

For documenting the changes, I think there are some automatic diff stuff here in the downloads.

My personaly view is that 70% of the development is setting object properties, and these kind of changes look like crap with an automatic diff on text files. So I just write documentation in the Documentation trigger by hand and extract it from the text files with a simple script.