3937177 Newbie

Hi Kumar and Elham, Thanks for the replies! Since 2008.1 is coming out fairly soon, I think we will use a simple workaround (like Kumar's suggestion) until we can manage Kits and Assembly Items properly through the API. Thanks again! Eric

Hi Sambhuni - any luck with this? I'm running into the same problem while adding a Lot Numbered/BoM item to a CashSale...

You have to resubmit all addresses each time... so even when you add one, you submit it plus the other already existing addresses. Basically, the addressbook items are not keyed, so that internalId doesn't serve the same purpose it does for something like a customer or a salesorder.

To anyone who might run into this issue, I resolved it by (a) setting the customer to taxable and (b) associating the customer with that tax group (ie, not necessarily the sales order). And yes, that means checking the shipping address for this particular order and updating the customer taxable/tax group information at…

My only workaround here was to update the default billing and default shipping addresses in the customer record just before generating the sales order or invoice... this essentially grabs the correct address at time of sales order generation, it just means from a customer perspective, the concept of default address is…

Disregard, I resolved the issue. For anyone experiencing this, it was based on not having any lot numbers listed. For lot numbered or serialized items, you must specify the serial or lot number when adding to a Cash Sale, Sales Order, Invoice, etc.

I'm not positive, but I'm pretty sure kits are not accessible via the API, the new API (this week sometime?) will likely support them. Again, I'm not positive, but it was certainly the case with Assembly Items.

Here is some actual test code I'm using: SearchEnumMultiSelectField oItemType = new SearchEnumMultiSelectField(); oItemType.@operator = SearchEnumMultiSelectFieldOperator.anyOf; oItemType.operatorSpecified = true; String[] aSearchVal = new String[] { "_inventoryItem" }; oItemType.searchValue = aSearchVal; ItemSearchBasic…

Hi Terry, thanks! That's exactly what I needed. I'm including my updated test code for anyone who might be doing this for the first time: SearchEnumMultiSelectField oItemType = new SearchEnumMultiSelectField(); oItemType.@operator = SearchEnumMultiSelectFieldOperator.anyOf; oItemType.operatorSpecified = true; String[]…

I believe it is in 2008.1, which is supposed to go live this weekend (I think) - if you have access to this upgrade, then you should be set... I think it's already in beta.

Thanks elham and wizard, There might be no great solution until 2008.1 is out, but what are developers doing currently who need to sell items that have member items (ie, kits and assembly items)? Do you just make them regular inventory items and do inventory adjustments for the Members manually?

Has this functionality been added? I'm using 2.5 wsdl and need to query for Assembly/BoM. Thanks in advance. Eric

I am having the same problem, was there a solution to this? // SET account to 10200 here so it's not in undeposited funds. RecordRef accountRef = new RecordRef(); accountRef.setType(RecordType.account); accountRef.setInternalId(nsCashSaleAccount); cs.setAccount(accountRef); cs.setCreatedFrom(salesOrderRef); ... Ends up in…

To answer my own question... You need to set the following. If you set the undepFunds property to false, then you must set the account. Otherwise it seems to ignore the account and defaults to true. cs.setUndepFunds(false);