Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

This page contains all the steps needed for a proof of concept related to pushing data through a CODAT API, which will replace the file loading.

  • Customer -
    • Push all the customers from the FastTrack table or Update if it does not exist.
    • Get the Customer Key after each push and store it in a FastTrack table.
  • Sales -
    • Push all the Invoices from the FastTrack table.
    • Get the Invoice Key after each push and store it in a FastTrack table.
    • Push single and multiple items per invoice.
    • Push the reference by using the Supplemental data. (CODAT)
  • Journals -
    • Push all the Journals from the FastTrack table.
    • Get the Journal Key after each push and store it in a FastTrack table.
    • Push Multi transaction types per one JSON.
    • Check there is no limit to the number of transactions per push. (CODAT)
  • Codes -
    • Extract from CODAT all the charts of accounts and store them in FastTrack tables.
    • Extract from CODAT all the Tracking Categories and store them in FastTrack tables.
  • Error handling -
    • Basic error capturing - Only for Customers, extract and store an error in a FastTrack table per push.
    • Display information back to the current UI. (FT) Tamir is working on it.
  • Delete -
    This functionality is currently only supported for QuickBooks Online integration. For Xero, the process is to update the invoice status to VOID using the PUT Invoice call.
  • Solving Asynchornize processes - When I try to run not in a debug mode, I found out that the GUID is not populated in the Debtor's table because the process hasn't been finished
  • Mapping - Pushing all the fields from the FastTrack tables. (Currently, we are pushing only a few). (FT)
  • Un-invoice in Sales and Unpaid in Wages - These can be pushed as journal entries and reversal entries. Verify the process with CODAT.
  • Missing Accounts - Create a pre-validation step to capture all the missing accounts (FT)
  • Run the same process for MYOB -
    • Push and Get all the command types from the Dlls
    • Check the data in the MYOB account
    • Test Tracking Categories and Transactions Types.
    • Map all the columns for previous files of MYOB and check nothing is missing in the JSON.
  • Gap analysis -
    • Analysis to document differences between exporting by batch vs. API
    • Define product enhancements to support this.
    • Product enhancement request submitted.

  • No labels