[Bug]: Subscription Billing - procedure ReplaceInvalidFilterChar does not handle equal ('=') char and causing invalid filter error for Subscription Packages

[anjajanic]

Describe the issue

When a Subscription Package Code contains the equal ('=') character, creating a subscription for an item that uses this package fails with an invalid filter error.

The root cause is that procedure ReplaceInvalidFilterChar() in codeunit 8021 "Text Management" only replaces (), <>, but does not handle '=' even though it is also treated as an invalid/special filter character. This leads to filters like 'INVALID=' being passed directly into SETFILTER, which then fails.

Expected behavior

Creating a subscription and using a Subscription Package whose Code contains = should work without an error, even if the code includes special characters.

The helper function that prepares filter text should handle = in the same way as the other invalid/special filter characters, so that the resulting filter is valid.

Steps to reproduce

1. Create Subscription Item
2. Create Subscription Package with equal char ('=') in Code (example: "INVALID=")
3. Assign the corresponding subscription package to Subscription Item
4. Create new Subscription with that Item
5. Error is expected 'The filter "INVALID=" is not valid for the Code field on the Item Subscription Package table. An error occurred while interpreting the filter: Did not expect '='.'

Additional context

No response

I will provide a fix for a bug

• I will provide a fix for a bug