Constructing an IEE external-search URL (used to open a specific form and pre-populate it with data from an external application/link) so it jumps to a specific record — for example, one particular Receipt line number rather than always landing on the first line — the URL follows the documented ifsapf: search syntax but consistently opens the wrong line.

All FAQ questions / Integrations and APIs

Answer

The most common cause is the URL not being properly percent-encoded — external-search URLs need special characters within the embedded search string (colons, question marks, equals signs, ampersands, and so on) percent-encoded according to standard URL encoding rules, per IFS's own external-search development documentation. A URL built with those characters left as literal, unencoded text often still loads the target form but silently fails to apply the specific filter values correctly (commonly defaulting to the first matching record), which is exactly the 'always opens line 1' symptom. Running your constructed search string through a standard URL-encoding tool (setting the character encoding to UTF-8) before embedding it in the final link typically resolves this.

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

← Browse Integrations and APIs questions