Hi, Long ago I created a tool to help converting your current diary-fields to a sub-form instead.
The interface is kind of crude, but it is quite powerful. For example it can pull out assignments and status changes into separate fields, under the condition that you have stored these in the diary field originally. RRR|DiaryX: https://rrr.se/cgi/index?pg=diaryx And yes, sub-reports make it possible to do reports on individual tickets and the "diary" data from the sub-form. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Hi John, > > We still use diary fields in some cases here, but, due to their > limitations, we have been steering clear of using them - same for status > history. > > We prefer to use a related companion form with workflow and a table field > on the main form to store a "Work Log" in stead of a Diary Field because of > the extra possibilities it offers for expansion and reporting. (same goes > for Status History). > > At the end of the day, if you are talking about a "Work Log" or status > history on a small data form somewhere in the background of your > application, sure, use the Diary and standard Status History, but if you > are talking about a main application form, rather go with the related > companion form to store a "Work Log" (or Status History). > > Reporting on the related form is relatively easy to do with sub-reports > etc. > If you are using Oracle, you could even use the LISTAGG function to combine > your related records into a single column value on a SQL Query or DB view > you create. > > HTH, > > Best Regards, > Theo > > > On Tue, Sep 30, 2014 at 12:30 AM, Reiser, John J <[email protected]> > wrote: > >> ** >> Hello Listers, >> I have quick question. >> What is the general consensus on the use of Diary fields? >> Are they going out of style? >> I have tried a “work log” table type of design to replace the diary >> function on a form. >> This method works ok except when it comes time to run reports. >> Do you dump the table field data to a large character field? >> Or is there a slick way to incorporate the child records into the report >> on the fly? >> >> Thank you, >> --- >> John J. Reiser >> Remedy Developer/Administrator >> Senior Software Development Analyst >> Lockheed Martin - MS2 >> The star that burns twice as bright burns half as long. >> Pay close attention and be illuminated by its brilliance. - paraphrased by >> me >> >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
