A Report Rule's Messages/email-body field needs to include a formatted URL (e.g. a deep link to a Customer Order), but IFS Cloud URLs contain semicolons — and the Report Rule engine treats a semicolon as a property separator, so the rule either fails to save or the encoded %3B breaks the link. Is there a way to escape a semicolon in a Report Rule?

All FAQ questions / Reporting and analytics

Answer

No — this is a genuine limitation, not a syntax mistake: Report Rules use the semicolon character to separate their own internal properties, so there's no way to include a literal (or encoded) semicolon in a rule's field value that survives intact. The practical workaround is to move the URL-building logic out of the Report Rule entirely — add a custom field to the entity the report is based on, populate it (via a customization) with the fully-formed URL including its semicolons, and reference that custom field in the Report Rule's message instead of trying to construct the URL inline.

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

← Browse Reporting and analytics questions