Passing Pipeline Trigger Time to Data Flows in Azure Data Factory: Use Strings, Not Timestamps!
When working with Azure Data Factory (ADF) and the Dataverse connector , passing the pipeline trigger time into a Data Flow can be trickier than expected. The Scenario You want to pass the pipeline’s trigger time—using the @pipeline().TriggerTime system variable—into a Data Flow. This is often needed for auditing, filtering, or other time-based logic. The catch? You’re using Dataverse , which communicates over the Web API and handles datetime values as strings . The Common Mistake In Azure Data Factory, you might instinctively define the Data Flow parameter as a timestamp or date type. But ADF doesn’t have a dedicated datetime type—only date and timestamp . So you choose one of those, thinking it aligns with your goal. Then you hit an error. And to make matters worse, the error message doesn’t clearly explain the real issue—it can be vague or misleading, which only adds to the confusion. This tripped me up for a while, as I assumed the problem was elsewhere. The Solution...