Forum Discussion

John_B's avatar
John_B
Former Staff
3 years ago

Critical Issue - Procore Integration packages will stop working on February 1, 2022

On February 1, 2022, due to the Vapid API Deprecation, MYOB Procore Integration of the following versions will stop working: 

  • All MYOB Procore Integration packages compatible with MYOB Advanced 2020.5.7 and earlier
  • Procore Integration v5.6.005 (compatible with MYOB Advanced 2020.8) and earlier packages
  • Procore Integration v6.3.008 (compatible with MYOB Advanced 2021.1) and earlier packages

 

The team are urgently testing updated versions (5.7 & 6.4) of the Procore integration for compatibility with the relevant versions of MYOB Advanced.

This thread will be updated as information comes to hand.

construction
Procore

2 Replies

Sort By
  • John_B's avatar
    John_B
    Former Staff
    3 years ago

    An updated Procore integration package (v6.4) is now available on the Partner Self Service site.

     

    Please note:
    v6.4 Provided by Acumatica has not yet passed QA with MYOB Advanced 2021.1
    A new 6.4 MYOB certified version is imminent and will be released as soon as QA has been completed.
    This download should only be used if a customer site is live with the Procore integration, and the existing integration has stopped working due to the deprecation of Vapid API

    • John_B's avatar
      John_B
      Former Staff
      3 years ago

      An updated Procore integration package (v6.5) is now available on the Partner Self Service site.

       

      Compatibility

      MYOB Advanced 2021.109 and later

       

      Known Issues:

      v6.5 provided by Acumatica has the following known issues:

       

      1. New suppliers created in MYOB Advanced might not sync to Procore, throwing an API error.
        Workaround:  Add any Account Email on the failing Supplier's screen AP303000. Acumatica and Procore are working on resolving this issue
      2. Customisation project fails validation – it still publishes and works, so this should be ignored (or not validated at all)
      3. Cannot publish the customisation to multiple tenants. Workaround: the customisation has to be published to each tenant individually.