Having a serial number / dummy code is not a solution for the customer. They are asking why Anaplan cannot create a unique id during the import when it can create an unique id when we insert using a dashboard.
I believe the issue is our Import process is designed to do Insert/Update at the same time. Many APIs in other applications clearly seperate the Insert action and Update action. Insert action does not require an Unique Id and Update requires a Unique Id.
Imports are designed so they can be safely re-run without silently duplicating data, which could easily cause models to produce wildly erroneous results. It is rare for list items to only be added to, and without a code or property combination composite key that the source of the data recognizes, you have the equivalent of a denormalized "relational" database table. You can dump more items into it, but you cannot determine if those items are already loaded, and loading module data where the list is a dimension is impossible because you cannot uniquely identify items from the source data. And what if an import only partially succeeds? Every item receives a unique ID, whatever method is used to create it, but that value will have meaning only in the context of that model; if you need to rebuild the model and re-import the data it will likely be different.
Thanks Ben. That is indirectly saying that Anaplan cannot act as a source for keeping a system of records. It can only depend on external system for importing the system of records and we cannot and should not be generating a system of records with in Anaplan.
In supply chain planning applications, the planning engine spits out "Planned orders" with unique ID for each planned order. I see this as a limitation.
・Create a numbered list. Numbers of items can be as many as you need. （It won't exceed 1,048,576 because of the excel limitation.） ・Build a model with the list. And prepare line items, same as excel. It would be better to make some list items to catch specific data. ・So let's copy and paste data from the excel.
You might think that I am joking, but why must we always use the import action? I believe copy and paste is the great invention of data integration. Perhaps, most Anaplanners would not recommend this kind of implementation. Yes, this is a mere imitation of Excel. But many people love excel and its functionality like your customer.
And I assure that your customer can enjoy benefits from this Excel-ish implementation than using Excel. As below. 1) Easy check of the irregular inputs by using list item format (End users sometimes destroy Excel formula or ignore the dropdown list) 2) Of course, the history functionality of Anaplan 3) Single source of truth
Besides, proper usage of DCA implements the additional functionality as follows. 1) Once data input through copy and paste, no one can change the data. 2) Some users can read limited items only.
It can be a system, especially when the data is critical for the customer.