Check Named Ranges Between PlanMaker and Excel

Keep an untouched master, save a separate XLSX exchange copy, and test named formulas in both programs. Opening a workbook successfully does not prove its names still resolve to the intended cells or that its results are live.

Choose a format for the job

PlanMaker 2026 documents PMDX as its native document format and PMVX for templates. It can open and save XLSX and supported XLS formats; some older formats are import-only. Use File → Save as → Save as type to choose the actual format, rather than simply changing a filename extension. See supported file formats.

For editable exchange with current desktop Excel, use XLSX for this test. CSV/TSV is a flat data format and does not preserve named ranges, multiple sheets, formulas as a working model, or formatting. PDF is useful for reading/printing, not for testing editable names. Do not assume ODS or every other import/export route has the same capabilities.

This walkthrough covers documented PlanMaker 2026 desktop controls and Microsoft’s current Excel Name Manager guidance for listed desktop versions including Microsoft 365 and Excel 2024. It is not proof of compatibility with every Excel version, mobile product, FreeOffice edition, or unusual workbook feature.

Make a small reference workbook

Create a sheet named Sales. Enter January sales in A1, then these nine synthetic values in A2:A10:

100, 120, 80, 90, 110, 100, 130, 70, 100

The expected sum is 900. A plain CSV of these values is available, but it contains no named-range definition. After opening it, save the working workbook as names-master.pmdx and confirm the sheet name is Sales.

1. Select Sales!A2:A10.
2. Choose Formula → Named areas → Edit names.
3. Enter January in the Name field and click Add. Check the range assigned to it.
4. In C2 enter =SUM(January). In C3 enter =SUM(A2:A10). Both should return 900.
5. Add a second sheet named Report and enter =SUM(January) in B2. Check that this also returns 900 before continuing.

The intended test is one unique name referring to the same nine Sales cells from both sheets. If that baseline does not work, fix it before exporting. See assigning names, using names, and the SUM guide.

Write down what must survive

Keep a short checklist outside the exchange workbook:

Check	Expected baseline
Name	January
Referenced sheet and cells	Sales, absolute A2:A10
Sales!C2 named formula	SUM of January, 900
Sales!C3 address formula	SUM of A2:A10, 900
Report!B2 named formula	SUM of January, 900
External workbook dependency	None in this practice model

Choose unique names without spaces or cell-reference-like spellings. In a real workbook, inventory duplicate names and their intended worksheet/workbook scope separately. This simple test does not prove preservation of every locally scoped, hidden, dynamic, or externally linked name.

Check the outbound XLSX in Excel

1. Save names-exchange.xlsx using PlanMaker’s XLSX file type. Keep the PMDX master untouched. Read any conversion warning rather than dismissing it.
2. Open the copy in the intended desktop Excel version. Go to Formulas → Defined Names → Name Manager.
3. Inspect January, its Refers To range and Scope. The intended workbook-wide name should point to Sales!$A$2:$A$10, not an external file or a truncated range. Verify both sheets’ formulas.
4. Change Sales!A10 from 100 to 125. The three totals should become 925.
5. Save as names-returned.xlsx and close it.

Microsoft’s Name Manager documentation explains the Refers To and Scope columns. If the scope differs from your intended baseline, stop and resolve it in a copy. Do not create a duplicate January name just to hide a failing formula.

Verify the returned copy in PlanMaker

Open names-returned.xlsx in PlanMaker. Inspect Edit names, select January from the name box, and check that the selected cells are still Sales!A2:A10. Confirm all three totals are 925, then change A2 from 100 to 110 and verify they become 935. This second edit checks recalculation rather than merely reading a stored result.

Record both program versions and the test outcome. If the returned file fails, retain both exchange copies and the untouched master so you can identify where the change occurred. Do not replace the original workbook until the receiving application has passed the required checks.

Conversion warnings and wider integrity checks

PlanMaker’s Excel-file guidance recommends View → Syntax highlighting to find incompatible formulas after an import/export warning. Compare them with the source and revise a copy. An absence of warnings is not a blanket round-trip guarantee.

For real files also inspect dates, percentages, currencies, merged cells, charts, validation, conditional formatting, comments, hidden content, print settings and protection. Check external-reference paths and freshness separately; a correct cached result can conceal an inaccessible source. Macros/scripts and newer functions need their own compatibility review. A named range passing this fixture says nothing about those unrelated features.

Testing note: The totals 900, 925 and 935 were independently calculated. The PlanMaker and Excel controls were checked against official documentation, but this cross-application round trip was not tested in either application. No finished compatibility certification or screenshots are claimed.

Related import and compatibility guides

• Import CSV data while preserving leading zeros
• Check ODS file compatibility