| Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies Author: | Teup | Posted: | Feb 1, 2024 19:44 | Subject: | Re: Bricklink API - Update Store Inventory | Viewed: | 106 times | Topic: | Technical Issues | |
| In Technical Issues, BrickFreedom writes:
| Hi
Have you made changes to the (Update Store Inventory -- PUT - /inventories/{inventory_id})
API request?
Previously you could call the API with the following parameters and would have
no issues:
['quantity' = '-2']
Now it's responding with:
["description":"String input must not be null","message":"PARAMETER_MISSING_OR_INVALID"]
Weirdly a couple of requests have completed successfully but most of the requests
are failing with the above error message. Can someone please advise what this
error is and if it's a bug that has been released into the API by accident?
|
Well, I am not surprised. This was my point... Making changes should have been
done the professional way by Bricklink:
1. Set a date, communicate clear heads-up, to get everyone on the same page with
it: the sellers, the guys from all these apps
2. Give enough time for everyone to prepare an update and stand by
3. Apply the changes all at once exactly on that announced date
Unfortunately what we got was more of a "let's push a button and see
what happens" way... I suppose such problems are going to persist no matter
the updates, as long as Bricklink gradually keeps changing things unannounced,
constantly rendering the updates outdated.
|
|
Author: | Teup | Posted: | Feb 1, 2024 13:56 | Subject: | Re: Variants Thread - January 31 | Viewed: | 74 times | Topic: | Catalog | |
| In Catalog, Teup writes:
| In Catalog, Admin_Russell writes:
.....
What a mess. Why does Bricklink never keep its own promises? Russell please....
don't do it like this, this is chaos. I have been a seller here for a very
long time, I have paid thousands of dollars to you guys and I really don't
want to close shop but you're really forcing my hand here. I simply cannot
manage my inventory if changes are randomly happening on random days over a course
of MONTHS.
The change was scheduled for 1 Feb. We sent out a newsletter to our customers
about the date. Then it was 15 Feb. That's ok, at least more time to prepare.
I've spent a full day writing software to handle the transition form old
to new item IDs. But now it turns out that the changes are going to be all over
the place between basically today and MAY. And even THAT is not
sure...?
Why wasn't it possible to simply set a date, announce it, and stick to that
plan? Why can't Bricklink go offline for maintenance on the set date of 15
Feb and come back up with the changes in place? It's a real shame that Bricklink
really doesn't seem to take these changes seriously and try to understand
the implications.... Does it really take that long to come up with new numbers?
And if it does, can you at least update them all at once by then, and announce
it properly?
|
So I see the first changes are made and are already causing inconsistencies.
VERY disappointed that my calls are ignored and that bricklink goes about this
in this very amateuristic way.
Sad that Bricklink never keeps its own promises. I will now close my store.
|
|
Author: | Teup | Posted: | Feb 1, 2024 07:28 | Subject: | Re: Variants Thread - January 31 | Viewed: | 69 times | Topic: | Catalog | |
| In Catalog, Stellar writes:
| In Catalog, Teup writes:
| In Catalog, helge writes:
| |
The change was scheduled for 1 Feb. We sent out a newsletter to our customers
about the date. Then it was 15 Feb. That's ok, at least more time to prepare.
I've spent a full day writing software to handle the transition form old
to new item IDs. But now it turns out that the changes are going to be all over
the place between basically today and MAY. And even THAT is not
sure...?
|
Just curious and asking because I am afraid that I have missed something:
Why do you need to write software to handle the transition?
|
Sorry, since the message was directed to Russell and I mentioned it before I
omitted it here - our sync system works based on item IDs. If they change randomly,
it will break our sync a little bit many times, at random moments, and it will
be hard to repair without understanding clearly what changed into what.
|
It would be easier to just monitor this page daily with your software to automate
making the changes accordingly:
https://www.bricklink.com/btchglog.asp
https://www.bricklink.com/btchglog.asp?viewHelp=Y
|
Thanks for the suggestion! Didn't know about this list. I already made somewhere
that compares our old and new inventory to identify changes, I will keep this
list in mind and it might come in handy at some point. But as for making changes
gradually: Technical details aside, manual changes are slow and annoying in our
system (not as high tech as Helge thinks ), and doing it on separate moments
for our 600+ head lots wouldn't be workable I'm afraid. At this point
closing shop and coming back in May seems the best solution unless Bricklink
can make the changes in a clean way.
|
|
Author: | Teup | Posted: | Feb 1, 2024 07:11 | Subject: | Re: Variants Thread - January 31 | Viewed: | 59 times | Topic: | Catalog | |
| In Catalog, helge writes:
| |
The change was scheduled for 1 Feb. We sent out a newsletter to our customers
about the date. Then it was 15 Feb. That's ok, at least more time to prepare.
I've spent a full day writing software to handle the transition form old
to new item IDs. But now it turns out that the changes are going to be all over
the place between basically today and MAY. And even THAT is not
sure...?
|
Just curious and asking because I am afraid that I have missed something:
Why do you need to write software to handle the transition?
|
Sorry, since the message was directed to Russell and I mentioned it before I
omitted it here - our sync system works based on item IDs. If they change randomly,
it will break our sync a little bit many times, at random moments, and it will
be hard to repair without understanding clearly what changed into what.
|
|
Author: | Teup | Posted: | Feb 1, 2024 07:01 | Subject: | Re: Variants Thread - January 31 | Viewed: | 79 times | Topic: | Catalog | |
| In Catalog, Admin_Russell writes:
.....
What a mess. Why does Bricklink never keep its own promises? Russell please....
don't do it like this, this is chaos. I have been a seller here for a very
long time, I have paid thousands of dollars to you guys and I really don't
want to close shop but you're really forcing my hand here. I simply cannot
manage my inventory if changes are randomly happening on random days over a course
of MONTHS.
The change was scheduled for 1 Feb. We sent out a newsletter to our customers
about the date. Then it was 15 Feb. That's ok, at least more time to prepare.
I've spent a full day writing software to handle the transition form old
to new item IDs. But now it turns out that the changes are going to be all over
the place between basically today and MAY. And even THAT is not
sure...?
Why wasn't it possible to simply set a date, announce it, and stick to that
plan? Why can't Bricklink go offline for maintenance on the set date of 15
Feb and come back up with the changes in place? It's a real shame that Bricklink
really doesn't seem to take these changes seriously and try to understand
the implications.... Does it really take that long to come up with new numbers?
And if it does, can you at least update them all at once by then, and announce
it properly?
|
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
|