We’ve seen an increase in integration failures—primarily invoice failures, but also some payment issues—stemming from end users editing key integrated fields in Textura. The most common ones we’ve encountered are:
- Updates to Change Order numbers in the Change Order section, and
- Updates to the Subcontract Item # on the Contract Maintenance page.
These are the most frequent examples, but if feasible, we would recommend locking all fields that are populated via integration to prevent downstream issues.
If these fields are locked for end users, it would eliminate the ability to edit/update values that should remain system-controlled. This would help avoid a significant portion of integration failures, reduce time spent by IT on troubleshooting, and prevent downstream impacts such as missing invoices in reporting and reconciliation challenges for Treasury.
Overall, this enhancement would be a meaningful improvement and a major win in reducing data discrepancies between Textura and integrated applications (Oracle).
Regards,
Deepa