BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
pcapazzi
Pyrite | Level 9

We would like to add a field to a contact history table in our CDM. Will CIS break due to this? We expect it to be null after data is published and a nightly process will update it. 

 

Thanks. 

1 ACCEPTED SOLUTION

Accepted Solutions
Dmitry_Alergant
Pyrite | Level 9
First of all, there are already two flexible "Additional_Info" fields in the table that you can use for that purpose. They were made there for that purpose. You can also change their length if it's too short.

If these two fields are not enough and you want to add a couple extra fields on top, it can be done - as far as I remember, no out-of-the-box code in SAS will break just because of that. An official SAS recommendation is to be considerate for performance and don't overload the table excessively with multiple extra fields due to performance concerns, as the contact history tends to have a lot of records. But at the end, it's up to your database to handle.

-------
Dmitriy Alergant, Tier One Analytics

View solution in original post

4 REPLIES 4
Dmitry_Alergant
Pyrite | Level 9
First of all, there are already two flexible "Additional_Info" fields in the table that you can use for that purpose. They were made there for that purpose. You can also change their length if it's too short.

If these two fields are not enough and you want to add a couple extra fields on top, it can be done - as far as I remember, no out-of-the-box code in SAS will break just because of that. An official SAS recommendation is to be considerate for performance and don't overload the table excessively with multiple extra fields due to performance concerns, as the contact history tends to have a lot of records. But at the end, it's up to your database to handle.

-------
Dmitriy Alergant, Tier One Analytics
pcapazzi
Pyrite | Level 9

Can the field types of EXTERNAL_CONTACT_INFO_ID1 and EXTERNAL_CONTACT_INFO_ID2 be changed from VARCHAR(32) to INT with no issues as well?

Dmitry_Alergant
Pyrite | Level 9

Should be of no impact for SAS MA. 

 

If you have SAS RTDM or may get it in the future, it has a built-in capability to write user-supplied values into these fields - and it expects them to be Varchars.  Similarly, it would not be a big surprise to see a new built-in capability to store information into these fields in new future versions of SAS MA (i have zero information on that, just a guess) - and if that happens it will also expect them to be character.

 

So, i'd rather either store numeric information in these varchar2 fields - you can always apply to_number() when you are accessing the data, like through a view. Or just added two new numeric fields.

-------
Dmitriy Alergant, Tier One Analytics
How to improve email deliverability

SAS' Peter Ansbacher shows you how to use the dashboard in SAS Customer Intelligence 360 for better results.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 1044 views
  • 0 likes
  • 2 in conversation