Hi,
The main reason we have Direct SQL is to integrate to data from outside
the Remedy-data.
If you use it to access/modify Remedy-data, you will have a hart time
analysing what is connected to a certain field. If you stick to
Remedy-workflow, you can do a very good cross reference of how things are
related in most cases.
I can see a few rare instances where Direct SQL can be 1000 times faster,
or where it is impossible to do with Remedy workflow. In that case you
should use it, and document it well with big red capital letters...
Best Regards - Misi, RRR AB, http://rrr.se
> I fail to see why, Direct SQL is a legitimate built in option.
>
>
>> Hi,
>>
>> Direct SQL makes a system hard to manage. If there are built in options
>> other than Direct SQL, use them instead!
>>
>> Best Regards - Misi, RRR AB, http://www.rrr.se
>>
>> Products from RRR Scandinavia:
>> * 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.
>>
>>> Another option would be to use a Direct SQL Action.
>>>
>>> Matt
>>>
>>>
>>>> Hi fellow listers,
>>>>
>>>> This is something which i had tried.
>>>>
>>>> My need was to change a field value in a form after a record is
>>>> submitted/modified and the record for which i need the field value
>>>> change
>>>> to
>>>> be made is the one which got submitted/modified.
>>>>
>>>> So I created a filter which gets triggerred(i.e on action Submit and
>>>> Modify)and then do a push field and change the value in the field for
>>>> the
>>>> same form-record.
>>>>
>>>> Now my problem here is that as I am doing the push in the same form
>>>> for
>>>> changing a value in the field, "ARERR 299 Too many levels in filter
>>>> processing" occurs. I know this happens because the Push field action
>>>> ultimately triggers a submit/modify action on the same form and the
>>>> filter
>>>> get triggerred infinitely.
>>>>
>>>> Can anyone suggest me a different approach to this?
>>>>
>>>> Cheers :)
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/ARERR-299-Too-many-levels-in-filter-processing-tp28750990p28750990.html
>>>> Sent from the ARS (Action Request System) mailing list archive at
>>>> Nabble.com.
>>>>
>>>> _______________________________________________________________________________
>>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>>>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>>>
>>>>
>>>
>>> _______________________________________________________________________________
>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>>
>>> --
>>> This message was scanned by ESVA and is believed to be clean.
>>>
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>>
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
