In SAS Marketing Automation, counts might be ignored when you generate or refresh campaign-group data where the member campaigns contain Link nodes.

This behavior occurs only when you select the diagram property use most current data when referenced by a link for the source campaign.

The problem occurs when you perform steps that are similar to the following:

1. Create a source campaign that contains a Select node and a Cell node, and you set the Cell node so that it is available for linking.


2. Set the diagram property to use most current data when referenced by a link.


3. Create a target campaign that has a Link node pointing to the Cell node that you created in step 1. Then, add a Communication node.


4. Add the target campaign with the Link node to a SAS Marketing Automation campaign group. Then, create or refresh the optimization input data.

The target campaign always keeps the same counts, even when the underlying data changes. This behavior means that the underlying source campaign is never re-executed.

The incorrect counts are displayed only in a SAS Marketing Automation campaign group. However, if you execute the target campaign with the Link node outside of the campaign group, the counts are recalculated and the correct counts are displayed.

As a workaround, clear the counts in the source campaign (with the Cell node that is available for linking) before you refresh or generate optimization input data.

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

Note: When you generate or refresh SAS Marketing Automation campaign-group data, issues can occur if the following Java arguments are in the wrapper.conf (Windows) or setenv.sh (UNIX) files:

For convenience, SAS Technical Support calls these options alwaysrun options because of the .alwaysrun extension.

In addition, the following property is set, typically, in conjunction with the Java arguments shown above. However, this property has no impact on a failed case:

The hot fix introduces a new Java argument:

When you generate or refresh campaign-group data (and you use many layers of Link node campaigns), the .alwaysrun extension can increase execution time.

Therefore, this new Java argument is introduced as a start-up property that explicitly turns on this behavior.

To set the alwaysrun functionality for all Link node campaigns and for generating or refreshing optimization campaign-group data, you must set these properties in the wrapper.conf (Windows) or setenv.sh (UNIX) file:

The following property is obsolete and does not need to be set. However, leaving it in place does not have any negative side effects.

Operating System and Release Information

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