Unfortunately modifying the database like that does not affect the reporting. Don't be surprised if TestStand couples them in the future so you only have to mod it in one location. 🙂
There are a 100 ways to get the behavior you want. You can put a step in the TestReport callback in your Process Model that will parse and add the information to Parameters.Report. Put a breakpoint in there and step through it and watch that parameter. It is the txt that builds your report. You'll figure out where to put the step. You can use the ProcessModelClient variable referred to earlier.
The report is built on what is in the ResultList. So adding to that is also an option. That would be more obscure and a little trickier.
On-the-fly reporting is a whole different animal so you'd have to modify in different locations for that to work properly.
None of these will be the exact same as the database options because that one was for every sequence call. These would be a one time shot.
If you want it to be similar you will have to modify each of the ReportGen_<format type>.seq files to handle the sequence call steps and put the right info in the report txt.
