Date	2017-07-13
Authors	Russell Steel (Unlicensed)
Status	In progress
Summary	The latest DR release, v1.17 has different columns names defined that in v1.16
Impact	Causing nightly ETL to fail

Root Cause

Their are table column name differences between v1.16 and v1.17;

e.g vwPerson.NaltionalityDual is name vwHEE_Person.DualNationallity

Trigger

Resolution

Hicomm to rationalise the DR view columns names

Detection

Sent: 29 June 2017 13:10
To: Yvonne Cunningham; Graham O'Regan
Cc: Benjamin Witton; Adrian Ashley
Subject: Re: Data Repository Access

Hi Yvonne,

I have been looking at the latest Data Repository for TV and SW, v1.1.7, and compared the view structures back to the previous versions, and have noted the following vwPerson column names didn't exist in v1.1.6 of the data repository;

name	name	name	column_id
HESW	vwHEE_Person	LegalForename	10
HESW	vwHEE_Person	DualNationality	39
HESW	vwHEE_Person	SexualOrientation	40
HESW	vwHEE_Person	ReligiousBelief	41
HESW	vwHEE_Person	EthnicOrigin	42
HESW	vwHEE_Person	InactiveFromDate	53
HESW	vwHEE_Person	InactiveNotes	54
HEWTV	vwHEE_Person	LegalForename	10
HEWTV	vwHEE_Person	DualNationality	39
HEWTV	vwHEE_Person	SexualOrientation	40
HEWTV	vwHEE_Person	ReligiousBelief	41
HEWTV	vwHEE_Person	EthnicOrigin	42
HEWTV	vwHEE_Person	InactiveFromDate	53
HEWTV	vwHEE_Person	InactiveNotes	54

For example, the new column DualNationality was previously namedNationalityDual, LegalForname was previously named LegalFornames, the other columns look to be newly introduced in v.1.1.7.

Please could you confirm that these column names changed are expected, and what steps can be taken to minimise these types of difference going forward ?

From: Yvonne Cunningham <Yvonne.Cunningham@hicom.co.uk>
Sent: 29 June 2017 13:53
To: Russell Steel; Graham O'Regan
Cc: Benjamin Witton; Adrian Ashley
Subject: RE: Data Repository Access

Hi Russell

The change of names between versions was not intentional and our upcoming release should contain the fixes to restore these back to the naming convention they previously used.

The “vwHEE_” prefix is also temporary while we transition the HEE users over to 10.90, once this is complete we would look to removing the “vwHEE_” prefix.

Once we have a confirmed upgrade timeline for the HEE users we can proceed to plan a release where we remove the prefix, but there is no intention to rename the columns within the views.

Please note the changes for consolidation also includes the removal of some fields, where they no longer exist in the datasource.

Hope that makes sense.

Action Items

Action Item	Type	Owner	Issue
	mitigate/prevent

Timeline

Supporting Information

e.g. monitoring dashboards

Browser not supported