Extended Tables - Parent/Child

[Jonathan102]

The OOB Business Application (BA) table does not contain a field for all of the information that we are collecting.  We are trying to stick with best practices and not add custom fields directly to the Business Applications table.  Instead, we have created an extended/child table off of the BA table.  The problem that we are now facing is that we cannot dot walk/add fields from the extended/child table to the BA table so the data is on two different tables.  To support several processes in development, we need to be able to access all of the needed data from the BA table.  Is there anyway to accomplish this without adding custom fields directly to the BA table?

Thanks!

[Mike_R]

Instead of extending the BA table, create a new related table.

Table Name: Business Applications Additional Info

Fields: 

Business Application (make this a reference field to the BA table) *this step is very important

Add all your other custom fields.

Once created, add this as a related list to the Business Application table.

[EricDohr]

Because of the importance of the Business Application table for CSDM and how products utilize that table, I would not recommending extending the cmdb_ci_business_app table.  

As part of your Tech Governance, you would want to evaluate the value of any new field versus development, manageability, usability, etc.