Import a subset from one list to another

Options
mwaltz0213
mwaltz0213 Member, ALL USERS, Community Member Posts: 5 Contributor

I have an import of an entire organization, which includes all levels (sales person, manager, regional manager and divisional manager). I would like to use the list that it imports in to and populate individual lists (one for each of Sales Person, Manager, Regional Manager and Divisional Manager). I have them all in subsets currently, but can't figure out how to only pull over those subsets into the individual lists.

 

Or, if possible, using the same import file, only import a subset into a separate list...

Comments

  • mwaltz0213
    mwaltz0213 Member, ALL USERS, Community Member Posts: 5 Contributor

    Thank you for the input. I'm attempting to create the module that pulls in the SalesOrg data (where the subsets are defined) but am having difficulty in creating view's off of the subsets. I can't seem to use the subset within the module or can't figure out how to do that... When creating the module, I could only bring in one subset, so I figured that wasn't the way to do it, that you use the entire SalesOrg List and somehow bring in the subset flags, but I could be wrong

    mwaltz0213_0-1594993400428.png

     

  • mwaltz0213
    mwaltz0213 Member, ALL USERS, Community Member Posts: 5 Contributor

    Hi Jitendra,

     

    Great question. I'm building out a hierarchy that I'll base user access off of. We have a way to readily pull in the entire organization and I'm hoping to limit it to the single import into Anaplan, and divvy up the organization within Anaplan. In my mind, this will allow for more of the data cleansing and structuring to be done more readily in the Data Hub, versus several imports. 

     

    Unfortunately, our import process is complicated and if I ever need any changes to the data coming in, it can take up to several weeks. I'm trying to avoid that and bring in as much as I can.

     

  • mwaltz0213
    mwaltz0213 Member, ALL USERS, Community Member Posts: 5 Contributor

    The import file does have a field where we could identify each role. I had set up the import with the logic to populate the subsets, so if we can use that field within Anaplan to identify, that would be even better. The field is TMRole and it is included in the list as well as the module currently. I imagine we can build this logic within Anaplan, but am unsure how to do that efficiently and effectively for this purpose.

     

    The SQL used is below:

    case when TMRole = 'TM' then 'TRUE' ELSE 'FALSE' end as 'TM Subset',
    case when TMRole = 'RM' then 'TRUE' ELSE 'FALSE' end as 'RVP Subset',
    case when TMRole = 'DVP' then 'TRUE' ELSE 'FALSE' end as 'DVP Subset',
    case when TMRole = 'AVP' then 'TRUE' ELSE 'FALSE' end as 'AVP Subset',
    case when TMRole = 'AGT' then 'TRUE' ELSE 'FALSE' end as 'Agent Subset'

  • mwaltz0213
    mwaltz0213 Member, ALL USERS, Community Member Posts: 5 Contributor
    Hmm. So, I'm able to create the views and have attempted to bring them in to the target model. But now I'm running into the issue of assigning a parent. I tried bringing it into the Data Hub module from a separate list, but cannot get the 'manager' to populate. Both lists have the Payee ID (which is unique) which I would think I can lookup on, but it's not bringing anything into the module. This is the formula I'm trying: Reports To Current.Reports To Payee ID[LOOKUP: SalesOrg.Payee ID]