Skip to Content

Non-shareable facets and containers

Can somebody explain to me, what is a logic for creating a container, when in the system one unique facet already exists for a customer and it is received as an update for another customer? Why the facet is removed from a first customer and a container is created, if facet is set as non-shareable?

What am I expected to do with these containers? Is there a review process possible and set the facet to one or other customer?

Should I set it as shareable to avoid data loss?

Best regards,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 05, 2017 at 01:13 PM
    Add comment
    10|10000 characters needed characters exceeded

    • The reason is, because the system cannot unambiguously assign the email address to one of the two contacts.

      I'd require some sort of decision mechanism. Since there is currently no manual workflow or tool to leave the decision to a business user (which would be difficult anyway for most of our customer given the number of customer records they deal with) the system automatically removes the address from both records. There might be an option to implement a different behaviour with one of the interaction contact BADIs.