okay, so I have an interesting problem that I can'...
# suiteflow
b
okay, so I have an interesting problem that I can't figure out why it doesn't work. I've got it narrowed down to the item type appears to be the issue. Need: we are tagging orders using the class field and for orders that come in with a certain class, we want to add an item to those orders. The item and it's location (line level) that are added are dependent on a couple things: 1) We prioritize certain locations over others 2) the order needs to have at least 1 item that is not a drop ship item to a vendor outside our company. We do have drop ship items that get created for our own company (long story) so I'm basing some logic off of preferred vendor in that case. Problem: I have a workflow field checkbox that gets checked when the workflow finds an item on the order that is at a certain location, that item is marked as a drop ship item, and the preferred vendor of that item is our company. This works properly for inventory items, but it doesn't work for assembly items. We do have the setting to allow purchase of assemblies checked. The system doesn't seem to recognize the item as a drop ship item. I've test using the 3 criteria and it fails. I've tested using certain location and drop ship item, fails. I've tested using certain location and preferred vendor, passes. So it's the drop ship item verification that fails on assembly items. When doing the checks, I used the same item to make sure that wasn't an issue either. Anyone else run into this issue or have an idea how to solve it outside of scripting? I could script it, this was just a much faster solution for what we needed and I'm under the gun on time. If I've left out any details needed for testing, let me know. Thanks!
I wound up creating a NS case for this issue and their support team confirmed the issue and that it was unique to assembly items. Their solve for it, while it works, is a little annoying. They had me add another column level field that sources the drop ship item field from the item so that that value is on the transaction and is less work for the workflow in terms of navigating joins. This works and solves the issue, but clutters up the items sublist some more now. Thought I'd share what I learned in case it helps anyone else out.