Hello Listers,

I opened a ticket with BMC Support about an issue with Modify All
clearing a Required Field on my form and throwing ARERR 326.
Then I found a list entry about SW00264343.

When I checked with BMC Support it was listed as "fixed". No version
reference or any other explanation ( unless I missed something in the
bug entry).

I updated my Issue with this bug number and sure enough I was told:
"After looking through the defects, SW00264343 is fixed.  It will be in
the next patch line and in the 7.1 release.  After the Modify All, the
valuechange [sic] flag need to be cleared."
So I figured this was a hint at a workaround. Clear the change flag and
the Modify All will not complain about a Required Field being set to
NULL. Only trouble is how to clear the flag. I used a Run Process
SE-CHANGE-FLAG 0 but when I triggered it I lost the ability to save my
entry. 

The work around that I found was to enter the search criteria and go
straight to the Modify All. It works that way but my users run up a
large search, pick and choose the entries to update and then try to do a
Modify All. The action of performing the search and subsequently
clearing the fields for the Modify All action brings on the error. And
it is not restricted to this one form.

I don't want to create a special workflow and objects ( buttons or
zTmp_Fields) just to get past this but I think I am stuck until BMC
support releases the fix.

Is there something that I am missing in the Run Process or $PROCESS$
commands?

TIA,


John "not going to the GWN for the BUW" Reiser
Software Development Analyst
Remedy Administrator/Developer
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased
by me 
 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to