Yes, this is the way I have always done it in a filter with the `! Of course for those on the BMC Developer communities I put in an idea to improve the filter phases (the `! naming convention) https://communities.bmc.com/ideas/3639
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky Sent: Saturday, January 02, 2016 3:26 PM To: [email protected] Subject: Re: 9.0 Filter table walk issue Hi, My experience with similar situations is that storing the values in display-only-fields prior to operating on them in this way works better. Set-Fields displ-field = $column$ Push-Fields xxx = $displ-field$ I learned this in versions long before 9. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Hi Randeep. > > Thank you for your information. > > Yes, this same code is working on our production (version 7.5) > Yes, I certainly use `! in the filter name. > > I remember this problem was in one of the previous versions (just don’t > remember which one) and BMC provided the hot fix. > I wander is other people experienced the similar problem on 9 and there is an > available patch. > > Thank you, > Mike > > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Randeep Atwal > Sent: Wednesday, December 30, 2015 4:33 PM > To: [email protected] > Subject: Re: 9.0 Filter table walk issue > > ** > Hi Mike > > Can you confirm if the same code worked on a pre 9.0 system? If so, I'd > recommend you file this with BMC Support. > > But before reporting it, please ensure you are using `! on the filter doing > the push into a seperate form if you are not already doing so. > > https://docs.bmc.com/docs/display/public/ars201401/Server-side+table+field+implementation+issues > > · When creating workflow for server-side tables, filters with the > Call Guide action can be defined to loop over table columns. The values > retrieved during the looping always comes from the last row of the table. To > retrieve different values, postfix two special characters ( `!) on the filters > within the filter guide. Adding these special characters causes your filter to > execute synchronously, instead of deferring into a later filter processing > pass. For example, if your filter within the Filter guide is named FormA: Push > New Entry to Form B, postfix those special characters to look like this: > FormA: Push New Entry to Form B`! > > > hope this helps > > Randeep > > > On Wed, Dec 30, 2015 at 12:54 PM, Mike Ilmer > <[email protected]<mailto:[email protected]>> wrote: > ** > Hi list. > > I found that on 9.0 the filter table walk has issue. > Filters recognize value in the table’s columns that could be used for the > “if” validation. Values also could be used for the “SET” action. > However direct pushing column’s values into the different forms doesn’t > work. It pushing $NULL$ > > To iterate: I can use the filter to set values of columns into the separate > fields. This works fine, but the direct push into the separate form is pushing > $NULL$. > > Is this a known 9.0 bug? Is there are a patch that fixes it? > > Regards, > Mike _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
