What is changing?
- For some customers, the date format in some of your Data Studio datasets is changing from short string format (ex: 9/13/2020 4:01:54 PM) to ISO format (ex: 2020-09-13T16:01:54.9930000Z).
- Unnecessary fields, which have no value to Data Studio users, will be removed.
- The version of the affected datasets will increase to v2.0.
- The affected datasets will be backfilled for version v2.0. That means historical data before 11/15/2020 will exist in version v1.x and v2.0.
Why is it changing?
These changes improve the usability of the datasets from the PL_RelationshipAwareness source provider within Data Studio. The ISO date format will now be the standard date format for all date fields contained within Data Studio datasets from the PL_RelationshipAwareness source provider. The removal of unnecessary fields further simplifies these datasets by reducing their size and dimensionality.
Which datasets are impacted?
CoreAccountFinancialStatements
Current version: v1.1
New version: v2.0
Column Name | Column Type |
Last Calculated | Date format changed to ISO |
CoreCommercialLoanAccounts
Current version: v1.0
New version: v2.0
Column Name | Column Type |
OriginationDate | Date format changed to ISO |
PayoffExpectedDate | Date format changed to ISO |
PLFTPCalculationDate | Date format changed to ISO |
MaturityDate | Date format changed to ISO |
NextAdjustmentDate | Date format changed to ISO |
FTPOverRemaingLifeCalcDate | Date format changed to ISO |
FTPOverCurrentPeriodCalcDate | Date format changed to ISO |
FTPOverLoanLifeCalcDate | Date format changed to ISO |
RunDate | Date format changed to ISO |
Date format changed to ISO | Date format changed to ISO |
Notes | removed |
RowValues | removed |
Comments | removed |
FTPValueLog | removed |
FTPOverCurrentPeriodLog | removed |
FTPOverLoanLifeLog | removed |
FTPOverRemainingLifeLog | removed |
DepositFTPLog | removed |
CoreDepositAccounts
Current version: v1.0
New version: v2.0
Column Name | Change Type |
CDOriginationDate | Date format changed to ISO |
DepositFTPRateCalculationDate | Date format changed to ISO |
RunDate | Date format changed to ISO |
Notes | removed |
RowValues | removed |
Comments | removed |
FTPValueLog | removed |
FTPOverCurrentPeriodLog | removed |
FTPOverLoanLifeLog | removed |
FTPOverRemainingLifeLog | removed |
DepositFTPLog | removed |
CoreOtherAccounts
Current version: v1.0
New version: v2.0
Column Name | Changed Type |
HorizonProjectionAsOfDate | Date format changed to ISO |
RunDate | Date format changed to ISO |
Notes | removed |
RowValues | removed |
Comments | removed |
FTPValueLog | removed |
FTPOverCurrentPeriodLog | removed |
FTPOverLoanLifeLog | removed |
FTPOverRemainingLifeLog | removed |
DepositFTPLog | removed |
How does my bank need to prepare for these changes?
- Any process that uses any of the removed columns need to be updated to no longer reference these columns.
- Any process that uses the impacted datasets will need to be limited to only use the most recent major version partition. When reading a given dataset, the major dataset version (i.e. v1.x) must be specified to prevent duplication of records (i.e. having a dataset with the same record from v1.x and v2.x).
Before the change, dataset reads must specify v1.x as the major dataset version.
Example:
datamart/L3/v1.0/Primary/PL_RelationshipAwareness/Core/ CoreAccountFinancialStatements/InstancePartition=[YourclientIdhere]/VersionPartition=v1.*/
After the change, dataset reads must specify v2.x as their major dataset version.
Example:
datamart/L3/v1.0/Primary/PL_RelationshipAwareness/Core/ CoreAccountFinancialStatements/InstancePartition=[YourclientIdhere]/VersionPartition=v2.*/
When are these changes happening?
- 10/15/2020: Emails to Data Studio clients notifying them of pending changes in 1 month.
- 11/15/2020: New major dataset version starts being populated (v2.0 for impacted datasets) and is backfilled.
- 12/15/2020: Prior major dataset versions will not be populated with new data.