How to Convert Date & Time to Cvent Format in Workfront Fusion - 2025-06-07T06:25:00.000Z

 Introduction

When working with APIs or third-party systems in Workfront Fusion, you often need to send date and time in a specific format.

If the format is wrong, your API call may fail.
So let’s understand this in a very simple way

What is Cvent Format?

Cvent format looks like this:

2025-06-07T06:25:00.000Z

This may look complicated, but it’s actually very simple when broken down.

Understanding the Format

YYYY-MM-DDTHH:mm:ss.SSSZ

Each part means:

  • YYYY → Year (e.g., 2025)
  • MM → Month (01 = Jan, 02 = Feb, etc.)
  • DD → Day (e.g., 07)
  • T → Separator between date and time
  • HH → Hour (24-hour format)
  • mm → Minutes
  • ss → Seconds
  • SSS → Milliseconds
  • Z → Time zone (UTC)

Example

2025-06-07T06:25:00.000Z

Means:

  • Date → 7th June 2025
  • Time → 06:25 AM
  • Timezone → UTC

 

How to Generate This in Workfront Fusion

Use this simple expression:

{{formatDate(now; "YYYY-MM-DDTHH:mm:ss.SSS[Z]")}}

 

Important Points

  • Always use capital letters for format (YYYY, MM, DD, etc.)
  • Use T exactly as shown (it’s mandatory)
  • Put Z inside square brackets → [Z]
  • Time is always in 24-hour format

Comments

Post a Comment

Popular posts from this blog

REST API Calls with Query Parameters in BizTalk: A Step-by-Step Guide

Image
 Introduction In this blog, I will provide a comprehensive guide on how to call a REST API that requires query parameters. We'll walk through the necessary steps to set up the environment and make successful API calls. Solution High Level Steps 1. API Overview: We will be using an open API for demonstration purposes. The API endpoint we'll be working with is: https://randomuser.me/api/?results=1 2. Schema Creation: Create a schema named "SourceA" that matches the structure of the messages you'll be dropping in the receive location. To create a JSON response schema, follow these steps: capture the JSON response by running a test in Postman, and then utilize a JSON schema generator to create the desired JSON schema. 3. Field Promotion: In the SourceA schema, promote the field called "results." This field will serve as the variable for the query parameter. 4. Receive JSON Pipeline: Develop a receive JSON pipeline that can receive JSON messages and convert t...
Read more

Error: Number of included segments do not match

Introduction In this blog, we tackle a crucial issue encountered during the reprocessing of an X12 EDI message. We will get into the root cause of the problem and provide you with a solution to overcome it. Error: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:       Error encountered during parsing. The X12 transaction set with id '103465910' contained in functional group with id '02', in interchange with id '000000009', with sender id '4532345856     ', receiver id '8038025150     ' is being suspended with following errors: Error: 1 (Miscellaneous error) 4: Number of included segments do not match . The sequence number of the suspended message is 1.  Root Cause: The issue stems from a mismatch in the number of se...
Read more

Updating BizTalk SSO DB using BTDF and a simple BTDF deployment

Image
Introduction In some cases, it becomes important to securely store key-value pairs, such as configuration data (e.g., usernames and passwords), rather than hardcoding them within a BizTalk orchestration. One effective way to achieve this is by storing these key-value pairs securely in the BizTalk SSO (Enterprise Single Sign-On) database and subsequently reading these values within our orchestration through a simple line of code within a BizTalk expression shape. In this blog post, we will go through the steps to add key-value pairs to the SSO database using the BizTalk Deployment Framework (BTDF). We will also explore how to read these values within a BizTalk orchestration and perform a simple BizTalk deployment using BTDF. Steps Creating a BizTalk Solution, Schema Project and Map project: Let's first create a BizTalk Solution called "SSOPOC" and a project called "SSOPOC.Schema". For this, you need to go to Visual Studio and click on File --> New Project --...
Read more