SETFILTER issue with special characters in Business Central

Why SETFILTER doesn’t work sometimes

Daniel Gorski
Daniel Gorski 04. Mai 2023
1 Min. Lesezeit

Every AL-Developer uses “SETFILTER” on a daily basis. But did you know that there are certain situations where “SETFILTER” will refuse to work?

First let’s look at the syntax:

Rec.SETFILTER(<Field>, <Filter>, <Placeholders>);

Seems simple enough right?

This will work just fine. But what happens if we do the following?

The applied filter will look like this:

AL did not manage to replace the placeholders inside the filter string, because “*” and “@” are used.

To make this work, we must use “STRSUBSTNO”:

STRSUBSTNO('<Filter>', <Values>)

That way, we construct the filter-text by ourselves and pass it into the filter string of the SETFILTER function. The result will look like this:

how-to
development
business central
setfilter
al code
troubleshooting
development tips
Azure Communication Services SMTP with Scanner

Using Azure Communication Services SMTP with Your Scanner or Printer

Need to send scans via email from your office scanner? Azure Communication Services provides a reliable SMTP relay that works with any device supporting SMTP au

Weiter lesen
Weiter lesen
XRechnung Einrichtung in Business Central

XRechnung in Business Central einrichten: Schritt für Schritt zur E-Rechnung

Ab 2025 wird die E-Rechnung im B2B-Bereich in Deutschland Pflicht. Wir zeigen Ihnen, wie Sie XRechnung in Business Central einrichten – mit E-Beleg-Dienst, Work

Weiter lesen
Weiter lesen