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 12:53 PM
To: [email protected]
Subject: Re: Merges Vs. Submit and Modify for Filters
Lisa:
What I said was:
"If the entry DOES not exist in the database, and you run a push fields
filter against the entry, the value NULL will be pushed." You can create a NEW
record from an existing record. However, you CANNOT push data into Form B from
Form A from a NEW record if there is a required field WITHOUT a default
value. I have created and then updated records through interactive
workflow, but I don't know the scope of the number of records being updated and
when this update takes place. Thus, a suggestion by me may result in a
non-responsive system during production hours (this is known as a bad thing.
(humor intended))
"If the entry DOES exist in the
database, and you run a push fields filter against the entry, the NEW value will
be pushed."
Again, I do not know of a method, other
than copying out the old value into a temporary field, to send out the old
value.
I think that your import is creating
new entries and thus there is no data in the field you want to send to the
second form from form A.
Maybe one of the other folks here knows
of a method that will work with merged data that will send the new entry's
serial number to the second form.
James McKenzie
________________________________
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of
Kemes, Lisa
Sent: Wednesday, October 11, 2006 9:45
AM
To: [email protected]
Subject: Re: Merges Vs. Submit and Modify for Filters
**
When there is a change on Form A, the
filter pushes the fields to a NEW record.
So your saying that, on a merge, the push is done first before
there is even anything committed to the database. So, really, when the
filter is doing its push, it's pushing "NULL" values.
How would I get the import to commit to
the database BEFORE the push is done? Or maybe I'm asking the wrong
question. How can I get the filter to not PUSH until the data is
committed?
Lisa
