HI,

I have been informed any Appended Tables to Master Data will be removed in upcoming upgrades.  As a result we must change to pushing the fields into the Master Data using 'a Map Columns' step in the source tables instead. We have a few of our source transform tables that append to more than one Master Data Set.  Is there a way to have multiple Master Data sets in the 'Map Columns' step from one Transform? I would like to avoid creating multiple versions of the same Tables bloating the project to use in each Master Data Set.

Any advice would be appreciated.
Thanks

------------------------------
Martyn Dawes
Cancer Research UK
------------------------------

#TBMStudio

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

Hi @Jenny Franklin - looks like you had the same reaction as me! I believe its 12.10.​
Original Message:
Sent: 05-19-2022 09:03
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

I was told by a Premier consultant that the Appends would be considered a customisation and be removed - we would either have to put them all back in after or send them in via Map Columns. The Append option will still be there - just that the update would clear them out!
Original Message:
Sent: 05-19-2022 09:03
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

Most definitely @Martyn Dawes - ugh!  Glad they're still there, though - just stinks we have to put them back. 😭  Thanks for the heads up!!! 🙌​
Original Message:
Sent: 05-19-2022 09:52
From: Martyn Dawes
Subject: Mapping Columns to Multiple Master Data sets

I was told by a Premier consultant that the Appends would be considered a customisation and be removed - we would either have to put them all back in after or send them in via Map Columns. The Append option will still be there - just that the update would clear them out!

Original Message:
Sent: 05-19-2022 09:03
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

@Martyn Dawes - wonder if we rebuild them after 12.10 if they'll be wiped out again with future upgrades? ​
Original Message:
Sent: 05-19-2022 09:52
From: Martyn Dawes
Subject: Mapping Columns to Multiple Master Data sets

I was told by a Premier consultant that the Appends would be considered a customisation and be removed - we would either have to put them all back in after or send them in via Map Columns. The Append option will still be there - just that the update would clear them out!

Original Message:
Sent: 05-19-2022 09:03
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

My understanding is yes they would be wiped each time (only on Master Datasets) and that all other appends (in Transforms) are unaffected.
Original Message:
Sent: 05-19-2022 10:00
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes - wonder if we rebuild them after 12.10 if they'll be wiped out again with future upgrades? ​

Original Message:
Sent: 05-19-2022 09:52
From: Martyn Dawes
Subject: Mapping Columns to Multiple Master Data sets

I was told by a Premier consultant that the Appends would be considered a customisation and be removed - we would either have to put them all back in after or send them in via Map Columns. The Append option will still be there - just that the update would clear them out!

Original Message:
Sent: 05-19-2022 09:03
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

Original Message:
Sent: 05-19-2022 10:05
From: Martyn Dawes
Subject: Mapping Columns to Multiple Master Data sets

My understanding is yes they would be wiped each time (only on Master Datasets) and that all other appends (in Transforms) are unaffected.

Original Message:
Sent: 05-19-2022 10:00
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes - wonder if we rebuild them after 12.10 if they'll be wiped out again with future upgrades? ​

Original Message:
Sent: 05-19-2022 09:52
From: Martyn Dawes
Subject: Mapping Columns to Multiple Master Data sets

I was told by a Premier consultant that the Appends would be considered a customisation and be removed - we would either have to put them all back in after or send them in via Map Columns. The Append option will still be there - just that the update would clear them out!

Original Message:
Sent: 05-19-2022 09:03
From: Jenny Franklin
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes  What?! 😲😱 Do you know in what version that's occurring?​

@Martyn Dawes are you talking about contenet upgrades or platform upgrades?  Thanks. ​

@Michael Enslein I think its the content - the one that updates the components​
Original Message:
Sent: 05-19-2022 10:35
From: Michael Enslein
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes are you talking about contenet upgrades or platform upgrades?  Thanks. ​

Do they have a plan for their out of box configuration that includes an append step to master data? Their AWS and Azure out of the box reporting has multiple master data sets with append steps that the end user cannot edit.
Original Message:
Sent: 05-19-2022 10:42
From: Martyn Dawes
Subject: Mapping Columns to Multiple Master Data sets

@Michael Enslein I think its the content - the one that updates the components​

Original Message:
Sent: 05-19-2022 10:35
From: Michael Enslein
Subject: Mapping Columns to Multiple Master Data sets

@Martyn Dawes are you talking about contenet upgrades or platform upgrades?  Thanks. ​

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​

