Fix Excel Adding an @ Symbol Before XLOOKUP Formulas
Question details
The user needs to understand and resolve an issue where an @ symbol is automatically inserted into an XLOOKUP formula (appearing as @=XLOOKUP or =@XLOOKUP) when the workbook is opened on a different computer.
- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Sharing or opening an Excel workbook containing XLOOKUP formulas on a different computer with a potentially different software version.
- Observed behavior
- The formula changes from =XLOOKUP(...) to include an @ symbol, caused by implicit intersection behavior or differences in Excel versions between the two computers.
Ensure both computers are running an updated version of their spreadsheet software that fully supports dynamic arrays and the XLOOKUP function. It is recommended to save a backup copy of your workbook before modifying legacy formulas.
Verify Excel Version and Dynamic Array Support
Determine if the receiving computer is using an older version of Excel that does not fully support XLOOKUP or dynamic arrays, which triggers the implicit intersection operator (@).
The @ symbol is Excel's implicit intersection operator. It is automatically added to older formulas when opened in newer versions of Excel, or vice-versa, to ensure backward compatibility for formulas that might return an array of values but were only designed to display a single value.
Launch Excel on the computer experiencing the @ symbol issue. Click on "File" in the top-left corner and select "Account" (or "Help" in older versions) from the menu.
Look under "Product Information" to see your version. XLOOKUP requires Microsoft 365, Excel 2021, or newer to function properly.
If the installed version is older (e.g., Excel 2016 or 2019), the @ symbol is added because the software does not support dynamic arrays natively. Update your Office suite to the latest version to resolve this natively.
Manually Remove the Implicit Intersection Operator
If both computers have compatible versions but the @ symbol persists due to legacy array formatting or file conversion, you can manually remove it.
Use WPS Office for Seamless XLOOKUP Compatibility
Avoid frustrating implicit intersection errors and version compatibility issues. WPS Spreadsheet offers full native support for XLOOKUP and dynamic arrays, ensuring your formulas work perfectly across all your devices without unwanted @ symbols.
- 1. Download WPS Office: Download and install the free WPS Office suite on your computer.
- 2. Open Your Spreadsheet: Open your .xlsx file directly in WPS Spreadsheet. There is no need to convert the file format.
- 3. Use XLOOKUP Seamlessly: Type or view your =XLOOKUP formulas normally. WPS handles dynamic arrays automatically without adding legacy @ operators.

Frequently Asked Questions
What does the @ symbol mean in an Excel formula?
The @ symbol is the implicit intersection operator. It ensures that a formula returns a single value rather than an array. This was the default hidden behavior in older versions of Excel before dynamic arrays were introduced, but newer versions display the @ to show explicitly where implicit intersection is happening.
Why does my XLOOKUP formula show a #NAME? error?
If the receiving computer uses an older version of Excel (like Excel 2016 or 2019), it does not recognize the newer XLOOKUP function, resulting in a #NAME? error. To fix this, you must upgrade the software, use WPS Office, or rewrite the formula using the older INDEX and MATCH functions.
Can I prevent Excel from adding the @ symbol automatically?
Excel automatically adds the @ symbol for backward compatibility when an array formula is authored in a way that implies a single value. Saving the file in a modern format on an updated version usually prevents this. You can also rewrite the formula to explicitly handle arrays using modern functions.
Does WPS Office support the XLOOKUP function?
Yes, WPS Office fully supports XLOOKUP and dynamic arrays. You can seamlessly open, edit, and share workbooks created in newer versions of Microsoft Excel without worrying about unsupported function errors.




