HOW TO: Remove Legacy R11 inference Joins to leverage new streamlined R12 column allocations

In R11 we used our inference engine to both join tables as well as drive allocations.  The combined use of this feature, however wasn’t as efficient, especially when we used up all of the allowable links.  In R12 we removed this dependency, essentially providing two features:

1. The Join step links the current table to other tables by matching values in a column in the current table with values in a column in another table. This can be useful for reporting purposes and for adding information to a table that will serve as a unit driver in a model. The intent of the Join step is to produce a single table with all of the data you need for reporting. - https://community.ibm.com/community/user/viewdocument/join-data?CommunityKey=7a610da7-1c62-4ccf-81e0-01925811038c&tab=librarydocuments
2. Database Relationship allocations in single model objects –The Data Relationship option distributes the allocation evenly across the units that match the values in a column in the source table with the values in a column in the target table. - https://community.ibm.com/community/user/apptio/viewdocument/standard-value-allocations?CommunityKey=44bcb0d2-5ce6-4504-89eb-019253d3b5d8&tab=librarydocuments

To start replacing the legacy inference joins in R11 with R12 data relationships do the following:

(Note, you’ll need to preserve a pre-worked version so you can spot check your allocation $’s. This can be accomplished via normal workspace checkout activity as it compares to your current staging build)

1. Identify an R11 legacy allocation. This will look like the below:
2. Find the backing table which supports the current document
   1. In the case of the above ^ it would be “All Business Services”
3. Click on the Join Step and identify the linking columns. (hint: these used to be the old key tables)
   
4. Go back to your single object viewer via tabs and check out this document
5. Click remove the legacy allocation by deselecting the automatic relationship check box. You’ll see this warning.  Click YES.  (NOTE: Please read the dialogue message.  Note if you did not want to remove the legacy join, you’ll need to revert this document to undo the prior change)
6. Once complete, rebuild the allocation by using the same keys you identified earlier from the Join step. Save.
7. Return back to the Join step in the backing table. Check out the document, click on the Join step, and remove. (IMPORTANT if you are trying to reduce your link path count)
   1. NOTE: An unintended result when removing this join is if you in fact were using it for reporting purposes. If this is the case, you can recreate the join using the standard R12 functionality based on the column mapping required for that report.
8. Verify your numbers against your pre-worked reference.
9. Check-in both documents.

If you were hitting the inference limit in R11 you will hit this limit in R12 until you rectify the above.  Please reach out to Apptio Support or your Apptio Customer Success Manager if you have any questions on this topic.

NOTE:  When dealing with the removal of Many:Many allocations you may see after these steps are complete that the allocation it will either not allocate or allocate less.  This means likely that one of the identifiers on either side of the allocation has gone to {various}.  In this case, add the column you are using to join the allocation to that identifier and this should fix the issue.  As always, if you have any issues please contact Apptio Support or your Apptio Customer Success Manager.

NOTE:  If working to remove an Inference Limit issue experienced in R12 Studio, Target the inbound & outbound allocations to IT Resource Towers.