This guide walks you through sharepoint document issues using Microsoft-supported steps first, with WPS only where it genuinely helps.
Problem Description: Determine If Multilookup Field
I am trying to fix the json view formatting that seems to have changed for multilookup columns, and my json works fine if there are multiple items in the lookup column, but if it's only a single lookup item in that column, the forEach portion of the formatting json breaks and debug mode reports that ```json Failure: @currentField is not an array, array expected in the expression choiceIterator in @currentField ``` However, it only reports this for rows when 1 lookup item is selected in that column, for rows where multiple lookup items are selected in that same column then it renders correctly as it always has. What am I supposed to do here? I can test the length and it reports the length correctly as if it's an array and not a string, but I cannot use this value in the iterator because SharePoint treats it as not an array. I didn't always have this problem with the formatting json, but a user recently brought it to my attention that values were missing, and after digging into it and enabling debugMode, I discovered the lookup column actually has values in it, but any row with 1 lookup value in the field would fail to render that field. I'm not sure what I'm supposed to do here since I cannot find a way to use a condition in the forEach attribute, and I don't really understand the point of this change to begin with, it makes custom json view formatting that much more cumbersome to deal with Is there a correct way to handle multilookup columns to test the value types that @currentField is passing to the iterator?
Quick Answer for Office Setup on New Device
When working with SharePoint JSON formatting, recognize that Multi-Lookup columns return arrays only when multiple items are selected, while a single selection is passed as an object, causing forEach loops to fail.
Likely Causes Behind SharePoint Document Issues Root Factors
The Microsoft account or license context may not match the purchase or device.
Cached credentials, outdated builds, or damaged local components can trigger sharepoint document issues.
A file-specific corruption or add-in conflict can mimic a broader application failure.
Recommended Solution: Installing Office on a New PC
When to use this: Apply these steps when the symptoms match and you can access the relevant Microsoft account or administrator.
To resolve this, stop using @currentField within the forEach property and instead reference the column directly by its internal name.
Validate your JSON syntax against Microsoft documentation standards, and always perform a complete backup of your source code and configuration files before implementing any formatting adjustments to allow for immediate rollback if unexpected errors occur during deployment.
Alternative Solutions for Secondary Document Fixes
Retry the Microsoft-side steps after restarting the app and device.
Test the same action in a private browser session or a new blank file to isolate account vs file issues.
Capture exact error text and screenshots before contacting Microsoft Support or your administrator.
Working with WPS Office: WPS as a Local Alternative

WPS Office cannot replace Microsoft account, activation, or cloud fixes for this scenario. It remains one of the best free Microsoft Office-compatible alternatives for opening and editing local files.
Download and install WPS Office from the official website.
Open local Word, Excel, PowerPoint, or PDF files in the matching WPS app.
Save a working copy locally while Microsoft-side issues are resolved.
Return to Microsoft Office after the primary fix succeeds.
If you need a practical local workspace in the meantime, try WPS Office.
Prevention Tips for Keeping Office Stable Long Term
Keep one primary Microsoft account for subscriptions and Office sign-in.
Install updates for Office and Windows before retrying failed workflows.
Back up important files before repair, reset, or reinstall actions.
Work on copies and keep version history enabled when available.
FAQs About Office Support Questions
Can WPS Office fix this sharepoint document issues issue directly? Only when the WPS steps match the formatting or file task. Account, activation, and cloud issues stay on the Microsoft side.
Should I reinstall Office before trying these steps? Not first. Confirm account, license, and the exact error before reinstalling.
What should I send to Microsoft Support? The affected account email, device type, Office version, exact error text, and screenshots with personal data hidden.




