Download Meta-Update User`s Guide

In the case where the target is a String Tag, the duplicate
assignment option default is DupOverwrite.
To use DupIgnore on String Tag targets so that prior
assignments may be made, the following command should
be run at an opportune point (the AssignInit or AssignTerm
sections for example) to remove the last iteration’s values:
@Cmd
=
Reference,
Tag,
/del
Only one of Skip: or Fields: can be used and it must be the last keyword on the
command.
Keywords for Copy commands
SrcTag
Specifies the source reference tag. This can be a string reference which
must evaluate to a defined tag.
This Tag can be a loaded Remedy record, a loaded File record, or a
String Tag.
Only fields with the same Ids (if both the source and target are Remedy
records), names and types can be copied. Options indicate what to do
on mismatches.
You can also override the copy of some fields by making explicit
assignments to those fields ahead of the copy command and selecting
the default option: DupIgnore.
DupAppend
DupOverwrite
DupIgnore
If a field already has been assigned a value, this will cause the copied
value to be appended to the current value if possible. This is only
possible for character and diary fields.
If a field already has been assigned, this will take the value in the copy
source record.
If a field already has been assigned, this will ignore the value in the copy
source record.
If not specified, DupIgnore is taken as a default.
MismatchIgnore
MismatchWarn
MismatchError
CoreAssign
NoCoreAssign
When comparing the source schema to the target schema, this will ignore
any mismatched fields.
When comparing the source schema to the target schema, this will ignore
any mismatched fields and issue a warning message.
When comparing the source schema to the target schema, any
mismatched fields will cause an error and the assignment will not be
processed. The record will not be updated.
Indicates that the “core” fields are also to be copied. This is only useful
when doing a Merge operation. Note that specifying CoreAssign will also
cause the Request Id field to be assigned. If you do not want this,
specify Skip: 1 in addition to the CoreAssign.
Indicates that the “core” fields are not to be copied. This is the default.
CoreAssign, NoCoreAssign, and the MisMatch options apply only if
the target is a Remedy record.
Meta-Update
- 171 -
User’s Guide