Importing Data from Aroflo into Reckon Hosted - Very Slow

  • 1
  • Question
  • Updated 5 months ago
  • Answered
Aroflo integration with Reckon Hosted
Photo of Joann Holmes

Joann Holmes

  • 100 Points 100 badge 2x thumb

Posted 5 months ago

  • 1
Photo of Rav

Rav, Community Manager

  • 49,488 Points 20k badge 2x thumb
Hi Joann,

Let me check in with our API team for their insight on this
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,002 Points 5k badge 2x thumb
Hi Joann,

The Hosted API is a very complex tool (far more complex than a desktop API or a cloud API) that enables a cloud app like AroFlo to talk to a desktop application (Reckon Accounts) that is also hosted in the cloud.

All developer partners, including AroFlo, are aware that the connection and completion time of the data sync can be significantly greater than the desktop API, although we are talking seconds not hours. 

We recommend they ensure their 'call' (the data back n' forth) to Reckon Accounts Hosted is as efficient as possible. We also recommend that once the API is authorised, it then uses an isolated user in the company file to make the calls so that you are not locked out of the file whilst the data is syncing. 

We will touch base with AroFlo to ensure the above recommendations have been followed. That said, AroFlo are fantastic partners so I am sure they will work with us to ensure the sync is functioning as you expect. 


Regards,
Jason
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,002 Points 5k badge 2x thumb
Hi Joann,

We contacted AroFlo and they did have a server issue at the time of your reported speed problems. This is now resolved. If you are still experiencing issues please let us know.


Kind regards,
Jason
Photo of Joann Holmes

Joann Holmes

  • 100 Points 100 badge 2x thumb
Hi Jason, this is an issue every time I try to integrate data. I am now trying to integrate now, just one invoice at a time this is the message I get on my screen after what seems an eternity of waiting. 
 An error occurred. AroFlo Technical Support has been notified.
I then go to Post Results tab, sometimes there is a message sometimes there nothing, like no attempt was made to even transfer data. Today I have this message.

400 Bad Request - Error connecting to Reckon Accounts. An internal Reckon Accounts error occurred while trying to access the Reckon Accounts company data file.

This is becoming very frustrating and extremely time consuming. We are paying for an integration to save us time. I could actually manually enter these invoices quicker than this whole process I am having to do on daily basis.
This seriously needs to be looked at.
Regards JoAnn
Photo of Joann Holmes

Joann Holmes

  • 100 Points 100 badge 2x thumb
I have just tried testing the connection, this is the error I am receiving. I'm really not sure if it's a Reckon problem or an Aroflo problem.

Error Message: 
Error connecting to Reckon Accounts. An internal Reckon Accounts error occurred while trying to access the Reckon Accounts company data file.
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,002 Points 5k badge 2x thumb
Hi JoAnn,

Thanks for that. Definitely not a speed issue any longer if you are getting that error. 

This generally means the Hosted API (connector) needs to be re-authorised. This happens from time to time to ensure only authorised users have access to your company file. It also may happen when we do a major change (as has occurred this week). 

AroFlo may need to assist. This is what they (or you) need to do.
  1. Send a call from AroFlo (sync) using the admin username and password to your company file (the company file must be closed to do this).
  2. Once completed you can revert to using the username that AroFlo was assigned previously (this may require a change under edit > preferences > integrated applications.

    Again.. AroFlo generally handle this for their clients. 
Please have them email reckonapi@reckon.com if they have any issues.
Photo of Joann Holmes

Joann Holmes

  • 100 Points 100 badge 2x thumb
Thank you.
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,002 Points 5k badge 2x thumb
Update:

Your other third party add-on vendor should also delete the lgb file that is located in the same folder as the QBW file. It will look like this...

myFileName.qbw.lgb

This file holds the authorisation information for the API. We have found that deleting this file BEFORE you reauthorise the app ensures that no legacy credentials are left behind. 

If in doubt your third party vendor should contact our API support team. 
(Edited)