07-19-04 10:53 PM
How are you passing in the user profile? If I remember correctly, you pass
it in to the evaluator via the dictionary under the key "UserObject", with
the value being the profile object itself.
-djm
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2004 Microsoft Corporation. All rights
reserved.
--------------------
From: hdanzige@gmail.com (Hal)
Newsgroups: microsoft.public.commerceserver.general
Subject: Problem with ExpressionEvaluator.eval
Date: 14 Jul 2004 13:37:51 -0700
Organization: http://groups.google.com
Lines: 22
Message-ID: <7985cc67.0407141237.4b18b64f@posting.google.com>
NNTP-Posting-Host: 69.18.134.136
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1089837472 4882 127.0.0.1 (14 Jul 2004 20:37:52
GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 14 Jul 2004 20:37:52 +0000 (UTC)
Path:
cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08
.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!tiscali!newsfeed1.ip.tiscali
.net!proxad.net!postnews2.google.com!not-for-mail
Xref: cpmsftngxa06.phx.gbl microsoft.public.commerceserver.general:14253
X-Tomcat-NG: microsoft.public.commerceserver.general
I am using ASP/COM on a Commerce Server 2k site. I am
trying to use the ExpressionEvaluator to evaluate a
target expression.
When the expression is related to non-profile data (such
as date), it properly returns true and false.
When the expression is related to profile data (such as
logon_name), it returns null. I have ensured that there
is a profile in the dictionary being passed into eval,
and have tested retrieving the GeneralInfo.logon_name
property from the profile in the dictionary. I was able
to retrieve it without a problem.
EVERY campaign expression (created in BizDesk) that I
test returns null when related to profile data.
Why is this happening? Any ideas? There are no errors
being return by the eval function.
Thank you,
Hal
[ Post a follow-up to this message ]
|