Skip to Content

Hi everyone,

I thought it would be nice to post something about this topic, which is very useful but still a mystery for some. I recorded a video (tutorial + explanation) about what you can do with an Internal Communication.

Internal Communication

The purpose of this blog is to collect all relevant information, tips, good practices, workarounds, etc. regarding Internal Communication.

You can find more details about it in the complete reference here.

Feel free to ask or share about IC!

Hope this helps. 🙂

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Dedeepya Reddy

    Hi Fernando This is a very insightful video recording. Can you please clarify – how is it different from Association apart from the point where the Receiver BO processing happens in backend.

    1. Former Member Post author


      If your source BO is a standard BO, you cannot define any associations. Also, the target BO could be in a different Deployment Unit. On both cases you cannot technically take advantage of the associations.

      The receiver BO will be processed asynchronously in a background run.

      Hope this helps.

  2. Uldis Kalviskis

    Hello Fernando!

    In your video mentioned that IC is 1:1, so if I need to update multiple instances in another DU based on customer ID and customer object in this case is the sender. It means Query option won’t help here?

    1. Pradeep Kumar N


      Internal communication won’t update multiple instance, Query should be used only in a case where there is no alternative key available on the target node.

      Thanks, Pradeep.

      1. Uldis Kalviskis

        Thanks Pradeep for a confirmation. Well then need find another way around.

        Maybe anyone has some good idea. I have a custom BO which has a subnode which is almost as a party node in standard BOs. If customer instances got updated, I need to change status for the all custom BO instances where customer key is assigned to.


Leave a Reply