You need to sign in to do that
Don't have an account?
Lee Anne G
workflow not firing after update by SOAP API
We have a very simple workflow defind on an Order. If the Status changes, then we have a workflow that changes the "Status as of Date" to Today(). If we change the status through the UI, the workflow fires as expected.
However, I noticed that if our order Status is updated via SOAP API webservice (from our ERP solution), the Status as of Date doesn't change as expected.
Everything I've read suggests that the workflow should be firing.
However, I noticed that if our order Status is updated via SOAP API webservice (from our ERP solution), the Status as of Date doesn't change as expected.
Everything I've read suggests that the workflow should be firing.
When that should work and that doesn't, it is sometimes a problem of incoherent and concurrent updates which finally modify twice (or more) the same field and you just see the final update but that should not be your problem here (no update at all for you).
- The most interesting is the Workflow Rule Detail page for seeing the rule criteria?
- status__c can be changed by this field update but also triggers, processes and so on.
- Only the debug log can show the all steps in detail for complex conccurent processes.
- SOAP API webservice (from our ERP solution) : what do you call your ERP solution?
Regards