locked
BAM relation ships with empty values RRS feed

  • Question

  • Hi,

    We are using the BAM in a lot of our projects with sometimes canonical BAM definitions (receive, send, process, error, ...).

    In order to track custom fields, business data in those definitions, and to avoid deploying a custom one for each new flow, we are using the "BAM RelationShips" to store these extra-data.

    In the Tracking Profile Editor, we use the "add relationship" in order to track the custom field we need. And it works fine... except for empty values.

    When we track empty values, we got in the BAM a value (in ReferenceData field) equal to "System.Object"...

    Any ideas to avoid it?

    Thanks.

    Tuesday, September 16, 2014 1:02 PM

All replies

  • What exactly do you mean by the extra data???

    Are these activities logically related to each other? And what are these empty values you are referring to??

    Regards,

    Mandar Dharmadhikari

    Tuesday, September 16, 2014 7:10 PM
    Moderator
  • Hi Mandar,

    As I explained in the thread, we are not only using the "RelationShips" to link activities together, but we use this mechanism to track custom fields that are not defined in the BAM definition itself.

    For example, we have a "Receive" BAM definition with a few business data and milestones. If we want to add a custom field (i.e the 'CustomerCode'), we create a relationship in the Tracking Profile named "CustomerCode" and we track into this relationship the customer code that comes from a message payload.

    And when this field in the message payload is empty, we have a "System.Object" value in the ReferenceData field in the RelationShips table, instead of having an empty value.

    Wednesday, September 17, 2014 2:20 PM