I've been getting this error in our Java program that sends RM Invoices over to GP from our app. It's inconsistent and I don't know what it means:
- Duplicate Tax Node ID exists in the RM Tax Work.
Our app treat it as a fatal error and stops processing, but in every case, the transaction did go into GP, so our systems end up out of sync.
Does anyone know what this error means?
Is there a way to set eConnect to treat this condition as a "warning situation" instead of error?
Thanks in advance.
- Duplicate Tax Node ID exists in the RM Tax Work.
Our app treat it as a fatal error and stops processing, but in every case, the transaction did go into GP, so our systems end up out of sync.
Does anyone know what this error means?
Is there a way to set eConnect to treat this condition as a "warning situation" instead of error?
Thanks in advance.
