Hello,
I want to add a field for perf_code to our local ticket history view so we can query that data in List Manager. I made a similar change before when I added a column for the number of tickets scanned, and when I did that I added a column to LT_TKT_HIST, and then to the secure view, and then to the screen in the constituent record. With all of that in place I altered the update procedure.
Now, I can do all of that again, or maybe I could just alter the secure view by joining it to VS_PERF and adding perf_code to the select statement. Is this a terrible idea? Are there reasons why I should do it the "right" way by adding the field to the actual table?
Thanks for your input.
Jared
I think doing the work in the view is a reasonable way to go. The only advantage to putting it in the ticket history table is if there is somewhere else in the system that the table is used directly which also needs the extra column. I think the join will work out for perf code. If you were joining using a non-indexed column or columns that weren't primary keys, I might go a different way.
- Levi
Unknown said: Now, I can do all of that again, or maybe I could just alter the secure view by joining it to VS_PERF and adding perf_code to the select statement. Is this a terrible idea? Are there reasons why I should do it the "right" way by adding the field to the actual table?
I think both of the methods you describe can be the "right" way. I've done both here: a completely custom LT_TKT_HIST + InfoMaker tab as Brian describes (and I'm looking forward to modifying these again with v12), and a quick added field to, e.g. satisfy some report that wanted a particular column.