March 2024

What's New

Identify the Requests you want to roll forward.
Identify the Ranges and Table names you want to move.
Design and upload your new DataFlow template.
Open the template design tool.
Follow the guidelines given in the DataFlow documentation to create your new template.
Save the template and upload it to the system through the upload interface.
Create the mapping file.
Select the Requests to roll forward
Select the requests you identified earlier.
Ensure that for multiple selections, the Template Name and version match.
Verify that the entity is available in the new DataFlow; otherwise, the request can't be rolled.
Select the New Properties for the Request.
Upload the mapping file and validate.
Go to the Data Mapping section and upload your mapping file.
Select Validate to check the mapping file for any errors or inconsistencies.
Select Next when you're finished.
Assign users and set a due date.
Select Finish when you're done.
Locate the created Request in the new DataFlow listed among the others.

Input name – copy this single value directly to the Request in the new DataFlow.
Block name – copy data from a named block (RangeNameBase.block) to either:
DCRange
Table
Wildcard name – use a wildcard range name to identify and move a group of data. Append the wildcard name with .0000, for example, “WildcardName.0000”. Copy wildcard data to:
DCRange
A column in a Table
The Destination specifies the Table name.
Leave SourceCol blank.
Specify the Header column of DestCol.
Repeating name – designate a repeating range of data with a name appended with .000, for example, “RepeatingName.000”. Move repeating data to:
DCRange
A column in a Table
Table Name – specify a DFTBL name in DataFlow Classic to copy data from.
To copy the entire table:
Leave SourceCol blank
Leave DestCol blank
Copy column to column
The DESTINATION column may include:
Input name – a single location for the source value.
Range name – a Range in DataFlow Next Gen for the source data.
Table name – a destination table for the source data.
The SourceCol column:
Specifies the header of the DFTBL column you want to move.
Requires one row for each header column you wish to copy.
Is optional if you are not working with tables.
The DestCol column:
Specifies the header of the column where you will place the data.
Requires one row for each header column you want to copy.
Is necessary when moving data from:
A DFTBL to a column in the new DataFlow Table.
A wildcard to a column in a Table.
A repeating range to a column in a Table.

Identify your DataFlow Classic Request identifiers (such as entities, period, and code) and create them in the new DataFlow to continue using them.
Ensure the entity exists; otherwise, the Request won't roll forward.
Select a new value for
Year
or
Period
to roll forward.
Save the mapping file as XLSX.
You may map a data type only as follows:
Input to input
Block to DCRange
Block to Table
Wildcard to DCRange
Wildcard to Table (to a specific column header)
Repeating to DCRange
Repeating to Table (to a specific column header)
DFTBL to Table
DFTBL to Table, column to column
Any unlocked destination will be overwritten, regardless of content.
Blank values will roll forward and overwrite populated locations when unlocked.
Avoid duplicate destinations as the results will be unpredictable.
Use identifiable Column names to ensure data transfer.
The Add Rows feature is required in the Destination to match the Source size to prevent truncating data if the Destination size is smaller than the Source.
The system maintains the order of the data in a table in the destination.
The system maintains blank values in a column of a table in the destination.
NoSave
type Wildcards won't be rolled over, as their data isn't saved.

Closed issues

Fixed a bug that prevented loading locally saved XML files.
The request grid now retains your page size preferences.
Corrected the Refresh Data Hub button functionality in Web DataFlow.