0

Data Type changes from Date to Datetime when reusing IMDB Models (blocking Multi-Select workflows)

Hello PA Team,

I'd like to report an issue with Data Type preservation that creates a blocker when using the "Multi-Select" feature in Data Flow.

The Scenario:

  1. I create a Data Model (Model A) with a column explicitly defined as Date (e.g., from a Date Range source).

  2. I create a second Data Model (Model B) and use Model A as the Source.

  3. I use the "Add as Multi-Select" option for the tables because I want to perform a direct pass-through of multiple tables.

The Problem:
When Model B reads Model A, the Date column is automatically converted/cast to Datetime.
Because I am using the "Multi-Select" node, I cannot add a "Convert Column" node to fix this back to "Date" (as Multi-Select nodes can only be connected directly to a Target).

 Impact:
This forces us to abandon the efficient "Multi-Select" feature and add tables individually just to fix a data type that should have been preserved correctly in the first place.

Proposed Solution:

  1. Ensure that the Date data type is strictly preserved when reusing In-Memory models as a source.

  2. OR: Allow basic Data Type mapping/overrides inside the Source Node properties even when "Multi-Select" is used.

Thank you.

Reply

null

Content aside

  • 3 days agoLast active
  • 7Views
  • 1 Following