A lobby navigation URL's $filter includes an enumeration comparison (e.g. Objstate eq $[SomeValue]), and the target page complains about a malformed filter (though closing the error and re-searching manually still returns the right data). What's wrong with the filter syntax?

All FAQ questions / Platform, Aurena, and customization

Answer

Enum values used in a $filter condition need the fully qualified enum type name, not just the bare value — write it as Namespace.Projection.EnumTypeName'Value' for a static value (e.g. IfsApp.ShipmentsHandling.ShipmentListState'Completed'), or Namespace.Projection.EnumTypeName$[Placeholder] when passing a parameter placeholder. A filter using just the bare value or placeholder without that qualified type prefix looks reasonable but isn't valid OData syntax for an enum comparison, which is why it fails as a direct navigation link even though the equivalent manual search in Advanced Search still works.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions