Hi All, Thanks very much for your help. With all help found here I figured out the reason of my issue. Basically, I was supposed to set the field Login ID before trying to set the Assignee because the filter HPD:INC:ValidateAsgneeShft_054 uses Login ID to set the temp field z1D Char01. So, after the execution of filter HPD:INC:ValidateAsgneeShft_054 I could execute my updates.
Thanks! []'s Mauro 2010/7/19 Mauro Monteiro <maumontesi...@gmail.com> > Hi All, > > First of all, thanks everyone for your help! > > I did some tests and I think that I figure out the reason for the error > message. As I said before, I am trying to update some information related to > incidents that already exist in my Remedy environment. These incidents don't > have the assignee information filled in. So, my idea is to assign some users > to this field (assignee). Now, I noted that the filter > HPD:INC:ValidateAsgneeShft_055 has the criteria below (I highlighted what I > think it the reason for this issue); > > > (( 'Assigned Support Company' != 'DB.Assigned Support Company') > OR ( 'Assigned Support Organization' != 'DB.Assigned Support > Organization') > OR ( 'Assigned Group' != 'DB.Assigned Group') > OR ( 'Assigned Group ID' != 'DB.Assigned Group ID') > OR ( 'Assigned Group Shift Name' != 'DB.Assigned Group Shift Name') > OR ( 'Assigned Group Shift ID' != 'DB.Assigned Group Shift ID') > * OR ( 'Assignee' != 'DB.Assignee') > OR ( 'Assignee Login ID' != 'DB.Assignee Login ID')*) > AND ( 'Assignee' != $NULL$ ) AND ( 'Assigned Group Shift Name' != $NULL$ > ) AND ( 'z1D Char01' = $NULL$ ) > > According to my understanding, the RUNIF is comparing the current value > value for fields (for instance, both highlighted above) with the value > stored in database. In my case, I am trying to set some value for Assignee > field but this value in database is null. So, these conditions is true which > means that the filter runs. I removed both conditions from filter and I got > successful to update the incidents. > > If it is true, the same error should happened when you do it through GUI. > Don't you agree? > > My concerns are: > > How does the GUI dealt with this? Does it disable the filter before > creating/updating the incidents? > > 2010/7/16 Doug Blair <d...@blairing.com> > > Mauro, >> >> This is a common error message construction in a lot of the BMC ITSM >> applications. The z1DChar01 field is just a temporary field that holds the >> results of some other query. >> >> This error message construction usually consists of two filters with >> almost identical RUNIF's. >> >> The first filter tests for some condition by (for example) looking up the >> contents of a field to see if that text is valid for this ticket. If it is >> valid some text is set into the z1DChar01 field and if it's not valid (no >> match is found in the lookup) the z1DChar01 field is set to NULL. >> >> In the second filter the same RUNIF is used with one additional >> qualification added, testing to see if the z1DChar01 field is NULL. If it >> is NULL then a message is displayed and the transaction is stopped. If it's >> not NULL then the transaction continues. >> >> These two filters execute one after the other with no other intervening >> workflow so that the only thing that will change z1DChar01 is the first >> filter and it will be immediately tested by the second filter. BMC usually >> includes the EXECUTION ORDER NUMBER in the name of the filter. >> >> The one which displays your error message ends in 053, so I would look at >> the filter that ends in 052 to determine what check is being performed. >> That will probably tell you what the data error is.. >> >> >> Hope this helps.. >> >> Doug Blair >> >> >> On Jul 15, 2010, at 8:23 PM, Mauro Monteiro wrote: >> >> ** Hi All, >> >> >> After some investigations I found a filter named >> 'HPD:INC:ValidateAsgneeShft_053' which is responsible for showing the error >> message I sent before. Apparently, I must set the field 'Assigned Group >> Shift Name', I did it a very similar error happened - ERROR (1291055). Now, >> the issue seems to be related to the field named 'z1D Char01' because the >> new error is set on field named 'HPD:INC:ValidateAsgneeShft_055' which has >> the following criteria: >> >> *(( 'Assigned Support Company' != 'DB.Assigned Support Company') >> OR ( 'Assigned Support Organization' != 'DB.Assigned Support >> Organization') >> OR ( 'Assigned Group' != 'DB.Assigned Group') >> OR ( 'Assigned Group ID' != 'DB.Assigned Group ID') >> OR ( 'Assigned Group Shift Name' != 'DB.Assigned Group Shift Name') >> OR ( 'Assigned Group Shift ID' != 'DB.Assigned Group Shift ID') >> OR ( 'Assignee' != 'DB.Assignee') >> OR ( 'Assignee Login ID' != 'DB.Assignee Login ID')) >> AND ( 'Assignee' != $NULL$ ) AND ( 'Assigned Group Shift Name' != $NULL$ >> ) AND ( 'z1D Char01' = $NULL$ )* >> >> I tried to found this field 'z1D Char01' in the form HPD:Help Desk but I >> have not found it. Does anyone know where this field is defined? How can I >> set a value for it? >> >> Cheers, >> Mauro >> >> 2010/7/15 Mauro Monteiro <maumontesi...@gmail.com> >> >>> Hi Chemys, >>> >>> I don't have so experience with Remedy. How can I enable the trace to >>> figure out all filters running ? Is there a wad to loogin it? >>> >>> Cheers, >>> Mauro >>> >>> 2010/7/15 chernys <ben.cher...@softwaretoolhouse.com> >>> >>> ** >>>> >>>> What you need to do in the API program you are using is the same as the >>>> user tool does. Turn on logging in the user tool and do the assignment >>>> change. Then you will see the hidden fields that are being set by the >>>> workflow. Set those fields and your problem will go away. >>>> >>>> >>>> Cheers >>>> >>>> You are missing some ID fields like Assigned Group ID and depending on >>>> what you are really doing, a bunch more. >>>> >>>> >>>> You could also trace the set of filters to determine when the error is >>>> thrown. >>>> >>>> >>>> Ben Chernys >>>> >>>> Senior Software Architect >>>> Software Tool House Inc. >>>> >>>> Canada / Deutschland / Germany >>>> Mobile: +49 171 380 2329 GMT + 1 + [ DST ] >>>> Email: Ben.Chernys _AT_ >>>> softwaretoolhouse.com<ben.cher...@softwaretoolhouse.com> >>>> Web: www.softwaretoolhouse.com >>>> >>>> Check out Software Tool House's free Diary Editor. >>>> >>>> *Meta-Update**,* our premium ARS Data tool, lets you automate >>>> your imports, migrations, *in no time at all*, without programming, >>>> without staging forms, without merge workflow. >>>> http://www.softwaretoolhouse.com/ >>>> >>>> >>>> >>>> >>>> >>>> *From:* Action Request System discussion list(ARSList) [mailto: >>>> arsl...@arslist.org] *On Behalf Of *Mauro Monteiro >>>> *Sent:* July-15-10 14:47 >>>> *To:* arslist@ARSLIST.ORG >>>> *Subject:* ERROR (1291053) >>>> >>>> >>>> ** Hi All, >>>> >>>> >>>> I am using Remedy 7.1 and I am using the API to update some Incident >>>> information (form HPD:Help Desk). Initially it was working fine, The issue >>>> started when I tried to update the 'Assignee' information. Every time I try >>>> it, I receive the following error: >>>> >>>> ERROR (1291053): ; The Asssigned Group fields are invalid. Use the >>>> menus for the Support Company, Support Organization, Assigned Group, and >>>> Assignee fields or the type ahead return >>>> function on the Assigned Group or Assignee fields to select this >>>> information. >>>> >>>> So, I defined these information, I mean I defined (They are the same >>>> values used in GUI): >>>> >>>> Support Company: My Company >>>> Support Organization: IT Support Organization >>>> Assigned Group: Internal Support >>>> >>>> However, I kept receiving the same error message. What can I do? I >>>> appreciate any suggestion. >>>> >>>> Cheers, >>>> Mauro >>>> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ >>>> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ >>> >>> >>> >>> >>> -- >>> []'s >>> Mauro >>> >> >> >> >> -- >> []'s >> Mauro >> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ >> >> >> >> >> Doug >> >> -- >> Doug Blair >> d...@blairing.com >> +1 224-558-5462 >> >> 200 North Arlington Heights Road >> Arlington Heights, Illinois 60004 >> >> >> >> > > > -- > []'s > Mauro > -- []'s Mauro _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
<<bmc_skilled_pro_ar.png>>
