When you use radio buttons for communication definitions in SAS Customer Intelligence Studio, publishing to the Common Data Model is not consistent. This problem happens when you perform steps similar to the following:

1. Create a communication custom detail by using radio buttons in the selection group, and add a Date field and a Numeric field:

   

2. Use this Communication definition in a campaign and enter a date (for example, September 30, 2018).

   

3. Execute the campaign. When you execute it, the CI_COMMUNICATION_EXT table does show the correct date of September 30, 2018. 
4. Return to SAS Customer Intelligence Studio. Then, inside the Communication node, switch to the second radio button (Group2) and enter a value (for example, 100).

   

5. Manually publish the campaign (do not execute). When you do this, published values are still correct. That is, the  CI_COMMUNICATION_EXT table does contain a second row with a new value for the COMMUNICATION_SK column, where the first row does have the date that you entered and the second row does have the value that you entered.
6. Return SAS Customer Intelligence Studio and switch to the date again and enter a different date (for example, September 28, 2018).
7. Manually publish the campaign (do not execute). This time, both values (numeric and date) are in one row for the same COMMUNICATION_SK instance.

This problem happens only when you manually publish campaigns, and it is dependent on which radio button you use:

• When you switch from the Date radio button to the Numeric button, the value for Date is deleted when the campaign is manually published.
• When you switch from Numeric to Date, the value for Numeric is NOT deleted when the campaign is manually published and no new COMMUNICATION_SK column is created.
• Executing the campaign or a communication always generates a new COMMUNICATION_SK column with only one value.

To work around this problem, do not manually publish campaigns when you use radio buttons in the custom details.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.5 is available at:

A fix for this issue for SAS Marketing Automation 6.4 is available at: