It's me again! 

The below issue was discovered in version 12.5.

Our attempts to change an existing allocation strategy configuration appear saved, but have no effect.

We logged case 148046. If you find this issue is affecting you, please reference our case and alert your CSM et al.

Here are repro steps performed on a modeled table called "Validation File Check" allocating into "Cost Source". To determine if this is a problem for you as well, sub "Validation File Check" with another modeled table. I also caution you to create a branch to test.

1. Go to Validation File Check modeled table.
2. Ensure you’re positioned on the Model step.
3. Set the Select a metric dropdown to “Cost Validation Metric 1”.
4. Click the Add Allocation button.
5. In the To section, set the “Choose the object to allocate to” dropdown to “Cost Source”.
6. Click on the Apply button.
7. Verify cost 100% allocated and evenly spread by reviewing the Destination tab.
   SPECIAL NOTE: Notice the Expense Type values. You should see more than “OpEx”. For example, “CapEx” and/or “OpEx Budget” should be listed. If not, go to another fiscal period where those values are observed in addition to “OpEx”.
8. In the Distributing section (of the allocation strategy’s config), enable the Data Relationship checkbox.
9. For the Source Colum and Destination Column, set to the “Expense Type” field.
10. Click on the Apply button.
11. Review the Destination tab again.
12. Notice the allocation affected rows in addition to “OpEx”. With the Data Relationship definition, only the “OpEx” rows should have been allocated onto.

Tagging our CSM and others who are on 12.5, about to upgrade to 12.6, or already upgraded.

If you already upgraded, I would really appreciate you testing and providing feedback if this issue is or is not observed in 12.6.

@Brett Yates @Julie Batty @Jenny Franklin @Richard Coronado @Molly Meinert @Tony Wong @Thomas Bognar @Prem Kilaru @Shannon Lynch @Sofia Angeles @Sandor Welfing Yamini Gummadi

Hello Matt,

We have done quite a few changes like you describe above in 12.6 and have not had this issue.  Is this problem limited to one model object or more?  It could be that the model object is "corrupted" so to speak and needs recreating or some serious assistance from Apptio support to set it right.

We're thinking along those lines considering other TBMers do not appear to be experiencing the issue nor do we see it affecting other objects we tested with.

We removed all allocations from the object, but it still was affected by the issue described in the original posting. The issue has been escalated to Apptio Engineering. I'll try to revisit this posting with the eventual resolution steps.

@Matt Temple did multiple allocations and did not experience this issue in 12.5 nor 12.6. Will want to know what engineering has to say and what is the work around they proposed in the interim?

Very good information. Thanks for sharing. Most helpful!