First, thank you all for your suggestions on this. I beleive that the way to fix this problem is to create the 10th view in the HD Archive form. Then all new fields should carry over correctly. Unfortunately, I haven't been able to do this and Remedy Support has not provided a process for doing it.
Carey,
You mentioned giving the 'driver' program a shot. I'm afraid I never used this tool. Is this the same as archgid that Fred referred to? Is this a Remedy utility or 3rd party and how can I get it.
Thanks,
.ron
On 9/5/06, Carey Matthew Black <[EMAIL PROTECTED]> wrote:
Ron,
Hum... I would think that some of what your experience might actually
be an Admin tool "resource" issue that I have seen from time to time.
I have seen:
) Field Property dialogs that have missing tabs. And as you click on
more tabs the tab that you just selected is removed too !
) Sync DB operations that fail
) Objects that refuse to open because I have dozens of other objects
open at the same time.
) etc..
I would suggest that you:
) exit all AR Admin Tools
) start only ONE ARS Admin Tool
) open only that form and make your changes
Now.. if all that still fails to create the field on the archiving
form (and it might) then I think I would give the driver program a
shot a creating the view and/or fields. You should be able to specify
the vuiId in that client. Then go back to the Admin tool and try to
add the field in the primary form. Please understand that getting the
vui created properly will take some trail and error, but I would think
you can work out the details by looking at the vui on the primary form
first.
HTH.
But I also have yet to use the Archiving feature in production yet.. so YMMV.
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.
On 9/5/06, Ron Tavares <[EMAIL PROTECTED]> wrote:
> **
> Hi Rick,
>
>
>
> I have tried creating the field in just the Admin view. It creates fine in
> the Help Desk form, but it still fails to carry to the HD Arcive form. This
> is because of that 10th view, (fr_CA), which is not on the HD Archive form.
> Even though the new feild is not included in the fr_CA view, the fr_CA view
> is still defined in the field properties in the 'Not in View' window. I
> believe this is what is causing the issue.
>
>
>
> On 9/5/06, Rick cook < [EMAIL PROTECTED]> wrote:
> >
> > **
> >
> > Ron,
> >
> > I tend to agree with Remedy, though it does seem a bit kludgey. Do you
> have a view in which all fields exist? If not, you should. If so, create
> the field in that view only, ensure that the archive form has the field (if
> appropriate), and then add it to the new view.
> >
> > Rick ________________________________
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected] ] On Behalf Of Grooms, Frederick W
> > Sent: Tuesday, September 05, 2006 6:30 AM
> > To: [email protected]
> > Subject: Re: Problem with Remedy Archiving when adding Views to the form.
> >
> >
> >
> > **
> > As for changing the view ID have you tried the archgid utility?
> (Unfortunately I can not answer the other as I do not use the out of the box
> archiving)
> >
> > Fred
> >
> > ________________________________
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected] ] On Behalf Of Ron Tavares
> > Sent: Tuesday, September 05, 2006 8:15 AM
> > To: [email protected]
> > Subject: Problem with Remedy Archiving when adding Views to the form.
> >
> >
> > **
> >
> > This is kind of a 'long story' problem, but I'll try to keep the
> explanation brief but clear and hopefully someone will understand this
> issue.
> >
> >
> >
> > We had 9 Views on our Help Desk form when we turned on the out-of-box
> archiving. When we did that, Remedy created the Help Desk Archive form with
> the same 9 views and the Archiving has been running fine since then. We
> then added a 10th view to the Help Desk form, this should have carried over
> to the Archive form, but it didn't. Remedy Support states that this is not
> a bug because Views are not required for archiving data. This is true only
> if you never add any new fields, (please read on).
> >
> >
> >
> > The problem comes when I add a new field to the Help Desk Form. The new
> field always fails to carry to the Archive form, because it contains a view
> that Archive form does not recognize. Even if I remove the field from that
> problem view, it still fails because the view is still included as an
> optional view. Additionally, the Archiving becomes disabled because the
> fields are out of sync.
> >
> >
> >
> > So, my work-around for this has been to manually re-creating the field on
> the archive form, being careful to keep the properties the same, especially
> the ID. This allows me to enable the Archiving process again and all is
> fine. BUT, I just tried adding a Radio Button field, and for some reason,
> when trying to create a Radio Button field on an Archive Form, all the
> attribute settings are grayed out, so I am unable to define the field
> properly. I have also tried re-creating the view in the Help Desk Archive
> form, but that doesn't work because the view id comes up different, and I am
> unable to change it.
> >
> >
> >
> > Has anyone seen this before?
> >
> >
> >
> > Thanks,
> >
> > .ron
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
__20060125_______________________This posting was submitted with HTML in it___
