| Discussion Forum: Thread 353330 |
|
 |
| | | Author: | constructibles  | | Posted: | Jan 30, 2024 21:14 | | Subject: | Variants Merge and the API | | Viewed: | 147 times | | Topic: | Catalog | | Status: | Open | |
|
| Hello everyone, I’ve been reading up on the multiple threads about the proposed
merge of variants. Setting aside the pros and cons of the change, I have a
question that may have material impact for any stores that are using the API
function. From what I can read it appears that one step in the merge plan is
to actually merge lot numbers together in a sellers inventory. That can create
huge problems for API users, as there is no function to link an inventory lot
ID number to a different inventory number.
My recommendation would be to leave all lot IDs existing and not merge them,
but just change the part number on both lots to the new post-merge item ID number.
So, for example, if a seller had one lot of 3747a and another lot of 3747b, then,
after the merge they would simply have two lots of 3747, and be able to make
the decision to physically combine those, keep them separate with notes, or just
leave the two lots in place.
Can we please get some specific technical information on the proposed actions
within the database and as someone commented previously it may be worthwhile
to send a targeted email to all API users alerting them of the detail of the
change, as some may not be reading the forum.
Thanks. -Jason
|
|
|
| | | | | |
| | | | | Author: | Nubs_Select | | Posted: | Jan 30, 2024 21:20 | | Subject: | Re: Variants Merge and the API | | Viewed: | 60 times | | Topic: | Catalog | |
|
| unless im mistaken thats whats happening. bricklin is only mergin the entries
not any lots for sale.
before
1 lot of exampe1
1 lot of example2
after
1 lot of example1
1 lot of example1
|
|
| | | | | |
| | | | | Author: | Give.Me.A.Brick | | Posted: | Jan 31, 2024 04:39 | | Subject: | Re: Variants Merge and the API | | Viewed: | 46 times | | Topic: | Catalog | |
|
| In Catalog, constructibles writes:
| | Hello everyone, I’ve been reading up on the multiple threads about the proposed
merge of variants. Setting aside the pros and cons of the change, I have a
question that may have material impact for any stores that are using the API
function. From what I can read it appears that one step in the merge plan is
to actually merge lot numbers together in a sellers inventory.
|
That's not the plan.
Russell said a few times already that lots will not be merged in stores:
"When catalog entries are merged, they do not combine lots in stores or wanted
lists. So separate lots will be retained with whichever note is attached. Only
the Item Name and Item Number of the item will change."
https://www.bricklink.com/message.asp?ID=1447429
And here's a link for Admin_Russell's messages:
https://www.bricklink.com/messageList.asp?uID=919043&max=20
|
|
|
| | | | | |
| | | | | Author: | Stellar | | Posted: | Jan 31, 2024 04:51 | | Subject: | Re: Variants Merge and the API | | Viewed: | 44 times | | Topic: | Catalog | |
|
| In Catalog, constructibles writes:
| | Hello everyone, I’ve been reading up on the multiple threads about the proposed
merge of variants. Setting aside the pros and cons of the change, I have a
question that may have material impact for any stores that are using the API
function. From what I can read it appears that one step in the merge plan is
to actually merge lot numbers together in a sellers inventory. That can create
huge problems for API users, as there is no function to link an inventory lot
ID number to a different inventory number.
My recommendation would be to leave all lot IDs existing and not merge them,
but just change the part number on both lots to the new post-merge item ID number.
So, for example, if a seller had one lot of 3747a and another lot of 3747b, then,
after the merge they would simply have two lots of 3747, and be able to make
the decision to physically combine those, keep them separate with notes, or just
leave the two lots in place.
Can we please get some specific technical information on the proposed actions
within the database and as someone commented previously it may be worthwhile
to send a targeted email to all API users alerting them of the detail of the
change, as some may not be reading the forum.
Thanks. -Jason
|
Only item ID and names are changing, you will end with 2 lots of the final entry:
https://www.bricklink.com/message.asp?ID=1448819
|
|
|
|
|
|
|
USA, South Carolina
Canada, Ontario
Portugal
Spain, Comunidad Valenciana