DV OData4 URL validation or parsing error with a multi-column key

Solution Verified - Updated -


  • Accessing JDV table via OData4 through Salesforce connect with multi key and salesforce engine is creating the OData calls. Whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter=%20ColumnA%20eq%20123%20and%20ColumnB%20eq.... The first space right after the $filter= throws off the DV engine as it thinks it's a malformed URL but OData2 accepts it


  • Red Hat JBoss Data Virtualization (DV) 6.3
  • DV OData4 Olingo connection

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content