From the tabs below you can drill down in the Event aggregation to end up on a single Event:

  • Events tab
  • All Events tab 
  • Search tab

Looking at the Events tab, you have a list of Events for a given Business Object. The message for each Event is presented with the spaceholders for parameters, the actual parameter values have not been merged into the message. 


Here's the Event list for the Account Business Object in the Workshop track with the Event I0019 highlighted. The Event complains that the InterestType of some 29.371 Accounts is unknown.



Intermediate Event aggregation

By clicking the Count for the Event I0019 you go to the intermediate Event list, where the actual parameter values have been merged into the Event message to replace the placeholder.

 


Now the values have been merged it is apparent that - even though 29.371 Accounts fired the Event complaining that an InterestType is unknown - in fact only 3 InterestType values are missing. It can be very useful to export this list to Excel (maybe in order to mail it to somebody that can add the missing InterestTypes in the Target System).


The Intermediate List exported to Excel



Business Object List

Clicking a count in the Intermediate list takes you to the list of Business Object instances that fired the Event with this value for the message placeholder. This is also the list you will get if you are using the Search tab



The columns in the Business Object list are:


Item Id
The internal Id of the Business Object instance in the migration database. Click to proceed to the detail view
Xml
Clicking one of the 3 icons opens the data for the different migration steps, from left:
  • Source Data
  • Export Result
  • Target Result 
Business Object
The name of the Business Object
Migration Key
The key in the migration. This is the value of the Target Interface Fields that were marked as Key in the Studio Target Map
Result
The Result tells how far the Business Object instance got in the migration
  • Export Failure: The Business Object instance was rejected by the Source Engine in the Export step
  • Import Failure: The Business Object instance was rejected by the Target Engine in the Import step
  • Import Success: The Business Object instance was imported successfully by the Target Engine - but may still have rejected child Business Objects

Detail View

Clicking the Item Id in the Business Object list proceeds to the detail view. Here all information for on specific Business Object instance is displayed



Item Detail
Detailed information about the Business Object instance.

Item Id
The internal Id of the Business Object instance in the migration database
BankId
The Partition Value. The label/value (here BankId/30 - Bank) is configurable in the Director.
Business Object
The name of the Business Object
Source Key
The key of the Business Object instance in the Source System. These are the Break Fields from the Studio Source Map
Migration Key
The key in the migration. This is the value of the Target Interface Fields that were marked as Key in the Studio Target Map
Target Key
The key in the Target System. Is equal to the Migration Key, unless an extension is in place for the Director Runtime to call to get the Target Key
Result
Result tells how far the Business Object instance got in the migration
Migration data
The data for the different migration steps
Depending on Items
Shows a list of Business Object instances, that this Business Object instance is dependent on. Relationships defined on this Business Object in the Studio Target Map point to these Business Objects
Items depending on this
Shows a list of Business Object instances that are depending on this Business Object instance. Relationships defined in the Studio Target Map on these Business Objects point to this Business Object
Event List
The complete list of Events fired for this Business Object instance
Event Detail
Click an Event in the Event List to see the details for this Event


Migration Data

Clicking on of the data icons in the Business Object List or the Detail View will show the xml data for the selected migration step.



Above is the Export Result from the Source Engine. Data for all three steps is an Xml hierarchy of data exactly reflecting the Business Object hierarchy as it is defined in the Studio.


What happened here?

Hopefully this exercise gave you an impression of how you can drill down in the Event aggregation to end up on a complete view of a single Business Object instance. Along the way the Tracker gave you an intermediary list, where parameter values have been merged into the Event messages, giving a nice overview of the discrete values in play.


Finally the Detail View exposes the unique advantages of the Business Object approach of migFx. In on and the same place you see a consolidated view of one Business Object instance. Right down to all the exact data that flowed through the migration for this one Business Object and the links to related Business Objects.


This is what truly distinguishes migFx from other, flow-based ETL tools.