This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
It looks like the MI_COMB columns takes that value from either MI2017(I assume its a typo) or MI2018 based on Case_Year, i.e. use MI2017 if CASE_YEAR is 2017, etc. If that's the case shouldn't the MI_COMB for row 5 be 46, instead of 45?
Here's dynamic version that uses a transpose/filter combination to determine the MI_COMP column.
The transpose tool pivots the data so all the year information is is 2 columns, Name and Value. The filter selects only the rows where the Case_Year is in the Name field. The Value field is renamed to MI_COMP and then joined back to the original data. The join is on App and case_year, so you can find the data for multiple years for each app, as in the 1st 2 rows below
I added an extra data to your input to demonstrate the dynamic nature of the solution. It should work with any number of rows and columns