Known Limitations

• Contract Payments syncing from Procore to Foundation is not supported.
• Direct Costs syncing from Procore to Foundation is not supported.
• Prime Contracts syncing from Procore to Foundation is not supported.
• Syncing Budget Line Items from Procore to Foundation requires Foundation's DataGenie. You can see an example DataGenie workflow here: https://sync-docs.agaveapi.com/docs/procore-and-foundation/prime-contract-change-orders#exporting-prime-contract-change-orders-to-foundation.
• Syncing Prime Contract Change Orders from Procore to Foundation requires Foundation's DataGenie. You can see an example DataGenie workflow here: https://sync-docs.agaveapi.com/docs/procore-and-foundation/prime-contract-change-orders#exporting-prime-contract-change-orders-to-foundation.
• Syncing Budget Modifications from Procore to Foundation requires Foundation's DataGenie. You can see an example DataGenie workflow here: https://sync-docs.agaveapi.com/docs/procore-and-foundation/prime-contract-change-orders#exporting-prime-contract-change-orders-to-foundation.
• Attachments/files (e.g Invoice PDFs) syncing is not supported, although URLs that link to these files can be synced.
• See all supported versions of Windows here: https://docs.agaveapi.com/source-systems/foundation/faqs.
• Foundation has a 10-character limit for Purchase Order and Subcontract IDs and stores both in the same table. Procore's default naming convention (<record type>-<job number>-<sequence>, e.g. PO-12345-001) can exceed this limit, causing the record type prefix to be truncated and resulting in ID conflicts between POs and SCs on the same job. We recommend changing the naming convention to <job number><sequence><record type> before syncing — once changed, future commitments on that job will automatically increment using the new format. See the Purchase Orders or Subcontracts pages for more details.