| ID | Service | Method | Description | Reported On | Status | Release Date |
|---|---|---|---|---|---|---|
| MAP-387 | Inventory Service | GetFilteredInventoryItemList GetFilteredSkuList |
Specifying "LastUpdateDate" as the "DateRangeField" in the "ItemCriteria" object does not reutrn the expected results. It always returns the items that were CREATED in the specified date range. Temporary Work-around: N/A |
3/11/2008 | RELEASED | 5/14/2008 |
| 11672 | Inventory Service | SynchInventoryItem | The "setup" scenario is the following ... 1) You have an existing Variation Relationship named "MyRel1" 2) You have an existing Item with SKU "MyParentSku1" which has already been defined as the Parent of "MyRel1" 3) You submit an API "Sync" request for "MyParentSku1" which contains the Variation Info node in the SOAP Packet as ... <VariationInfo> <IsInRelationship>true</IsInRelationship> <RelationshipName>MyRel1</RelationshipName> <IsParent>true</IsParent> <ParentSku>MyParentSku1</ParentSku> </VariationInfo> So basically ... You are just submitting the exact state of the Parent Item as it already exists in the database. The error is happening becase the code is incorrectly trying to create a new Varition Relationship for the Item. And really, all that it really needs to do is recognize that it is already there. Temporary Work-around: Dont provide the Variation Information if it there is nothing to change |
2/7/2008 | RELEASED | 3/8/2008 |
| 11417 | Inventory Service | SynchInventoryItem | When UPDATING an item that already has Item-level Shipping Rates defined ... And you specify Classification information without Shipping Rates ... The API is incorrectly throwing an "Object Reference Not Set" error. This is because it is assuming that it has to look for and update rates eventhough you havent specified any. Temporary Work-around: Provide the shipping rates in your call |
12/1/2007 | RELEASED | 1/26/2008 |
| 10690 | Inventory Service | SynchInventoryItem | When UPDATING an item that already has a Flag assigned to it ... If you specify the Flag "ExclamationPoint" in your update request ... The API is incorrectly removing the currently assigned Flag and NOT setting the Flag to "ExclamationPoint". Temporary Work-around: None |
9/3/2007 | RELEASED | 10/16/2007 |
| 10489 | Inventory Service | SynchInventoryItem | When UPDATING an item that already has a Flag assigned to it ... If you do NOT specify a Flag in your update request ... The API is incorrectly removing the currently assigned Flag when it should be leaving it alone. Temporary Work-around: None ... You'll have to specify the current Flag in the UPDATE request. |
8/8/2007 | RELEASED | 10/16/2007 |
| 10488 | Inventory Service | SynchInventoryItem | When creating a NEW Item ... If you have Global-level Shipping Specified for your Account ... And you specify a Classification and Distribution Center combination that DOES NOT specify its own Sipping Rates ... Then the API should be setting the shipping calculation method for the new Item to "Global". Instean, the API is incorrectly changing the indicator to say that the method is "None". This issue is very similar to ID #9644 listed below. Temporary Work-around: If you go to the Global Shipping or Classification Shipping settings page and click "Save", this should reset the indicator correctly. |
8/7/2007 | RELEASED | 8/23/2007 |
| 10353 | Inventory Service | SynchInventoryItem | If you UPDATE an item that has existed for a while, after the UPDATE, it shows up in the All Items View in Merchant when you have the New Items Filter selected. This is incorrect since you only updated the item. Temporary Work-around: None. This is a data problem with a time-stamp value that is being incorrectly set for the item. |
7/17/2007 | RELEASED | 10/16/2007 |
| 10274 | Inventory Service | SynchInventoryItem | "Blocking" an item does not work. Temporary Work-around: You'll have to perform this operation through the Merchant UI until this bug is fixed. |
7/5/2007 | RELEASED | 10/16/2007 |
| 10227 | Inventory Service | SynchInventoryItem | If you do not have a ChannelAdvisor Store created for your Account, and you try to add/update an item and include a value for the StoreInfo complex type, the method call fails with a "Object reference not set" error. Temporary Work-around: Do NOT include this complex type in your method call. |
6/29/2007 | RELEASED | 10/16/2007 |
| 10083 | Inventory Service | SynchInventoryItem | When specifying a NEW image to associate with the Inventory Item ... No image thumbnails are being generated. Temporary Work-around: Create the image through the Merchant UI (or via FTP) first and then use the API to associate it to the Item. |
6/19/2007 | RELEASED | 7/2/2007 |
| 9928 | Marketplace Ad Service | AddMarketplaceAd | The method call returns an error when you specify a Primary or Secondary Store Category value that is different than the value you have specified with the desired Posting Template. This is an incorrect restriction for the Store Categories. It is however valid for the Primary and Secondary Category values. Temporary Work-around: Create the Ad using the API, but modify it through the Merchant UI to set the correct Store Category value overrides |
5/25/2007 | RELEASED | 10/16/2007 |
| 9877 | Marketplace Ad Service | AddMarketplaceAd | When your "Add" request meets the following criteria:
|
5/23/2007 | RELEASED | 5/25/2007 |
| 9644 | Inventory Service | SynchInventoryItem | When updating an existing SKU that is using Global or Class level shipping rates ... If you do not provide any shipping details in your update request, then the API is incorrectly changing the indicator to say that the Item is using Item level shipping eventhough there are no configured rates. This then causes an error during the Poisting process saying that the item has no valid shipping rates configured. Temporary Work-around: If you go to the Global Shipping or Classification Shipping settings page and click "Save", this should reset the indicator correctly. |
5/8/2007 | RELEASED | May Release |