A Scheduled Database Task is configured with a parameter meant to restrict it to a specific site's Customer Orders, but it ends up processing orders from other sites too, even though the parameter looks correctly set.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Double-check that you're actually calling the specific API function you intend, and not a similarly-named one with different scope — for example, a 'Create Consolidated Pick List for Customer Orders' function and a 'Create Consolidated Pick List for Shipment (CO)' function sound close enough to select the wrong one by mistake, and they don't necessarily respect a site filter the same way. Confirming the exact API function name against its actual documented parameters (rather than assuming from the name alone) is often the real cause of a site-filter parameter appearing to be ignored.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions