Hi,
I have seen some problems with table-columns and/or table-loops where I needed
to copy the field-id to a normal tmp-field first. I think this was the exact
scenario, but it was a long time ago...
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 Robin,
>
> I actually use this mechanism quite a lot, and it certainly does work when
> it gets the field id from other fields. One thing to note is that you MUST
> use this in a Set Fields - I actually don't think it'll even work in a Run
> Process (though I haven't confirmed this just now, but I'm pretty sure I've
> tried it in the past). So, that Set Fields action might look like:
>
> Field: SomeInteger0
> Value: $PROCESS$ Application-Copy-Field-Value $TargetFieldID$
> $SourceFieldId$
>
> where:
>
> *SomeInteger0 *- is some integer field that receives the "result" of the
> operation.
> *TargetFieldID* - is an integer field containing the field id that should
> receive the value
> *SourceFieldID* - is an integer field containing the field id that contains
> the source value
>
> As Fred mentioned, you can check the "return" value of this operation - the
> value that will be put into 'SomeInteger0' in my example - to determine if
> the operation was successful or not. It'll be set to 1 if it worked, 0 if
> not. I don't bother checking this anymore because, once you get it
> working, it's a very robust mechanism and never fails.
>
> This may be obvious, but just to be clear, the data types of the fields
> referenced by 'SourceFieldID' and 'TargetFieldID' do not themselves have to
> be integers. I haven't exhaustively tested this with all the different
> field data types, but it certainly works with Character, Integer, Date,
> Time, and DateTime field types. I also have NOT tried to use this to move
> a value from one data type to another...I'm not sure it'll do the
> conversion that a "normal" Set Fields would do.
>
> Let me know if this works for you or if any of this is not clear.
>
> Thanks,
> Charlie
>
>
>
> On Thu, Apr 24, 2014 at 2:26 AM, Robin Mathew <[email protected]>wrote:
>
>> Hi Fred,
>>
>> Application-Copy-Field-Value command works when ID of the field is given
>> as shown below.
>>
>> Application-Copy-Field-Value 1300567 1300568
>>
>>
>> In my case,I cannot use hard-code value as I am implementing dynamic field
>> value functionality.
>>
>> I have two fields ,Field_ID and Field_Value(ID : 1300567)
>>
>> Field_ID contains 1300568(ID of Priority field)
>>
>> I want to set Priority field value in Field_Value field.
>>
>> I tried, Application-Copy-Field-Value 1300567 $Field_ID$,but did not work.
>>
>> Please let me know how I can set value of a field to another field using a
>> variable(variable contains ID of the source field)
>>
>> Regards
>> Robin
>>
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> "Where the Answers Are, and have been for 20 years"
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
