Skip to main content

Async Plugins vs. Power Automate Flows

How to correctly display a SPFieldCalculated with datatype DateTime

In this blog I want to talk about my recent experiences with displaying values from a SPFieldCalculated field with datatype "DateTime" in another Web control (asp textbox or label).

My first approach was this:

// Get calculated due date field values and set them in the textboxes
SPFieldCalculated cf3Due = (SPFieldCalculated)SPContext.Current.ListItem.Fields["Due date"];

DueDateField.Text = cf3Due.GetFieldValueAsText(SPContext.Current.ListItem["Due_x0020_date"]);

Later I figured out that using the first approach will not correctly apply timezone and region settings to the current datetime values.

My next approach solved my issue with displaying the right datetime in the right timezone. But it took me several hours to find out this freaking solution.

System.Globalization.CultureInfo ci = null;
SPRegionalSettings regSettings = null;
var user = SPContext.Current.Web.CurrentUser;
// Always perform a Null-Check on SPUser.RegionalSettings
if (user.RegionalSettings != null)
{
    regSettings = user.RegionalSettings;
    ci = System.Globalization.CultureInfo.GetCultureInfo((int)user.RegionalSettings.LocaleId);
}
else
{
    // User didn't set a time zone, so use the one from the Web
    regSettings = SPContext.Current.Web.RegionalSettings;
    ci = System.Globalization.CultureInfo.GetCultureInfo((int)SPContext.Current.Web.RegionalSettings.LocaleId);
}

string[] calculatedFieldParts = ((string)SPContext.Current.ListItem["Due_x0020_date"]).Split(';');

//strip leading # from value
string fieldValue = calculatedFieldParts[1].Remove(0, 1);

DueDateField.Text = Microsoft.SharePoint.Utilities.SPUtility.FormatDate(SPContext.Current.Web, regSettings.TimeZone.LocalTimeToUTC(System.Convert.ToDateTime(fieldValue)), Microsoft.SharePoint.Utilities.SPDateFormat.DateTime);
I don't know if this is actually an ideal approach, but it seems to work well in my in our customer's enviroment. If you know a better way to do this please leave a quick comment on this topic.

Comments

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...

Async Plugins vs. Power Automate Flows

Choosing Your Automation Tool Choosing the right tool for automation and business logic in the Power Platform and Dynamics 365 is crucial for building scalable, maintainable, and performant solutions. Both asynchronous plugins and Power Automate flows can execute logic in the background, but they are designed for different scenarios and user profiles. This interactive guide provides a comparative overview to help you determine the most suitable option for your specific requirements. At-a-Glance Comparison This chart provides a visual summary of the relative strengths of each tool across key decision factors. Hover over the points for more details. Interactive Criterion Explorer Sel...

CRM 2013: Translation import error: The value passed for ConditionOperator.In is empty

This week a very evil error drove me nuts. In CRM 2013 I tried to import a translation file into an organization. It always ended up with this error message: The value passed for ConditionOperator.In is empty I was like what in the world does this message mean. If an old school approach in splitting up the file into serveral smaller Import files I finally figured out that the following lines in the "Localized Labels" sheet caused this trouble: RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.ToolTip.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.ToolTip.LocLabel To resolve t...