Help CenterTroubleshooting

Troubleshooting: SAI Parse Error - Toggle EU/EN in Formula Builder

The Problem

You're getting a parse error when trying to use a SAI command (like #SAI...) in your spreadsheet. The formula isn't being recognized or processed correctly.

Why This Happens

Parse errors can occur due to regional number format differences. SheetXAI supports both:

  • EN (English): Uses periods (.) for decimals and commas (,) for thousands
  • EU (European): Uses commas (,) for decimals and periods (.) for thousands

If your spreadsheet or system uses a different number format than what SheetXAI is currently set to, you may encounter parse errors.

How to Fix It

Step 1: Open the Formula Builder

  1. Click the ⨍ (function) icon above the chatbox in the SheetXAI sidebar
    • This is the Formula Builder icon
    • It appears as a function symbol (⨍) above the chat input area

Step 2: Scroll to the Bottom

  1. Scroll down in the Formula Builder panel
  2. Look for the En/EU toggle at the bottom of the page
  3. You'll see options for En (English) and EU (European)

Step 3: Toggle the Setting

  1. Click to toggle from En to EU (or vice versa)
    • If you're currently on En, switch to EU
    • If you're currently on EU, switch to En

Step 4: Try Your Command Again

  1. Close the Formula Builder (or leave it open)
  2. Go to a new cell in your spreadsheet
  3. Try your SAI command again (e.g., #SAI...)
  4. Check if the parse error is resolved

Quick Checklist

  • Opened Formula Builder (⨍ icon above chatbox)
  • Scrolled to bottom of Formula Builder
  • Found En/EU toggle
  • Toggled from current setting to the other (En ↔ EU)
  • Tried the SAI command in a new cell
  • Verified the parse error is resolved

When to Use This Fix

Use this solution when:

  • You get parse errors with SAI formulas
  • Formulas work in some regions but not others
  • You're working with spreadsheets that use different number formats
  • SAI commands aren't being recognized correctly

Still Not Working?

If toggling EU/EN doesn't resolve the parse error, try:

Last updated on 2025-01-12