Why was the OBJID field removed from the DC staging tables?


Why was the OBJID field removed from the DataConnect (DC) staging tables for Classifications and Locator fields (Tri-160132)? How should we now update a Classification field such as triMainPriorityCL in t_tripeople through the staging table? Would it work if we update the text field triMainPriorityCL in the staging table, and expect that the DataConnect staging process will update the corresponding OBJID field in the real t_tripeople table?

From IBM TRIRIGA Platform 3.4.2.1 on, we have this change: “DataConnect staging tables no longer contain the unused OBJID field for Classifications and Locator fields. (Tri-160132)” Those OBJID fields were removed since they were not functional, and not required as part of the staging table functionality.

When configuring your interface, if you map the full path of the field correctly to the respective ones on the staging tables, the platform code automatically maps it to the field. The system will take care of correctly updating a Classification field such as triMainPriorityCL in t_tripeople through the staging table, if the mapping has been correctly configured. So, if the mapping is OK, this should not be a concern. There is no need for the staging field OBJID for such a scenario.

Continue reading

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s