Hey @Mitch Miller, personally haven't had the appends wiped out before with an upgrade, though - so who knows.  Definitely going to give the pre-append file a spin, though - thanks!​
Original Message:
Sent: 05-19-2022 11:37
From: Mitch Miller
Subject: Mapping Columns to Multiple Master Data sets

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​

​@Mitch Miller @Martyn Dawes @Jenny Franklin  this only happens if you revert the OOTB table during the upgrade process.  However this seems to be a catch 22, if you do any updates to master table ie appends.   if you don't do the revert then when you do the upgrades in the tables.   Seems to be counter productive sometimes because everything has to be customized at some point.  Just my thoughts.
Original Message:
Sent: 05-19-2022 11:37
From: Mitch Miller
Subject: Mapping Columns to Multiple Master Data sets

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​

As the product manager for TBM Studio and the OOTB applications we have built on top of it, let me clarify a few things about content upgrades and specifically tables.  

Platform upgrades (e.g. Server 12.10.1 / Client 1.11) have no impact on the configuration of any applications.  These upgrades only change the behavior of the TBM Studio and the underlying calculation model.  

Content upgrades (e.g. Template v110) will impact the configured applications (e.g. CT, BoIT).  However, it is not an automatic upgrade when a new template is released.   To upgrade to a new template, in TBM Studio ribbon > Project Settings > Components Version, you first need to select the latest version, then go to the Components feature to upgrade the individual components.  

See "About upgrading Cost Transparency" for a high-level overview of these concepts (Apptio help).
See "Cost Transparency to the Latest Template Version" for a detailed description of the steps to follow.

Master Datasets are impacted in two different ways during the upgrade depending upon how you have linked the source files to the master datasets: Mapped Tables step vs Append step.

1. Mapped Tables were created to avoid having to re-map your source tables/transform tables during the upgrade process.  This is the recommended approach.  

2. Append step is the original method for linking your source tables/transform tables to the master data sets.  Unfortunately, this step is seen as a customization by the platform during an upgrade.  Two approaches can be followed for handling master datasets identified as "Customized" in the Component Upgrade screen. 

a) Do not revert the datasets shown under "View Conflicts" and just "Upgrade" the component (yellow panel).  The component will proceed and will update reports, metrics, etc.  However, it will not change the master dataset so any modification you made will remain intact.  

b) Revert the datasets show under "View Conflicts" and then select "Upgrade" (should be a blue panel if no customizations).  The component will update all tables, reports, metrics, etc.  Once complete, you will need to re-append and re-map your source tables.  This can be a fair amount of work.  One recommendation is to document and/or take screenshots of your current tables and mappings before doing the update.  

My recommendation is to follow step a and NOT revert the datasets.  The only issue is that if the OOTB content introduced a new column which is then used in a new / modified report, then the column will not be there.  You can review the table changes made to master data set tables during the different template updates and manually add the columns as needed.  

Here is the list of Dataset changes for applications on TBM Studio 12.9 (e.g. Template v109).  The previous versions are available on Community.   Server 12.10.0 / Client 1.10 introduced the latest Template v110.  However, there were no changes to the existing master datasets (as of this point in time).
Original Message:
Sent: 05-19-2022 12:12
From: Michael Enslein
Subject: Mapping Columns to Multiple Master Data sets

​@Mitch Miller @Martyn Dawes @Jenny Franklin  this only happens if you revert the OOTB table during the upgrade process.  However this seems to be a catch 22, if you do any updates to master table ie appends.   if you don't do the revert then when you do the upgrades in the tables.   Seems to be counter productive sometimes because everything has to be customized at some point.  Just my thoughts.

Original Message:
Sent: 05-19-2022 11:37
From: Mitch Miller
Subject: Mapping Columns to Multiple Master Data sets

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​

@Ed Hayman Thanks for the information, that is what I have done in the past when I have upgrade.  ​
Original Message:
Sent: 05-19-2022 15:04
From: Ed Hayman
Subject: Mapping Columns to Multiple Master Data sets

As the product manager for TBM Studio and the OOTB applications we have built on top of it, let me clarify a few things about content upgrades and specifically tables.

Platform upgrades (e.g. Server 12.10.1 / Client 1.11) have no impact on the configuration of any applications.  These upgrades only change the behavior of the TBM Studio and the underlying calculation model.

Content upgrades (e.g. Template v110) will impact the configured applications (e.g. CT, BoIT).  However, it is not an automatic upgrade when a new template is released.   To upgrade to a new template, in TBM Studio ribbon > Project Settings > Components Version, you first need to select the latest version, then go to the Components feature to upgrade the individual components.

