I have previously used NetSuite's Internal ID to create account mapping transformation rules. It was basically a set of transformation rules where source was the internal ID and target was account members in OneStream.
It worked well for us because the internal ID for each account in NetSuite was unique and there were no duplicates. I would assume as long as your external ID are unique and there are no duplicates, you would be able to create transformation rules in OneStream.
Things to make sure:
1) Make sure the external ID is unique for each OS member equivalent
2) Make sure all records do have an external ID assigned.
Hope this helps.
@WchoWcho
Huge thank you for your response, I appreciate it.
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 development/maintenance 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 ...
Please let me know what you feel, what was your motivation for using the internal ID for mapping?
