Volatile function error for SharePoint calculated field current date

 

Today's Issue: Volatile function error for SharePoint calculated field current date

While creating calculated column to find date difference, I encountered this error. Here I have provided the resolution to fix it,

  1. Create a new column called Today (Single line of text).
  2. Create a calculated column, name it anything you want, say 'CurrentDate'.
  3. In the formula, insert the column you created previously 'Today'.
  4. Set the data type to 'Date and Time'.
  5. Set the Date and Time format to 'Date Only'. You can even select Date & Time if you would want to use hours/minutes as well.
  6. Now delete the 'Today' column you created in first step. Don't worry, just go ahead.
  7. Add the 'CurrentDate' column to your view and check the value.
  8. You should see today's date in there.
  9. Modify the formula as required, you can use the column Today just like the function [Today] without any issues.
Same approach could also be used for [Me], if there is a need for calculated column that involves it.

Comments

Post a Comment

Popular posts from this blog

Power BI Refresh Issue: unable to convert the value '' from the source data type 'VT_BSTR' to the expected data type 'VT_I8.

Image
While scheduling refresh in Power BI, you might get below error . Issue: Unable to convert the value '<pii></pii>' from the source data type 'VT_BSTR' to the expected data type 'VT_I8 .     Cause/Reason Behind: Column datatype mismatch between power bi desktop and power bi cloud report. Solution: Edit query in power bi desktop and change the data type so it’s in sync with Power BI service/cloud. Example: In my case, I have modified a column’s datatype from decimal to whole number (to display no. of days). Now power bi desktop and power bi service synced up and I could perform automatic data refresh.
Read more

Office file not working for federated authenticated sites in SharePoint (SAML authentication).

  Situation After implementing “iTrust” – SAML authentication while creating external facing sites(DMZ Area) – office files didn’t work.   Task/Analysis Microsoft Office 2016 clients use modern authentication by default. In certain configurations, modern authentication isn’t supported by the Office 2016 clients with SharePoint Server 2016, such as when it is used for Active Directory Federation Services (AD FS) 3.0 installations. SharePoint administrators can now configure SharePoint Server 2016 to suppress modern authentication in Office 2016 clients .   Action To configure SharePoint Server 2016 to suppress modern authentication in Office 2016 clients, follow these steps to run Microsoft PowerShell commands in the SharePoint 2016 Management Shell:   When you install SharePoint Server 2016, the user account from which you ran the installation is granted the appropriate permissions to run Microsoft PowerShell cmdlets. If any users have not been...
Read more