MYOB Advanced Procore Integration 6.4 Release Notes

This page describes what was introduced in the 6.4 release of the MYOB Advanced Procore integration

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

All MYOB Advanced 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 most recent version of MYOB Advanced Procore Integration package has been updated to accommodate and must be installed. In order for Procore Integration to work, make sure to install the recent version of Procore Integration package:

Procore Integration v5.7.000 (compatible with MYOB Advanced 2020.6) and later packages.
Procore Integration v6.4.000 (compatible with MYOB Advanced 2021.1) and later packages.
Procore Integration v7.0.000 (compatible with MYOB Advanced 2021.2) and later packages.

What's changed?

An error message has been corrected for the case when the budget code of the imported item is missing an essential element. The entities imported from Procore must have budget key specified in Procore. If the element of the budget key is missing in Procore, the error message will be displayed.
Optimization of event handling RowSelecting in Procore Integration. Technical item to improve the integration performance and efficiency.
Added a validation on Subcontractor Invoice import with no lines. On import of subcontract from Procore to MYOB Advanced, the validation asses that the subcontract has detail lines in Procore.
SQL_Migration_Procore script is made to be MySQL compliant. Technical item.
The uniqueness requirement for Policy number of the insurance documents in the Compliance Management is removed.
Learn more
Compliance Management CL401000:
On the Compliance Management (CL401000) screen, the Policy number does not have to be unique for the documents with type Insurance. The duplicates are restricted based on the combination of the parameters (for the documents with Document Type = Insurance only):
- Document Category
- Policy
- Vendor
- Project
- Effective Date
- Expiration Date
- Limit
Procore Integration:
The rules for finding a match on the import of project insurances and vendor insurances from Procore were changed.
MATCH rules on Import of the Project Insurance (Project Insurances Synchronization PC201004):
- Project insurance exists in Procore and MYOB Advanced if:
  - Policy (MYOB Advanced) = Policy number (Procore)
  - Project (MYOB Advanced) = Project (Procore)
  - Vendor (MYOB Advanced) = Company (Procore)
  - Document Category = Insurance Type (Procore)
  - Effective Date = Effective Date
  - Expiration Date = Expiration Date
  - Limit = Limit Amount
MATCH rules on Import of the Vendor Insurance (Vendor Insurances Synchronization PC201003):
- Vendor insurance exists in Procore and MYOB Advanced if:
  - Policy (MYOB Advanced) = Policy number (Procore)
  - Project X (MYOB Advanced) = Global Insurance information level in Procore
  - Vendor (MYOB Advanced) = Company (Procore)
  - Document Category = Insurance Type (Procore)
  - Effective Date = Effective Date
  - Expiration Date = Expiration Date
  - Limit = Limit Amount
On import of project/vendor insurances:
- If a match is not found (there is no insurance for which all parameters match the imported values) – then create a new Insurance
- If a single match is found (there is an insurance for which all parameters match the imported values) – link and update the documents
- If multiple matches are found (there are several insurances for which all parameters match the imported values) – import is not executed and the error message is displayed. The user can manually map the documents on the MATCH tab.
Optimize the calls to the database from the Subcontractor Invoices Synchronization screen to get rid of the timeout error. Technical item.

What's fixed?

List of resolved issues

Issue	Resolution
Snapshots affects sensitive integration Procore-related database tables.	When a snapshot was created in a Settings Only mode, Procore Integration related data used to be copied into the snapshot despite the mode of the snapshot creation which caused errors. A new mode Settings Only with Procore mode was added to the snapshot creation. It has to be selected when creating a snapshot in settings only export mode (on the Tenants SM203520 pop up screen) from the tenant that has Procore Integration established. When a snapshot is created with a Settings Only with Procore mode, there is no need to run a script after the snapshot is applied to a new tenant (which was a workaround for the earlier versions).
Subcontract Invoice import duplicates AP Invoice lines when Subcontract already has more than one invoice created for it.	The issue has been fixed.
After failed commitment validation code try to validate commitment lines.	On import of Commitment Change Orders from Procore to MYOB Advanced, if Allow Import for not Synchronized Commitments setting is cleared on the Change Order tab in Procore Integration preferences PC100000, then related commitments must be synchronized before the CCO import. If commitments are not synchronized, the system stops the import once the validation shows the error the commitment is not synchronized yet.
Procore Subcontractor Invoices import is not executed because the integration tries to process zero-lines even if the corresponding line of the commitment is closed.	When the system imported subcontractor invoices from Procore for the commitment, and at least one line of the commitment was closed, then even if the corresponding line of the subcontractor invoice did not have any value to bill (has 0s in all the columns), the system still tried to select this commitment line on the creation of the AP document. That caused an error, as the line was closed. If the line of the Subcontractor Invoice in Procore has 0 value in all the columns of the line, then on import the system does not try to include this line to the created AP document (since the corresponding line of the commitment might be closed).
Subcontractor Invoice cannot be linked on the Subcontractor Invoices Synchronization > Match tab. Invalid field type SubcontractorInvoiceLinkRecord.ProcoreInvoiceNumber.	The system did not allow to select Subcontractor Invoices to manually match with the AP documents in MYOB Advanced on the Subcontractor Invoices Synchronization > Match screen.
When Procore SCI line has zero value, API call returns NaN value which is not processed by the system.	Randomly reproduced technical item. In some cases, f.e. is the CCO-related line of the SCI does not have any value to bill API call returns NaN value instead of the 0.00 values in the line. The integration did not process this value correctly.
AP Bill created on import from Procore contains duplicated values in the lines if imported subcontractor invoice has more than one line with the same budget key and related subcontract already has more than one subcontractor invoice imported.	If subcontract in Procore had more than one line for the same budget key on the subcontractor SOV tab and the subcontractor invoice has several lines for the same budget key, then AP document created on import from Procore contained duplicated values in the created lines.
When multiple languages are specified on the System Locale, the description of the Project does not appear on the Projects PC201101 and the export fails.	When multiple languages are specified on the System Locales SM200550, the description of the Project did not appear on the Projects PC201101 and the export of the project failed. The issue is fixed and the project can be exported.
Procore Vendors created on import from Procore does not have the Account Name populated in the Payment tab, Remit-to Info section of the Vendors screen AP303000.	The default logic of filling in the Account name on the Payment tab, Remit-to Info section of the Vendors screen AP303000 was introduced.
AP Bill created from import of the subcontractor invoice from Procore has date equal to the current business date instead of the date of the invoice in Procore	The date of the AP Bill created on import of the Subcontractor Invoice from Procore is equal to the Invoice Date of the imported Subcontractor Invoice.
Subcontractor Invoices Synchronization process does not support the Updated status (Synchronize All functionality fails).	Technical item.

What's changed?

Compliance Management CL401000:

Procore Integration:

What's fixed?