Brien, The default value of the field TempReqSummary is #First Name# as defined on the form, in the Field Attributes Default Value.
When entering the information on the form, I enter the name Denise in the field First Name. Upon submission the Replace function is changing the TempReqSummary value to the value in the First Name field (in this case, Denise). This is as I want it. I see this happen in the log. When the record is saved, the saved value is back to #First Name#. Is the Default Value overwriting the Set Fields Replace() function? Thank you for your help, Christine On Oct 7, 3:23 pm, Brien Dieterle <[email protected]> wrote: > Is there a Set Fields operation that is setting $TempReqSummary$ to > "#First Name#", or is "#First Name#" the default value or the value you > are entering into the field manually? > > Brien > > On 10/7/2010 1:25 PM, Christine wrote: > > > > > > > I’m using the Replace() function in a filter Set Fields action. I can > > see in the logs where the Replace() is successful during filter phase > > I processing. However, when the record is saved the original value of > > the field (not the Set Fields value) is still present. > > > Original Field Value: #First Name#; > > Filter Set Fields action: REPLACE($TempReqSummary$, "#First Name#", > > $First Name$) > > > The result in the log is the first name in the field TempReqSummary. > > Entry from the log is: “TempReqSummary (536871236) = Denise;” > > > When the record is finally written to the db the TempReqSummary has > > the value of #First Name#, not ‘Denise’ as I am trying to achieve. I > > see nothing else in the log where this value is getting overwritten. > > I’m logging both ACTL and Filters. In the log when this filter is > > complete there is the message “End of filter processing (phase 1) – > > Operation Create on (form name) -<NULL> “ > > > I’ve been looking at the filter processing for the email message > > creation which uses this type of Replace() action. I’ve logged that > > process but I can’t see what actually ‘seeds’ the value in the target > > field. There is no ‘commit changes’ in filter processing as in ACTL. > > I’ve read and re-read the Workflow manual about filter phasing but I > > am obviously missing the fix for this. > > > Can anyone direct me to what I should read/understand next in order to > > get this working? > > > This may be a very simple replace function, but it is a test of > > something larger that will aggregate values of multiple fields into > > one text field with other wording and formatting. > > > Thanks, > > Christine > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are"- Hide quoted text > - > > - Show quoted text - _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
