'Error in the evaluation of expression...' with emptyattributes

Mike Pokraka wug.replies at workflowconnections.com
Tue Sep 6 08:15:51 EDT 2005


Hi Jocelyn,
Interesting point, yes that would give the error. They do exist though,
it's a dynamic parallel subflow based on the object and the one whose
attribute is missing is the one that fails.

Incidentally, I've seen some curious behaviour debugging this one:
Sometimes a synamic parallel subflow going into error automatically puts
all other flows into error at the very top, other times not (the other
subflows are 'started' and agents of the other subflows get their items).

Thanks for the input,
Cheers
Mike

Dart, Jocelyn wrote:
> Hi Mike,
>
> You might want to check that your object attribute is attached to a
> valid object instance at the point it is being evaluated.  If the object
> instance hasn't been created yet that would give the kind of error you
> are receiving.
>
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com
>
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for
> the person or entity to which it is addressed. If you are not the
> intended recipient, you are hereby notified that any distribution,
> copying, review, retransmission, dissemination or other use of this
> electronic transmission or the information contained in it is strictly
> prohibited. If you have received this electronic transmission in error,
> please immediately contact the sender to arrange for the return of the
> original documents.
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or the
> consequences thereof.
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of
> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability
> for the accuracy or completeness of the views or information contained
> herein. Please be aware that the furnishing of any pricing information/
> business proposal herein is indicative only, is subject to change and
> shall not be construed as an offer or as constituting a binding
> agreement on the part of SAP AG or any of its subsidiaries to enter into
> any relationship, unless otherwise expressly stated.
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Friday, 02 September 2005 6:21 PM
> To: SAP Workflow Users' Group
> Subject: RE: 'Error in the evaluation of expression...' with empty
> attributes
>
> Good point! Just checked, and no exceptions are raised. It's just
> empty...
> Thanks
> Mike
>
> Tiwari, Rammanohar wrote:
>>
>> not sure but can you check if any exception like 'object not found' is
>> used inside the coding for this object->attribute?
>>
>> cheers,
>> Ram
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On
> Behalf
>> Of Mike Pokraka
>> Sent: Thursday, September 01, 2005 11:23 PM
>> To: sap-wug at mit.edu
>> Subject: "Error in the evaluation of expression..." with empty
>> attributes
>>
>>
>> Hi folks,
>> Has anyone seen problems in assigning empty attributes?
>>
>> It's working fine in dev: I assign an object attribute with an object
> type
>> to a container element and check it later for various reasons. However
>> once transported to QA its all falling apart with "Error in the
> evaluation
>> of expression ....." when the attribute has no instance.
>>
>> I've gone as far as doing a detailed trace and on one system the
>> assignment is followed by 'Node Processed' and the other does a
>> 'SWW_WI_WRROR_MESSAGE_SEND' after the identical container operation.
>>
>> OSS hasn't even heard of the error message number, but searching for
> the
>> error text just turned up a few older notes.
>> Stumped.....
>>
>> Cheers
>> Mike Pokraka
>> Senior Consultant
>> Workflow Connections Ltd.
>> Mobile: +44 (0)7786 910 855
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> This e-mail and any attachment is for authorised use by the intended
>> recipient(s) only. It may contain proprietary material, confidential
>> information and/or be subject to legal privilege. It should not be
> copied,
>> disclosed to, retained or used by, any other party. If you are not an
>> intended recipient then please promptly delete this e-mail and any
>> attachment and all copies and inform the sender. Thank you.
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> Mike Pokraka
> Senior Consultant
> Workflow Connections Ltd.
> Mobile: +44 (0)7786 910 855
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


Mike Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44 (0)7786 910 855


More information about the SAP-WUG mailing list