Re: Merges Vs. Submit and Modify for Filters

Wed, 11 Oct 2006 11:06:23 -0700

Title: RE: Merges Vs. Submit and Modify for Filters
**
Fred,
 
I tested this and found that the default value gets pushed.
 
Lisa

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Wednesday, October 11, 2006 1:42 PM
To: [email protected]
Subject: Re: Merges Vs. Submit and Modify for Filters

**
What happens if you set that core field with a Default value?  Does the Default value get pushed to the history form or the value you are importing?

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kemes, Lisa
Sent: Wednesday, October 11, 2006 12:38 PM
To: [email protected]
Subject: Re: Merges Vs. Submit and Modify for Filters

**
OK, here's what I have found.....
 
I have the exact same set up for another form and it works just fine (each form has it's own history form).  The difference is, on my "problem" History form I am using a core field ("assigned to") as the serial number field.   I do this alot with core fields that I would normally not use, I just rename them to another field name. 
 
For some reason, this core field acts differently than a normal character field. (why, I'm not sure)  But as soon as I put a default value into the Serial Number field (a.k.a the "assigned to" field) and created another character field to put the serial number in, voila...it worked.
 
We are working with ARS 6.3 and it's a completely home grown system that we've created, so a lot of the core fields are just extra fields that we never use (i.e. - "Assigned To" and "Short Description")
 
Ugh, now I have some work to do, to fix my boo boo......
 
Lisa

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McKenzie, James J C-E LCMC HQISEC/L3
Sent: Wednesday, October 11, 2006 1:20 PM
To: [email protected]
Subject: Re: Merges Vs. Submit and Modify for Filters

**

Lisa:
 
No problem with the 'n00bie'.  We have all been there.  Some of us a long time ago, some a few weeks ago.  I just was asking for more information and made assumptions that you were creating a new entry in Form A as well.  Now that I understand the situation, I can make the following recommendation:


"It is interesting that the serial number field is being reported as empty.  Is this one of the fields being changed?  If not, I would report this problem to BMC, as the error should not happen."


James McKenzie
L-3 GSI
 

________________________________

From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kemes, Lisa
Sent: Wednesday, October 11, 2006 10:11 AM
To: [email protected]
Subject: Re: Merges Vs. Submit and Modify for Filters


**
Sorry! (You have to excuse my "newbie-ness"), but the entry does exist in the database, the import is just changing one or two fields.  The filter is supposed to push those changes to Form B (my History form) on the "merge" action.  This is where I'm getting the error message.


Lisa   

 

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

Reply via email to