How to use a Righthand with Microsoft Excel

Review a named table instead of a whole workbook

Use Righthand with Microsoft Excel to prepare an exception review from a selected workbook table. The useful result identifies the business row, source cells, and proposed correction. A cell address alone can become unreliable after sorting or inserting rows, so include the table's stable business key.

Microsoft's Excel Graph guide distinguishes workbook resources, tables, ranges, values, formulas, and session behavior. Reading displayed values does not establish that writing a proposed value will preserve the workbook's calculation logic. Keep formula and input boundaries explicit.

Define the workbook schema

Give the file link, worksheet, table name, included rows, and key column. For an illustrative inventory review, map SKU, Count date, Recorded quantity, Checked quantity, and Review note. The owner supplies the actual column names and rule for flagging discrepancies.

Inspect available Excel reads through integrations. If table or formula detail is unavailable, provide an approved export or authorize a browser review. An exported CSV loses formulas and formatting; use it for analysis without claiming full workbook inspection.

A complete example brief

At 10 AM America/Los_Angeles on Monday, review the approved InventoryCheck table in the linked workbook. Return a private discrepancy worksheet with workbook and worksheet reference, SKU, source row key, recorded and checked quantities, difference under the supplied rule, and proposed review note. Identify formula cells and duplicate SKUs. Do not edit, reorder, or delete rows. Send to me for inventory-owner review. Reconcile row counts and totals to the source table and label any formula information unavailable.

This example is illustrative. The assistant should not interpret a blank quantity as zero unless the owner explicitly defines that convention.

Define the expected result

An example row might say: “SKU example; checked quantity supplied; recorded quantity blank; comparison unresolved; owner must verify the source.” Another can show a numeric discrepancy without deciding whether a stock adjustment is appropriate.

Duplicate SKUs may represent separate locations or lots. Keep those distinguishing fields and ask the owner for the intended key. A proposal to update quantity should not overwrite a formula-driven cell or erase the evidence used for the review.

After a row moves, confirm the business key and worksheet still identify the same record before assessing any proposed correction.

Reconcile supported writes and persistence

Before later approved edits, refresh the target rows and compare their current values with the proposal. Apply only supported input-cell changes under the selected write route. Then independently reopen or reread the workbook's persisted values, because a temporary session result is not the same as a saved workbook change.

Access failures, stale exports, and concurrent edits should produce an incomplete review rather than guessed corrections. Set authority through Righthand connection permissions. Check pricing for recurring workbook support and keep inventory adjustments with the responsible owner.