-
1. Re: What should be the value for Record Key we should pass while importing characteristics values against Item via manual import?
Hi Anurag, you don't need to precisely follow this format. It is just the identifier for the value. That is important since characteristics can follow a hierarchy where one value follows as child of another (record key and parent record key)
-
2. Re: What should be the value for Record Key we should pass while importing characteristics values against Item via manual import?
Hi Stefan,
Long time.. Hope you are doing great..
Even I was thinking same but again I need to figure out a way to auto generate this number as Data Stewards are going to load characteristics values against an Item via csv import and there they wont be having a way to remember previous number.
Do you know any way by which we can generate number automatically during Import so that will be unique always ?
Regards
Anurag Chourasia
-
3. Re: What should be the value for Record Key we should pass while importing characteristics values against Item via manual import?
1 of 1 people found this helpfulHi Anurag,
indeed. Even more happy to hear from you
Which version of Product 360 are we talking about? We have improved the data model in that area substantially with 10.0. It is not needed anymore to have the identifier unique on the same level (say root) as we can now club it with the identifier of the characteristic itself.
If you are on 10.0 try a sample export of characteristic values on an item to see what I mean.
Perhaps a useful lead?
Cheers,
Stefan
-
4. Re: What should be the value for Record Key we should pass while importing characteristics values against Item via manual import?
1 of 1 people found this helpful0000.0000.RK is always a good one. It needs to be unique together with the characteristic.
That's also the default we use with version 10.0 for the first record of a specific characteristic and item.
Especially for root characteristics which do not have multiple records it would be great if you use that, since the "simplified characteristics" will automatically show you the values with version 10.0 in case you used that record key (as it's the default there).
Greetings
Andreas
-
5. Re: What should be the value for Record Key we should pass while importing characteristics values against Item via manual import?
Hi Andreas,
Thanks for update. That's the good one to start however I have already started with "ItemNo.RK" as Item Number will also be unique. Let me know your thoughts on this.
Regards
Anurag Chourasia
-
6. Re: What should be the value for Record Key we should pass while importing characteristics values against Item via manual import?
The itemNo is unique across the items, but that's not really a requirement for the record key. You need a unique record key especially for characteristics which have an upper bound of > 1, so the customer can have multiple records per item for the same characteristic. That is the crucial part.
Your solution won't work in this case.
If you use 0000.0000.RK for the first record of a characteristic, it will also work fine after the upgrade to 10.0 or later and you can see those values also in the main table in the clients as well as use the rich client search for it etc. ("Simplified Characteristics"). If you have a different Record key, you would need to migrate that then.