#REF! on new Worksheet

I have created a self-marking worksheet so colleagues can answer questions and, with the use of =IF it will give 0/1/Unanswered.

I want to create a second worksheet with a different set of questions, but when I create a new worksheet, and rename it, whenever I try and reference a cell (or set of cells) from this new worksheet it returns a "#REF!" error. (See Core!L12 for example)

Original worksheet created - all working fine
Second worksheet created, Try and get Worksheet2!D4 to display in original worksheet - all working fine
Rename Worksheet2 to New, try and get New!D4 to display in Original Worksheet - #REF! is displayed

The #REF! is shown if I try and reference a single cell, a group of cells, or create a =sum pulling data from "New" onto original worksheet.

I have tried recreating "New", but as soon as I rename it, it get the error.

Hello
You have probably deleted lines in the Sheet ("Application") thus stating the reference.
In fact the reference is, in the Sheet ("Application"), to cell D4 while the value is now in cell D2

Hello,
Mario

Hi Mario
No, data was not deleted, that was just put there as test data, and even referencing to a blank cell was brining up the same issue, however, I think I may have discovered the reason - SharePoint

Hi John. Ditto.

I think I may have found the issue - SharePoint

SO, I think I may have found the issue/resolution.

The worksheet was saved to a locally saved version of my Office365 Portfolio (OneDrive). This means that, whilst I had renamed the tab, this had not replicated throughout my profile, and so Excel was being told to reference data on "New" worksheet, whilst SharePoint was telling it that the "New" worksheet was still called "Sheet2".

Once the saved file was given time to replicate to Office 365, and therefore update the SharePoint version, all referencing worked without fault.

Strange, as the file was created on my local portfolio. Edited in my local portfolio, and resaved on my local portfolio. Wouldn't have thought that SharePoint replication time (local - Office365) would have had any bearing on it, but there you go.