Koyb, I concur, it can be done. Axton makes a good point that your programming has to be exact for this to work.
Another approach is to not use Diary fields and instead use a separate form for your diary entries. Each record in the form would contain a 0 length character field and be linked to a ticket (or any other type of entries). Related topic: This approach works well for attachments. Instead of adding attachment fields to your forms create a separate form that holds all attachments for all tickets (or any other type of entries). This allows you to have unlimited attachments per ticket, allows you to use workflow to limit the number of attachments and/or size of attachments based on what you want (ie. Group membership or type of ticket). HTH Stephen -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Grams Sent: Tuesday, September 12, 2006 8:53 PM To: [email protected] Subject: Re: Your article on web re diary fields. This is possible. In my current environment, we parse the diary fields into a table containing 4 columns for reporting purposes: - entryid - data - timestamp - user There are a series of special control characters (high bit ascii charactesr) used in diary fields to separate the user, timestamps, and actual data. You will have to mimic this format exactly to manipulate the data using direct sql. Be careful when doing this, as malformed entries can cause client instability (e.g., user tool crashes ungracefully). It would probably be safer to use an api to manipulate the data in diary fields unless you are extremely meticulous in the implementation of said feature. Axton Grams Koyb P. Liabt wrote: > ** > > Hi Axton, > > I was surfing the web looking for info on how to write a direct SQL to > a diary field. Is this possible. I created a custom diary field. > When a user presses a button the SQL statement appends the info within > a column in the database to the last entry. Is this possible? When I > set the field with the SQL statement -- the user's data is not sent > directly to the diary field. > > I came across your article on the web. Do you have any idea if a SQL > can directly send info into the worklog/and append more info later. > > > > Re: Duplicate Entries in Diary Field > <http://www.opensubscriber.com/messages/[EMAIL PROTECTED]/384.h > tml> by Axton > <http://www.opensubscriber.com/profile.os?individual=1771507> > > Reply to author > <http://www.opensubscriber.com/sendEmail.os?individual=1771507> Reply > to group <http://www.opensubscriber.com/sendEmail.os?message=1771507> > > > > It is active links that read the contents of a diary back into the > diary field when opened as a dialog. Subsequent saves cause the > entire contents of the diary to be rewritten. Be careful with this > becuase if the size of the text exceeds 1bm and the Oracle-Max-Text > size (or whatever it is called) is not set to a value greated than > 1mb, your server will crash. The workaround for this is to create a > display only char field that is used for new diary entries and update > the active links triggered when clicking the save button to push the > char field contents to the diary instead of the old diary field > contents. I have a bug open with Remedy on this, but no resolution > will ever be provided for the current release of the apps. > > Axton > > __20060125_______________________This posting was submitted with HTML > in it___ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
