What's new in Customer Journeys?

Connect and learn more! ×
Core.Alternate Name Not Working for Subscriptions — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Core.Alternate Name Not Working for Subscriptions

Received Response
edited May 27, 2021 4:24PM in Enterprise Data Management 1 comment


Core.Alternate Name Not Working for Subscriptions



We are attempting to use the new Core.Alternate name property in subscriptions that connect a FCCS application to PBCS application. A few issues that we are running into:

1. When we add the Alternate Name property to the node types, it will not allow multiple nodes to have null values for Alternate Name property (enforcing name uniqueness). The use case for Alternate Name that we have is an override on the Core.Name property in only a few instances. So we do not want/need every node to have a value for alternate name. To get around this we also tried to derive Core.Alternate Name to simply return Core.Name, and then allow for overrides so that every node will have a value for Alternate Name & will be unique. However

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!