SAS Real-Time Decision Manager has many interconnected objects that must all be present in a repository for a decision campaign to execute successfully. The list of objects includes campaigns, sub-diagrams, treatment campaign sets, treatment campaigns, activities, scoring models, and others. In some cases, if the interconnected objects are imported into an environment using more than one SPK file, the connections between objects are lost. In particular, importing a treatment campaign set separately from its members can break the connections between objects. Importing a decision campaign separately from a sub-diagram that the campaign references can also break connections.

To work around this problem, export and then import the full dependency tree of campaign objects when you promote decision campaign objects. Because you are prevented from importing or overwriting existing campaigns, treatment campaign sets, and treatments in the target environment, you must perform an extra step first. Before you import, use SAS^® Customer Intelligence Studio to delete the existing objects in the target environment that you want to replace.

If you do promote objects separately, you might need to re-create the connections after you import. For example, you might need to reassign decision treatment campaigns after you promote a new version of the parent campaign and its matching treatment campaign sets.

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

After you apply the hot fix, the link between a campaign and its subdiagram is maintained if you import the two objects separately. The link between a treatment campaign set and a member treatment campaign is also maintained if you import them separately. Note that the directory paths for the objects in the target environment and the source environment must still be identical. This requirement that the directory paths for decision campaign objects be identical does not change after the hot fix is applied.

Operating System and Release Information

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

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