Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
Thanks for reploy Jack, we actually develop the soluction for the business ourselves. And we understand that they GUID will be generated when the migration happens. The reson why we ask is that we noticed after the upgrade, the Card Id will become the Display ID in the AccountRight Live, and the key id like EmployeeId from the ODBC drive we can't mapping to any of the field (the key id is used for our other system to link the entry).
Let me know if i missed something.
Hi there @AndrewDing,
AccountRight Live and AccountRight Classic have different ways to integrate so its not as simple as simply pointing the current solution at the new file.
In the AccountRight Live API you can uniquely identify an employee (or any other record/resource) by its UID - this is a GUID unique to the resource. The "DisplayId" field is what you see in-product and is likely what you're using from the ODBC driver in AccountRight Classic.
As far as upgrading goes, I'd recommend reaching out to your third-party solution and ensure they're compatible with AccountRight Live and the REST API. All the documentation is up at developer.myob.com and they can reach out to firstname.lastname@example.org for support if they need.
Hope this helps!
We have a 3rd party intergation soluction for AccountiRight V19, currently we are upgrading our solution to support the new account right online. Just one issue, currently our customer don't use "Record Id" in V19, we use the primary key like "EmployeeId" from the odbc drive to do the link. How can we mapping the existing record after the migration to AccountRight Online?