When missing code / unique identifier in transactual data (general ledger) for list dimension
What is the best way of treating a general ledger, in other words a big data transaction file, that is required to be in the data hub and is missing a unique identifier for each row, i.e. something to be used as a code for the list that will act as the dimension for the DATA module? I could create my own code in the file 1, 2, 3, ... and so on, but when the customer then load in the next month and they cannot start over from 1 but need to follow the count. This seems a bit manual. What would be the best practice here in case the customer will not / cannot provide me with a unique identifier?
Re: When missing code / unique identifier in transactual data (general ledger) for list dimension
I agree with the earlier comments, the best way to handle this instance would be to create a unique ID using fields in your data source. The good news is you don't need to do this offline before import, you can instruct Anaplan to combine these fields in your import process
While this does work, it is best to create a unique ID at the source to remove extra processing time and work by Hyperblock. Also, by creating the unique member at the source, you will be able to import the transactional data to Trans module and the properties to a SYS Properties module. If you use the combination of properties method, you will not be able to do that and will be forced to store all data as properties in the list which is not advisable and is against best practices.