The VERO and Yardi integration relies on the mapping and status of information between the two systems. If that mapping or status is changed, it can cause a sync error to occur on the deal. This will prevent data from being updated to Yardi as expected.
One of the most common causes of sync issues on deals is because changes were made in Yardi instead of in VERO. You should be making all decisions in VERO (approve/deny/cancel) and allowing that action to trigger and send the data to Yardi.
This article explains how to identify a sync issue and how to solve some of the most common situations.
How to Identify a Sync Issue
Hover over the Yardi icon on the deal and the sync window will expand
Review if there are any sync errors
Use the RESYNC option to force the deal to sync again
Wait for the sync to complete - this may take a couple of minutes during peak times
Reload the page to see if there are any remaining errors
How to fix the sync error
Use the below list for instructions on specific errors.
After you have completed the instructions, attempt to RESYNC the deal
If this is unsuccessful you will need to Contact VERO Support and we can assist
Error Messages
Use the table below for guidance on how to fix common sync errors:
Message(s) |
Cause |
Solution |
|
Unable to retrieve the Yardi agent that is linked to the employee related to this deal Cannot add a new Agent for CRM Property |
There is an issue with the Yardi agent that the VERO agent is linked to. |
|
Unit(xxxx) Status is 'Vacant Rented Not Ready' - not available for selection in this Property(p-ID) |
There is an issue with the unit availability |
Check the unit status in Yardi to make any updates |
Unit(0000) is not available until mm/dd/yyyy. Does not meet desired Move-In date(mm/dd/yyyy) |
The applicant selected a move-in date before the unit is available |
Leverage the date change mechanism in the deal's primary view in the manager portal an edit button next to the rent value will allow you to do this now) to update the date; then re-sync. |
[pcode]: Approve Application event invalid. Guest must be in ‘Applied’ status. |
Related to a guest card either being canceled or moved to an invalid status in Voyager; sometimes this can be the result of a merge/deduplication effort by the client. |
Revert the guest to the status listed in the sync error and attempt to RESYNC |
[pcode]: Prospect Status is 'Resident', Prospect is not editable. Please use Resident Data web service to make changes |
Changes were made to the guest card directly in Yardi to convert them to a Resident. VERO cannot make updates once they are a resident. |
If possible, revert the changes in Yardi to make the guest a prospect. If that is not possible, you will need to accept the sync error and make updates manually in Yardi to correct any missing information that did not sync. |
[pcode]: CancelApplication event invalid. Guest must be in 'Applied', 'Approved' or 'Future Resident' status. |
Changes were made directly in Yardi to change the status of the guest. |
Revert the guest to the status listed in the sync error and attempt to RESYNC |