Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536.1K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.6K Security Software
Import columns from TB for mapping only?

Hi,
My Source TB has [Account] (usually numeric) and [AccountName] (usually a string).
Sometimes I want to use [AccountName] to map source data to target dimension [Reporting Account] while for other [Reporting Account], I would like to use [Account]
Is this possible? If so, please explain steps.
Thank you in advance!
Answers
-
What version of Hyperion(including patch level) are you on or are you cloud?
What have you design or what is currently in place?
Also providing an sample example what exactly you are seeking to do allows folks to provide more reasonable recommendations.
-
Thanks for the comment. I am using Cloud PBCS.
This is what I have currently done (I didn't know if this would work, I just tried it):
- Import Format: I added both [AccountName] & [Account] from the Source TB as columns that target [Account] (note in my original question, I renamed the target [Account] as [Reporting Account]
.
2. This concatenates [AccountName] & [Account] to give Source-AccountName
3. Data Load Mapping: I use type Like, e.g.
- C/S PARTS WARRANTY* maps to Warranty C/S
- *485 maps to Internal C/S
This gives the right outcome, but any better ideas would be appreciated?
-
That is one way of going about it, alternatively you could create a lookup dimension for account name and then use a multi dimension mapping on account to define whether to use account or account name.
Cheers
John