Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

Invalid Expression after copying code from one BPEL to another
Problem Description
Sometime after you copy BPEL code from one BPEL to another you get error messages such as Invalid Expression, or unexpected $.

This might be due to the target BPEL having a different default expression Language to the source BPEL.​

Cause
The code being copied is based on XQuery, however it is using the default expression builder for the BPEL. If it is copied to a BPEL that has a different default expression builder (if none is defined then the default is XPath 1.0), then the code is incompatible.
Solution
This could be addressed at a process level or at an assignment level.

At Process Level

  • If you have copied chunk of code or a full BPEL and there are more than one of these errors, you probably need to change the default expression language for the BPEL.
  1. Open the BPEL.
  2. Click the background of the canvas.
  3. Go to the Properties tab.
  4. Click the All tab.
  5. Find the Expression Language.
  6. Click the Ellipsis.
  7. Select the xQuery Option and click OK.
  8. Save:
    • Your ​Expression Errors should be resolved.

At a​ Script Assignment level

  • ​If you only have One error or you do not want to change the BPEL properties, you could address this in the assignment.
  1. Open the Assignment with the error.
  2. In the Expression builder, find the Expression Language.
  3. Click the ellipsis.
  4. Select the XQuery option and click OK.
  5. Save​:
    • ​​​​The error for this a​ssignment should go away​.
More Information
Applies To
Product: Active VOS; MDM Multidomain; Product 360 (Media Manager)
Problem Type: Configuration
User Type: Developer
Project Phase: Configure
Product Version:
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:7/13/2020 2:38 AMID:621909
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)