It is expected behaviour. A set fields filter action is NOT a get fields.
So, to do what you want, you'll need to - do a GetFields and add the fields you need to your formB and to your push fields or - (better) add a condition on the get fields filter such as "any of the fields you are setting are null" and fire the filter on both get fields and modify. Cheers 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 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/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Brien Dieterle Sent: October-04-11 19:54 To: [email protected] Subject: Get Entry + Set Fields from another form's Set Fields operation ARS 7.5 P7 I have a form (formA) that sets a field on "Get Entry". This works great when looking at records or running reports on FormA, even if the field is display only. Is there any reason why this filter wouldn't execute from another form (FormB) performing a Set Fields operation of its own and using FormA as its data source? Checking Filter logs, the GET event doesn't get triggered for FormA when FormB is doing its Set Fields operation, so I don't think this is a phasing or execution order problem. I cannot find in the documentation whether this is expected behavior. A little background, I want to pull in one piece of Customer data from an external DB (cell phone #) but make sure that it is fresh whenever it is displayed. So, I have a display only field on FormA that is set on Get Entry using a SQL command data source. This works great when viewing FormA. Now I want to make that visible on FormB. I can't. I could setup the same DB Set Fields call on FormB, but I would need the same key fields on that form to do the same SQL command. I could also bring in the external DB as a view form and join that to FormA and then go from there, but it seems more complex than it needs to be for just this one piece of data. Any ideas? ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
