SKForbes - If the ID's are just for supporting detail and it is not part of your consolidation or FP&A process. I would recommend bringing this into the Attribute or Value Dimension. So the data will be stored in Stage and not in the cube. It will be visible when you brill down to stage area in OS. You can also create dashboard and in future if you are going to BI Blend you can utilize these ID's to create dashboards.
Krishna Huge thank you for your response, I appreciate it.
The internal UDs are not required for supporting detail, the business would like to make changes to the external ID and the description of many accounts, further they would like to, in some cases, shrink the number of NetSuite accounts from many to one. They feel that if they have mapped using the internal IDs this will reduce their maintenance, because the internal IDs will always be the same ....
My feeling is that the internal ID will mean nothing to the end user when they drill down and see the detail from the data upload?
I also feel that the changes made to the accounts when in the sandbox environment, unless made in exactly the same order and not allowing for any errors, during the process, will end up meaning the internal IDs can be different in the two environment, only on the affected accounts, but if we test mapping from the sandbox and then migrate to production ...
