<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 8/30/22 17:51, Mark Murawski wrote:<br>
</div>
<blockquote type="cite"
cite="mid:cd97cb1b-5101-7024-3228-6904e22701f9@intellasoft.net">On
8/30/22 12:34, Antony Stone wrote:
<br>
<blockquote type="cite" style="color: #007cff;">I want.
<br>
<blockquote type="cite" style="color: #007cff;">
<blockquote type="cite" style="color: #007cff;">However
writing:
<br>
Tracker=${CDR(uniqueid)};
<br>
<br>
results in:
<br>
MSet(Tracker=-1661872057.2349)
<br>
<br>
systemname is missing.
<br>
</blockquote>
Hi Antony,
<br>
<br>
This is not a problem with MSet.
<br>
</blockquote>
No, it is indeed the documented behaviour of MSet "MSet behaves
in a similar
<br>
fashion to the way Set worked in 1.2/1.4 and is thus prone to
doing things
<br>
that you may not expect."
<br>
</blockquote>
<br>
<br>
Please re-evaluate what I wrote previously. Again, this is not a
problem with MSet. You can see this for yourself if you do an
inline MSet(Tracker=${CDR(uniqueid)}); this will work fine.
<br>
<br>
Just because the documentation says that MSet should not be used,
it's not appropriate to blame all undesirable behaviors on MSet(),
since clearly MSet() is not the problem here.
<br>
</blockquote>
<br>
<br>
Let me correct myself. The documentation doesn't say it shouldn't
be used... it's making you aware of possible side-effects. It's
perfectly legitimate to use MSet() if you prefer the
assumptions/behaviors of MSet() as opposed to the
assumptions/behaviors of Set().<br>
<br>
<br>
</body>
</html>