Unmatching cell references

This help page describes the error message “Unmatching cell references”. If you still don’t understand what to do after reading this page, please contact Client Services.

When you upload a wrap template to your wrapsite, you may get an error message saying

Expected reference cell keys ”x’ but got reference cell keys ‘y’. The wrap template was not installed. Make the reference cell keys match or use override and try again.


In previous versions of ExcelWraps, you were not required to name cells that contained a function in the WrapLink family or their holder cells. When WrapCreator doesn’t find a cell name, it instead uses standard row/column cell references as field names for the database. This was meant to create flexibility but instead turned into a trap.

If you insert new rows above, or new columns to the left of such a cell, its row/column references change, which also changes these automatic field names for the database. The new version of the wrap template will save the same fields under new names and become unable to read frozen wraps that use the previous field names. You may be thinking you could go back to the wrap template and assign names to these cells, it still doesn’t solve the problem for the wraps that have already been frozen.

If this situation is identified during import, an error message is displayed, warning you that you risk losing data for existing wraps by importing the new wrap template. If you enable the Ignore warning for linked cell, linked cell aggregate and reference cell keys being changed when frozen instances exist when you import an updated wrap template, you will override this message and continue with the import.

If you enable this option for a wrap template that has at least one frozen wrap, you will lose data.

Avoiding this issue in the future

This problem does not appear when you use named cells that can be moved freely within the wrap since they always retain their original name. Always name your WrapLink cells and holder cells!

If you want to avoid using holder cclls, use the second-generation WrapLinks (WrapLink2 and WrapLinkAggregate2) for new projects as these do not use holder cells.


Move new rows down, new columns to the right

The problem only appears when you insert rows above or columns to the left of the cells that are referenced in the error message. It may be possible to get around the problem by editing the wrap template spreadsheet, placing the new rows below and the new columns to the right of the cells that cause the problem so that they retain their old cell references. This will ensure that the new version of the wrap template will work also with the old data.

Accept losing all the wraps

If you can accept the loss of data for all the existing wraps, e.g. during initial testing, just enable the override option described above and attempt the upload again.

Keep the wraps, lose the data

If you cannot accept the loss of the wraps, you may consider recalculating all the live wraps. This will apply the new wrap template to the old records in the database. Recalculation is a laboriously slow process and should only be initiated when there are very few live wraps, less than a thousand.

Enable the override option described above, perform the upload of the new wrap template, then request recalculation of the live wraps on the Wrapsite Administration dashboard or with MyWraps.

Create a completely new wrap template

If you cannot accept any of the previous solutions, you will have to create a completely new wrap template under a new name and save the old template and its wraps as history. Since you use a new name, the two datasets get different wrap names, avoiding any conflicts.

Remember that in reports, MyWraps allows you to append the two datasets, so you can still produce reports that include all wraps even though they technically are divided across two different wrap templates.

Contact Client Services

If the above doesn’t help you solve your problem, please contact Client Services.