Hi Lisa,
Taking the fields out of the view the users get should fix the problem.
Brian
Brian Bishop
Goldstag Consultants Ltd
+44(0)7973 746832
-Original Message-
From: Kemes, Lisa lisa.ke...@tycoelectronics.com
Sender: Action Request System discussion list(ARSList)
I have found that it seems that when I use LIKE Company%, the % is not used a
wild card but as the actual per cent symbol in the search.
So when in doubt I use LIKE Company + %
Dave
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org]
Hi all,
I need some information that we are currently planing to upload 6.3 ITSM
closed change request's to 7.5 patch 4 can any one please give me you're
tip's and tricks how to do it.I am trying to do comparing the field on the
change console in 6.3 and 7.5 to find out any new fields added or
I agree with Dwayne. I don't know if it has something to do with how
Remedy parses out the variable or not, but I've found that sometimes I
have to use LIKE ($Company$ + %) in cases where I'm using a variable
within a filter.
Thanks,
Gary Opela, Jr.
Remedy Engineer
Avaya Phone Support
CNI/IT
I would not recommend uploading ITSM 6 Change to ITSM 7.X change due to the
many differences in the mappings. If this is needed for historical data please
review the form naming and since they are different just opy the 6 form to 7
without workflow and then export and import the changes using
Roger Justice wrote:
I would not recommend uploading ITSM 6 Change to ITSM 7.X change due to
the many differences in the mappings. If this is needed for historical
data please review the form naming and since they are different just opy
the 6 form to 7 without workflow and then export and
Meta-Update is the only product that can migrate ITSM 6 Changes (as well as
anything else) to 7.5 bar writing a program with the API.
Meta-Update is a scripting tool is replete with data transformation
features. Moving from ITSM 6 to ITSM 7.5 involves mismatching schemas.
That is, one change
7 matches
Mail list logo
