# Why sharePoint online is not saving my calculated column formula

300 Reputation points
2024-08-24T23:37:15.9466667+00:00

I have created a calculated column of type Date/time with this formula:-

=IF([DueDateTime]="12:00 AM", [DueDate],
IF([DueDateTime]="1:00 AM", [DueDate] + 60/(24*60),
IF([DueDateTime]="2:00 AM", [DueDate] + 120/(24*60),
IF([DueDateTime]="3:00 AM", [DueDate] + 180/(24*60),
IF([DueDateTime]="4:00 AM", [DueDate] + 240/(24*60),
IF([DueDateTime]="5:00 AM", [DueDate] + 300/(24*60),
IF([DueDateTime]="6:00 AM", [DueDate] + 360/(24*60),
IF([DueDateTime]="7:00 AM", [DueDate] + 420/(24*60),
IF([DueDateTime]="8:00 AM", [DueDate] + 480/(24*60),
IF([DueDateTime]="9:00 AM", [DueDate] + 540/(24*60),
IF([DueDateTime]="10:00 AM", [DueDate] + 600/(24*60),
IF([DueDateTime]="11:00 AM", [DueDate] + 660/(24*60),
[DueDate]))))))))))))

but when i try to apply this formula to the site column i will get this message forever:-

and the formula will not get applied to the list column and hence to the list.. any advice? i read that in sharepoint online we can only have 19 nested If statements inside calculated columns, but in my case i only have 12.. so why this is not working?

SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
10,631 questions
SharePoint Development
SharePoint Development
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Development: The process of researching, productizing, and refining new or existing technologies.
2,904 questions

1. 16,665 Reputation points Microsoft Vendor
2024-08-26T07:44:43.05+00:00

Hi @john john Pter,

Thank you for posting in this community.

I tested your formula in my environment but I was able to save it successfully. There is no problem with your formula.

But I ran into another issue where the calculated column doesn't show up in the list even though it calculates the value of the date.

This is most likely an issue that arose with a recent update to SharePoint, so I suggest you open a ticket for it.