Tom,

I saw the report button. I'm not using ITSM, I only access it from a remote
site.

The form that I built needs to be able to report on x number of parent
records and include y number of children records for each parent.
I could do it with a Parent/Child join but that would duplicate the parent
record info for each row when there are more than one children.
The customer wants the ability to dump the data from the schema for analysis
and have it all together.

I guess part of my issue is  I don't know if having a diary filed is worth
the space it consumes. The so-called security of the field can be duplicated
if needed or circumvented with the right tool or export / import steps.

Thanks,

--- 
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 


-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Tommy Morris
Sent: Thursday, September 22, 2011 12:41 PM
To: [email protected]
Subject: EXTERNAL: Re: Diary field vs Work Information form

Have you checked out the Report button at the bottom of the Work Info
table field? It might get you what you want other than the custom
tagging. That could be addressed with a process change though. Have the
user that is entering a Work Info record add the tag. That way you stay
as close to OOB.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Reiser, John J
Sent: Thursday, September 22, 2011 11:13 AM
To: [email protected]
Subject: Diary field vs Work Information form

Hello Listers,
ARS 7.6.03
MS SQL Server 2005
VMWare Windows 2003 Enterprise

My question: Does anyone use Diary Fields anymore? I don't see a Diary
field
anywhere on the Incident form.
I don't have access to the ITSM suite so I only know about the Incident
form
from a user perspective. 

I have something similar to the Incident Work History form. The
difference
is that I take the info from my "Work Activity" fields and push them to
a
Diary field in addition to pushing them to a Work Activity form. The
customer wanted custom tagging added to each Diary entry.
I'd rather not store the data twice so I was wondering if there is a way
to
use a display only field during report retrieval to table walk the Work
Activity and use the concatenated rows as field data.
I think I can do it for a report of one record from the parent form but
what
if the end user wants to report 2 or more parent records. 
I don't have access to Crystal Server or I would just do a sub-report.
A join won't work because it would duplicate parent data fields for
every
Work Activity record.

Any ideas are welcome.
TIA,

--- 
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 



________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to