---
schema_version: "1"
id: a89b776cae08f2b5d2f9ee8b527a13a2bce5205ec8fcb2470b9e29bd836e6ca0
title: Use New Behaviors in More Tableau Semantics Functions (Release Update)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_tua_functions_regex_number.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_tua_functions_regex_number.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a16107ba281acc7fe836b0b20807b3453b50887a5ac093b9852b76f3fb52a42a
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Use New Behaviors in More Tableau Semantics Functions (Release Update)

Certain number functions (ASIN, POWER, ACOS, LOG, COT, and LN), if given invalid input, return a query failure rather than return Null. In addition, Regex functions use the RE2 library rather than ICU. Check existing content to see if you must take action to prevent breaking changes before these updates are released.

**Where:** This change applies to Tableau Next in Enterprise, Performance, and Unlimited editions.

**When:** Salesforce enforces this update in March 2026. To get the major release upgrade date for your instance, go to [Trust Status](https://status.salesforce.com/), search for your instance, and click the maintenance tab.

**Why:** These changes ensure data integrity and improve performance.

**How:** Calculations that use invalid inputs cause query failures (number functions) or different handling of certain regex functions. Review existing calculated fields to prevent breaking changes.

**Updated number functions**

- ASIN, POWER, ACOS, LOG, COT, and LN
    - Previously: Invalid input returns Null
    - Now: Query failure

**Updated regex functions**

Empty string handling. The RE2 engine handles empty strings and "zero-width" matches differently than the previous library. In RE2, an empty pattern is considered a match at every possible position (including the start of the string).

Updated Regex Functions   
| Calculation | Old Behavior (ICU) | New Behavior (RE2) |
| --- | --- | --- |
| REGEXP\_REPLACE('', '()', 'newstring') | '' (i.e. empty string) | 'newstring' |
| REGEXP\_REPLACE('', '', 'newstring') | '' (i.e. empty) | 'newstring' |
| REGEXP\_REPLACE('tableau', '', 'replace') | 'tableau' | 'replacetableau' |
| REGEXP\_MATCH('string', '') | FALSE | TRUE |

**Unsupported syntax**

RE2 prioritizes speed and security by excluding features that require complex backtracking. If your current calculated fields use the following syntax, they will need to be modified to not use the syntax in this table.

Unsupported Syntax   
| Feature | Unsupported Syntax Example | Description |
| --- | --- | --- |
| Backreferences | (abc)\\1 | Referencing a previously captured group within the same regex. |
| Lookahead | (?=...) or (?!...) | Checking if a pattern exists (or doesn't) ahead of the current position without "consuming" characters. |
| Lookbehind | (?<=...) or (?<!...) | Checking if a pattern exists (or doesn't) behind the current position. |
| Possessive Quantifiers | .\*+ or \[0-9\]++ | Quantifiers that do not allow the engine to "backtrack" if a match fails. |

**Improved Error Handling for DATEPARSE Function**

If you have existing calculations with invalid date strings, DATEPARSE returns a query error for invalid inputs instead of a Null value.

#### See Also

- [_Google Help_: Calculated Field Formula Functions](https://github.com/google/re2/wiki/Syntax)
- [_ICU Documentation_: Regular Expressions](https://unicode-org.github.io/icu/userguide/strings/regexp.html)