Skip to main content

Enhancement request: Add wildcard searching to fields in the Self-Service Portal (assystNet)

  • August 20, 2026
  • 3 replies
  • 38 views
Do Gooder (Customer)
Forum|alt.badge.img
  • Likoe
  • Do Gooder (Customer)

A. What is your idea?

1) Classification

  • Opportunity for improvement

2) Brief description

Despite allowing wildcard searching in the assyst portal for lookup fields (Items, Contact users, Buildings, etc.), this same feature is missing in the Self-Service Portal.

 

As a result, searching in lookup fields on the Self-Service Portal is robust and nonintuitive for our users. The expected behaviour is that wildcard searching is available in lookup fields on both assyst and the Self-Service Portal.

B. Context and scope

1) Who is affected?

  • Internal users
  • Customers

2) Frequency

  • Daily

C. Value and impact

1) What is the business outcome?

  • Improves productivity or efficiency
  • Enhances user experience
  • Enables new capability

2) Impact scale

  • 5 — Enterprise-wide

3) Workaround
No workaround

D. Evidence and examples

Actual result:

Expected result:

E. Additional details

1) Enter support ticket ID reference (If applicable)

503753

2) Would you like to participate in validation or early testing?

Yes

3 replies

Hero (Employee)
Forum|alt.badge.img+7

Hi

The message you see above indicates an error searching, not missing results. On 26 R1 if I try your test case using percent character in the middle of a phrase I successfully get results.

I wonder if you maybe have an invalid lookup filter expression on the above lookup? Might be worth contacting our support team to have this investigated. 

Alan 

    Do Gooder (Customer)
    Forum|alt.badge.img
    • Likoe
    • Author
    • Do Gooder (Customer)
    • August 20, 2026

    Hi

    The message you see above indicates an error searching, not missing results. On 26 R1 if I try your test case using percent character in the middle of a phrase I successfully get results.

    I wonder if you maybe have an invalid lookup filter expression on the above lookup? Might be worth contacting our support team to have this investigated. 

    Alan 

    Hi Alan,

     

    The lookup in the example above is the standard “Affected User” field with no customization added.

     

    We inquired with the support team about this issue and received the following information: “wildcard searching in contact user lookups is no longer supported in the Self-Service Portal”

     

    We are using assyst version 11.7.4, but it would appear this feature has been potentially introduced in later versions of the tool (contrary to the statement we received).

     

    Thank you for the reply.

    Evan

    Do Gooder (Customer)
    Forum|alt.badge.img+6
    • Jeremias
    • Do Gooder (Customer)
    • August 21, 2026

    Hey,

    I tested the search using the “%” wildcard for the affected user on our end, and it seems to work for us. However, we're running version 25R2 SU4. Maybe it's a bug in an older version of Assyst?

    Or please check if the name really does start with “Evan” on your end. On our end, names start with the last name. So you might need to add a placeholder at the beginning as well.

    Best regards!
    Jeremias

     

    Terms & ConditionsAccessibility statement