What is the wait time on developer program application?
What is the current wait time for a developer account? MYOB website says it can be turn around within a day. The email confirmation I got says up to 5 business days. My application has been pending for almost 2 weeks. I tried to follow up by replying to the email but no response. It seems like there are no other way to contact the team to get an update. Does anyone have any success with this? In case anyone here can help internally, my ticket number is 49966.
CC Email field is not presented in the v2 customer endpoint data
In the MYOB web dashboard., to create a customer contact., its interface is able to add email together with CC email for a customer address (see screenshot)., however., I can not find the "CC email" field in this MYOB endpoint api document https://developer.myob.com/api/myob-business-api/v2/contact/customer/ ., only the email field is there for a customer addressNot receiving CC Email field in v2 Contact endpoint
I am able to add multiple CC Emails from the Create/Edit Contacts web GUI, but when fetching the Contact data, either through list all or even find by Name, I am not receiving any CC Emails data. https://developer.myob.com/api/myob-business-api/v2/contact/personal/ I can see the Emails in the Address array, separated by a semi colon ";" in case of multiple emails, but not the CC Emails.
MYOB TEAM API for Geolocation, Clock on/off status, leave and Rooster
Hello MYOB API Support Team, I would like to suggest several feature enhancements related to MYOB Team and the MYOB Business API that would be very useful for workforce monitoring and system integration. 1. Clock On/Off & Geolocation via API It would be very helpful if clock on/off status and geolocation data could be pushed or made available via the API in real time. (why is it currently a problem) Because currently, there are no warning indicators in the timesheet user interface when managers are approving employee timesheets, especially for the following situations: No warning when an employee starts working before their scheduled roster time. This may cause financial loss to the company, as working hours outside the roster schedule are not paid. No warning when an employee works late or exceeds their scheduled start and end times. No warning when an employee clocks on or clocks off outside the designated geolocation area. No warning when an employee forgets to clock on when their roster starts, or forgets to clock off when their roster ends. In addition, the current user interface for accessing geolocation information is not practical. I suggest displaying the geolocation details directly on the timesheet page, next to the clock on and clock off times, so managers do not need to click through multiple pages to access this information. 2. Ability to see users who have logged In but not out At the moment we can only see data once both clock in and out has been completed. It would be very useful to be able to see users who have clocked in but not yet clocked out. This would enable: Identification of people who have forgotten to clock in Identification of people who are absent (not clocked in) so a welfare check can be conducted Identification of people who clocked in late so that immediate performance management can be done Identification of people that have clocked in but forgotten to clock out 3. Ability to Remove Leave Requests and also access by API Remove from website and app - We would like to see the leave function removed as many businesses would prefer not to manage leave requests this way. It is also likely to confuse many employees who do not have leave entitlements (like casuals) If it is to remain, API access would be handy so that we can retrieve all requests and ensure they are responded to It would be useful to have API functionality to cancel or remove submitted leave requests when required. 4. Push Notification Support Push notifications for people who have not clocked in to a rostered shift or clocked out would be very handy! Even better would be for that notification to be sent once the person is within their geodata region but hasn’t clocked out, but also if they are clocked in but leave the geodata location An employer option to decide whether the app can only be used if location services is set to ALWAYS would also be very handy. This could be at the option of the employer? Can we access roster through API? Thank you
API Developer Access
Is it possible to have an all around API Access to any MYOB Account? Example: MYOB_1 API access can be used to multiple accounts, (MYOB_2, MYOB_3) just by using one API Key from MYOB_1? or is it unique per every account? The purpose is for make.com automation/integration. --------------------------------------------------------------------------------------------------------------------
API Internal Server Error 500 on Odata Filter Queries
Hi team, As of Monday afternoon 10/12/2024 we started receiving Internal Server Errors (500) on any Odata Filter query raised using the .NET SDK. No changes to the solution have been made, there appears to be a breaking change or an issue on the API endpoint/server. We have no problems in submitting orders via the API. Any breaking changes in the API or AccountRight company cloud files? Assistance is urgently required.
How to add the due date when posting an MYOB invoice from the API
We post sales invoices from third-party software to MYOB AccountRight. We can post invoices to MYOB but can't set the Invoice Due Date. Without Due Date, it works well and AccountRight Invoice is set as "Cash on delivery". What we need is to put it as "Due on this day" with the due date we sent. "Terms": { "PaymentIsDue": "Dueonthisday", "DueDate": "2024-07-26T00:00:00" }, Invoice Terms have been sent as above (Full JSON file is attached here). But I get the validation valid error: "Unexpected value for 'Terms.PaymentIsDue': Cannot convert 'Dueonthisday' to a valid value." Does anyone know how to post the due date?