See "About upgrading Cost Transparency" for a high-level overview of these concepts (Apptio help).
See "Cost Transparency to the Latest Template Version" for a detailed description of the steps to follow.

Master Datasets are impacted in two different ways during the upgrade depending upon how you have linked the source files to the master datasets: Mapped Tables step vs Append step.

1. Mapped Tables were created to avoid having to re-map your source tables/transform tables during the upgrade process.  This is the recommended approach.

2. Append step is the original method for linking your source tables/transform tables to the master data sets.  Unfortunately, this step is seen as a customization by the platform during an upgrade.  Two approaches can be followed for handling master datasets identified as "Customized" in the Component Upgrade screen.

a) Do not revert the datasets shown under "View Conflicts" and just "Upgrade" the component (yellow panel).  The component will proceed and will update reports, metrics, etc.  However, it will not change the master dataset so any modification you made will remain intact.

b) Revert the datasets show under "View Conflicts" and then select "Upgrade" (should be a blue panel if no customizations).  The component will update all tables, reports, metrics, etc.  Once complete, you will need to re-append and re-map your source tables.  This can be a fair amount of work.  One recommendation is to document and/or take screenshots of your current tables and mappings before doing the update.

My recommendation is to follow step a and NOT revert the datasets.  The only issue is that if the OOTB content introduced a new column which is then used in a new / modified report, then the column will not be there.  You can review the table changes made to master data set tables during the different template updates and manually add the columns as needed.

Here is the list of Dataset changes for applications on TBM Studio 12.9 (e.g. Template v109).  The previous versions are available on Community.   Server 12.10.0 / Client 1.10 introduced the latest Template v110.  However, there were no changes to the existing master datasets (as of this point in time).

Original Message:
Sent: 05-19-2022 12:12
From: Michael Enslein
Subject: Mapping Columns to Multiple Master Data sets

​@Mitch Miller @Martyn Dawes @Jenny Franklin  this only happens if you revert the OOTB table during the upgrade process.  However this seems to be a catch 22, if you do any updates to master table ie appends.   if you don't do the revert then when you do the upgrades in the tables.   Seems to be counter productive sometimes because everything has to be customized at some point.  Just my thoughts.

Original Message:
Sent: 05-19-2022 11:37
From: Mitch Miller
Subject: Mapping Columns to Multiple Master Data sets

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​

Thank you, @Ed Hayman (and @Debbie Hagen)! 😊​​
Original Message:
Sent: 05-19-2022 15:04
From: Ed Hayman
Subject: Mapping Columns to Multiple Master Data sets

As the product manager for TBM Studio and the OOTB applications we have built on top of it, let me clarify a few things about content upgrades and specifically tables.

Platform upgrades (e.g. Server 12.10.1 / Client 1.11) have no impact on the configuration of any applications.  These upgrades only change the behavior of the TBM Studio and the underlying calculation model.

Content upgrades (e.g. Template v110) will impact the configured applications (e.g. CT, BoIT).  However, it is not an automatic upgrade when a new template is released.   To upgrade to a new template, in TBM Studio ribbon > Project Settings > Components Version, you first need to select the latest version, then go to the Components feature to upgrade the individual components.

See "About upgrading Cost Transparency" for a high-level overview of these concepts (Apptio help).
See "Cost Transparency to the Latest Template Version" for a detailed description of the steps to follow.

Master Datasets are impacted in two different ways during the upgrade depending upon how you have linked the source files to the master datasets: Mapped Tables step vs Append step.

1. Mapped Tables were created to avoid having to re-map your source tables/transform tables during the upgrade process.  This is the recommended approach.

2. Append step is the original method for linking your source tables/transform tables to the master data sets.  Unfortunately, this step is seen as a customization by the platform during an upgrade.  Two approaches can be followed for handling master datasets identified as "Customized" in the Component Upgrade screen.

a) Do not revert the datasets shown under "View Conflicts" and just "Upgrade" the component (yellow panel).  The component will proceed and will update reports, metrics, etc.  However, it will not change the master dataset so any modification you made will remain intact.

b) Revert the datasets show under "View Conflicts" and then select "Upgrade" (should be a blue panel if no customizations).  The component will update all tables, reports, metrics, etc.  Once complete, you will need to re-append and re-map your source tables.  This can be a fair amount of work.  One recommendation is to document and/or take screenshots of your current tables and mappings before doing the update.

My recommendation is to follow step a and NOT revert the datasets.  The only issue is that if the OOTB content introduced a new column which is then used in a new / modified report, then the column will not be there.  You can review the table changes made to master data set tables during the different template updates and manually add the columns as needed.

