Need unique element through versions

[LipChean_Soh]

Hi,

You can perform 2 imports sequentially, i.e. the first from whatever source into 'All Entries', and then the second from 'All Entries' into 'Alphabets'.

You can incorporate a delta mechanism, such that previously imported 'All Entries' are flagged, and not imported again from 'All Entries' into 'Alphabets'.

Thanks,

LipChean

[Vladimir]

Yes, 2 sequential imports will do.

But I hoped to solve with formulae because I have too many imports and a huge amount of items in the model, so duplicating imports will affect Its speed

[LipChean_Soh · Accepted solution]

Hi,

To be honest, the setup of Unique Codes should be done outside of Anaplan, since Anaplan is a client facing tool and not a database tool.

Having said that, please see if the following works.

1. Concatenate.All combines all All Entries.Code using TEXTLIST.

2. All Entries.'Count 2' counts the number of All Entries.Code in the entire list.

3. All Entries.'Unique Code 2' grabs All Entries.Code where All Entries.'Count 2' = 1

Thanks,

LipChean

[DavidSmith]

@Vladimir 

Maybe I am missing something, but if you create a list based on the code, that will only generate unique values (you can ignore the duplicate value errors)  

You can then bring the data into a module by country, list, version and the list created above

David

[Vladimir]

Hi David.

This is exactly what I'm trying to avoid, many imports in model generating duplicate value errors, so I need to form views with unique elements.

[Vladimir]

Hi,

That is tricky)

But it works.

Many thanks!!!!  @LipChean_Soh 

[DavidSmith]

A better solution is to try and get the file sorted at source and have only the unique members in the file

Can you ask to provider of the file to do this? It will simplify the problem because Anaplan is not an ETL tool

David

[LipChean_Soh]

@Vladimir 

I agree with @DavidSmith, i.e. "Can you ask to provider of the file to do this? It will simplify the problem because Anaplan is not an ETL tool"

Remember, just because we can do it, doesn't mean we should do it.

As mentioned at the beginning of my suggestion, the setup of Unique Codes should be done outside of Anaplan, since Anaplan is a client facing tool and not a database tool.

Thanks,

LipChean

[Vladimir]

I'm not sure if the customer's IT dept would be able to generate these codes, but I'll try

Thanks again.