logo
search
list

Table of Content

Why the same workbook can show different CELL results
What coauthoring changes in this case
Checks that confirm the limitation
What you can do in Excel now
Excel coauthoring can make CELL() session-specific
Review shared spreadsheets with a cleaner workflow
Use WPS Office as a Free Microsoft Office Alternative
Excel CELL Results Differ Between Coauthors FAQs

Why Excel CELL Results Differ Between Coauthors

Posted by Muhammad Talha

calendar

2026-09-17

views

869

likes

4

In Excel coauthoring, CELL("row") and CELL("col") may return each user’s active selection, so shared workbooks can display different values.

Why the same workbook can show different CELL results

This issue appears in Microsoft 365 Apps for Business and Enterprise when a workbook is edited by more than one person at once. The reported setup used these formulas to identify where data was last entered, but the returned row and column changed depending on which cell another user had selected.

If data is entered in C4, the workbook should return row 4 and column 3 logic consistently for everyone viewing the sheet.

One user can see values tied to C4, while another sees values tied to their own highlighted cell such as F6.

The formula is not reliable for a shared “last edited cell” tracker during live coauthoring.

What coauthoring changes in this case

Excel showing different values to different users with CELL() function instructions and verification workflow
What coauthoring changes in this case in Excel.
Scenario User A action User B selection What each user may see
Single-user editing Enter data in C4 No second editor Consistent row and column result for one session
Live coauthoring Enter data in C4 Highlight F6 User A may see values tied to C4, while User B sees values tied to F6
Workbook logic impact Use CELL to detect “last input” Another user remains active elsewhere Results can differ by session, so the sheet no longer has one shared answer

Not a normal shared-state formula

The behavior suggests the formula can depend on each active session, not only workbook content.

Macros are not required

The same symptom was reproduced even when no VBA code or macro logic was involved.

Reproducible behavior matters

Because the issue can be repeated, it points more strongly to a product limitation or bug than random corruption.

Checks that confirm the limitation

Reproduce it in a coauthoring session

Open the same workbook in Excel for Microsoft 365 with two users signed in at the same time. Enter data in one cell, then have the second user click a different cell and compare the returned CELL("row") and CELL("col") values.

  • Expected verification: the two users can see different results simultaneously.
  • This confirms the workbook is not using one shared formula outcome for all viewers.

Rule out the earlier macro assumption

  • The earlier incident involved VBA execution, but the later test reproduced the same symptom with worksheet functions alone.
  • That means the workbook does not need edited macros to trigger the mismatch.
  • If your file behaves the same way without VBA, the practical conclusion is the same: CELL() is not dependable here for shared last-input tracking.

What you can do in Excel now

What is not supported by the evidence

  • There is no confirmed worksheet setting in the source that forces CELL("row") and CELL("col") to use one shared coauthoring state.
  • No verified formula-only fix was provided for this exact behavior in Microsoft 365 Apps for Business or Enterprise.
  • The issue may be a design limitation or a product bug tied to coauthoring.

Exact escalation path

  1. 1Ask your Microsoft 365 admin or IT team to sign in to the Microsoft 365 Admin Center.
  2. 2Open Support and select New service request.
  3. 3Describe that CELL("row") and CELL("col") return different values to different users during live coauthoring in Excel for Microsoft 365 Apps for Business/Enterprise.
  4. 4Include a reproducible sample workbook with all private data removed if your organization allows it.

Useful references: Get support - Microsoft 365 admin and How to find your Microsoft 365 admin.

Excel coauthoring can make CELL() session-specific

The evidence points to a coauthoring limitation or bug, not a simple formula typo. If different users see different row or column values at the same moment, treat CELL("row") and CELL("col") as unreliable for shared last-entry tracking and escalate through Microsoft 365 Admin Center when needed.

Review shared spreadsheets with a cleaner workflow

Use WPS to inspect formulas, compare workbook behavior outside live coauthoring, and keep your troubleshooting process simple when Excel session-specific results get confusing.

Use WPS Office as a Free Microsoft Office Alternative

WPS Writer logo
WPS Presentation logo
WPS Spreadsheets logo
WPS PDF logo
Use Word, Excel, and PPT for FREE

WPS Office cannot change Microsoft Excel’s volatile CELL function behavior during Microsoft 365 coauthoring. Complete that Microsoft-specific step in the original Microsoft application or account.

WPS Office free alternative for excel cell results differ between coauthors
Use WPS Office for compatible local office files while the Microsoft-specific issue is resolved.

You can still create, open, edit, and export compatible DOCX, XLSX, PPTX, and PDF files with Writer, Spreadsheets, Presentation, PDF tools, and WPS AI. Test macros, add-ins, protected files, and cloud-only integrations before replacing a critical workflow.

100% secure

Excel CELL Results Differ Between Coauthors FAQs

Why do two people see different CELL("row") results in the same workbook?

In the reported case, Excel appears to evaluate the function against each user’s active selection during coauthoring. That means the workbook can show session-specific results instead of one shared value.

Does this mean my VBA code is the cause?

Not necessarily. The same symptom was reproduced without VBA, so macros are not required for this issue to appear.

What is the exact Microsoft path to report this behavior?

Have your organization’s admin sign in to Microsoft 365 Admin Center, then go to Support > New service request. Include the workbook version, the coauthoring scenario, and the reproducible CELL() result mismatch.

Does this prove that the workbook’s VBA caused the problem?

No. The follow-up clarified that the later case happened with no VBA involved at all, so the mismatch cannot be blamed only on macros.

Muhammad Talha

7+ years in productivity tech. I test and review the latest tools to simplify your workflow. Follow for honest app comparisons, practical guides, and curated tech picks to boost efficiency.