Here is the list of Dataset changes for applications on TBM Studio 12.9 (e.g. Template v109).  The previous versions are available on Community.   Server 12.10.0 / Client 1.10 introduced the latest Template v110.  However, there were no changes to the existing master datasets (as of this point in time).

Original Message:
Sent: 05-19-2022 12:12
From: Michael Enslein
Subject: Mapping Columns to Multiple Master Data sets

​@Mitch Miller @Martyn Dawes @Jenny Franklin  this only happens if you revert the OOTB table during the upgrade process.  However this seems to be a catch 22, if you do any updates to master table ie appends.   if you don't do the revert then when you do the upgrades in the tables.   Seems to be counter productive sometimes because everything has to be customized at some point.  Just my thoughts.

Original Message:
Sent: 05-19-2022 11:37
From: Mitch Miller
Subject: Mapping Columns to Multiple Master Data sets

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​

Thank you for clarification @Ed Hayman​
Original Message:
Sent: 05-19-2022 15:04
From: Ed Hayman
Subject: Mapping Columns to Multiple Master Data sets

As the product manager for TBM Studio and the OOTB applications we have built on top of it, let me clarify a few things about content upgrades and specifically tables.

Platform upgrades (e.g. Server 12.10.1 / Client 1.11) have no impact on the configuration of any applications.  These upgrades only change the behavior of the TBM Studio and the underlying calculation model.

Content upgrades (e.g. Template v110) will impact the configured applications (e.g. CT, BoIT).  However, it is not an automatic upgrade when a new template is released.   To upgrade to a new template, in TBM Studio ribbon > Project Settings > Components Version, you first need to select the latest version, then go to the Components feature to upgrade the individual components.

See "About upgrading Cost Transparency" for a high-level overview of these concepts (Apptio help).
See "Cost Transparency to the Latest Template Version" for a detailed description of the steps to follow.

Master Datasets are impacted in two different ways during the upgrade depending upon how you have linked the source files to the master datasets: Mapped Tables step vs Append step.

1. Mapped Tables were created to avoid having to re-map your source tables/transform tables during the upgrade process.  This is the recommended approach.

2. Append step is the original method for linking your source tables/transform tables to the master data sets.  Unfortunately, this step is seen as a customization by the platform during an upgrade.  Two approaches can be followed for handling master datasets identified as "Customized" in the Component Upgrade screen.

a) Do not revert the datasets shown under "View Conflicts" and just "Upgrade" the component (yellow panel).  The component will proceed and will update reports, metrics, etc.  However, it will not change the master dataset so any modification you made will remain intact.

b) Revert the datasets show under "View Conflicts" and then select "Upgrade" (should be a blue panel if no customizations).  The component will update all tables, reports, metrics, etc.  Once complete, you will need to re-append and re-map your source tables.  This can be a fair amount of work.  One recommendation is to document and/or take screenshots of your current tables and mappings before doing the update.

My recommendation is to follow step a and NOT revert the datasets.  The only issue is that if the OOTB content introduced a new column which is then used in a new / modified report, then the column will not be there.  You can review the table changes made to master data set tables during the different template updates and manually add the columns as needed.

Here is the list of Dataset changes for applications on TBM Studio 12.9 (e.g. Template v109).  The previous versions are available on Community.   Server 12.10.0 / Client 1.10 introduced the latest Template v110.  However, there were no changes to the existing master datasets (as of this point in time).

Original Message:
Sent: 05-19-2022 12:12
From: Michael Enslein
Subject: Mapping Columns to Multiple Master Data sets

​@Mitch Miller @Martyn Dawes @Jenny Franklin  this only happens if you revert the OOTB table during the upgrade process.  However this seems to be a catch 22, if you do any updates to master table ie appends.   if you don't do the revert then when you do the upgrades in the tables.   Seems to be counter productive sometimes because everything has to be customized at some point.  Just my thoughts.

Original Message:
Sent: 05-19-2022 11:37
From: Mitch Miller
Subject: Mapping Columns to Multiple Master Data sets

Hey @Martyn Dawes and @Jenny Franklin I want to say this has happened on all component upgrades as it wipes out customizations and appends have always been a customization. I don't think this is new for just the latest upgrade.  This is why there are some best practices to have a Pre Append File that you append into the master that lines up 100%, so you just append the table and the columns line up perfectly and you just click the save button.  If this new for this upgrade then the pre append file could be a quick work around!​​