Search Results for

    Show / Hide Table of Contents

    LOADING OF FILES


    This option enables the loading of data contained in iConnect templates, supporting both the insertion of new records and the update of existing ones. It can be found within the "APP" section.

    Load button

    Some key points when updating data: To build a template for updating existing records, there are different approaches:

    • Retrieving data from Unit4 ERPx (template with data):

    The template is generated with data from the defined report, then you can proceed to amend the required values, and upload it. The system will amend what has been changed in the template.

    • Generating an empty template:

    Start from scratch by entering only the values required to update the existing data

    Regardless of the approach used, please note that the Master File ID in the main (first) tab of all templates is always mandatory

    STEPS OF THE PROCESS

    1) How to load excel templates with data?

    In the load template window, we can drag and drop the file we need to upload or click to pick it up from the desired folder.

    Load browse

    Once the archive is browsed and open, the file will be seen in the screen.

    Load browse file

    Remember you need to define at which Client you want to load the template, by selecting the check box in the environments section

    Load client screen

    Then it can be load by using the icon Upload files

    Load button screen

    2) How see the progress in the work queues?

    Once the file is processing, you can go to the menu option "Work queues" in order to see a progress bar showing the size and name of the file and the status.

    Load Work queues screen

    The upload in the image below hasn't started yet. There is no progress.

    Load files process 1 screen

    The upload in the image below has finiseh. The progress is over.

    Load files process 1 screen

    Note that you can add more than one file per run.

    This section includes the following info:

    • User: user from the company that executes the job
    • Filename: name of the template
    • Type: job type (generate-load)
    • Status: job status (not started, started, finished)
    • Environment: environment where the template was generated from
    • Client: client where the template was generated from
    • Creation: job date
    • Start: job start date
    • Finish: job finish date
    • Actions: Details, Delete, Download Template

    3) Result and status

    The process will go through different statuses: not startated, started.... until the process ends. The final status can be:

    • Finished: if the process ended correctly
    • Error: if ended incorrectly

    Once ended you will see the details in the section "Actions":

    Actions screen

    The 2 actions are:

    • Details: That takes to the "Task log"
    • Delete: Deletes the record

    ACTION-DETAILS

    We can see the Task log here, including the task log encrypted, the progress of the task and the icon for Transaction log.

    Task log screen

    ACTION-DELETE

    This opition, allows you to delete the generated job, a prompt window asking for your confirmation is shown:

    Load status screen

    4) Managing an error

    When in the "work queues" we see that the task has the status "Error", it means that the excel template is not correct and the data hasn't been uploaded.

    Load error 1 screen

    In order to track the error go to Actions details that will open the Task log menu.

    Load error is tasklog

    In the bottom of the screen, you can see the description of the errors.

    From the task log, you can go to the Transaction log and see the details of the error in each transaction.

    You can also download the excel log.

    Taslog download button

    In the downloaded excel log you will find the rows with error marked with an X in red, and if you move the pointer on this cell a message will indicate the error.

    Load template screen

    Once the data have been corrected, the file can be loaded again.

    5) Load templates for multicompanies

    In order to load a template for two or more companies, in the load window check the box for all the companies you need, marked in the green square on the picture below, and proceed as explained in the single company load section:

    Load multicompany screen

    6) Load settings

    Skip workflow check

    skip workflow check

    iConnect is designed so that when an active workflow exists, data cannot be sent to ERPx. By selecting the Skip Workflow Check option, this restriction is bypassed, allowing data to be loaded even if an active workflow is present.

    However, this does not mean that the workflow itself is skipped. Only the restriction on data loading is bypassed. This option serves as an acknowledgment by the user, allowing iConnect to send data to ERPx despite the presence of an active workflow.

    Overwrite Old Relations

    Given the way the Unit4 API manages relation PATCH operations in various master files, this option should only be activated when strictly required, to prevent unintended deletions or unexpected changes in relation values.

    7) Advanced Settings for loading files

    Please note that these options are only available for Admin users.

    Reqquisition screen

    Batch Size:

    Can help in reducing processing time depending of the size of the information being loaded by each row in the template, for instance, if you are loading �Financial Transaction� information it will have a lot of data in each line, in this cases increasing the Batch Size will make the load even longer since the process will need to manage larger amounts of data.

    In general, if each row has several fields the suggestion is to reduce the batch size, only if you are loading templates with a few columns in the template it could help to increase this value.

    Some other reason to decrease the size could be that: if any rows have errors, the error will be launched faster with a smaller batch size, due to iConnect having fewer lines to check; this happens because the errors are only being shown after the whole batch has been processed.

    Parallel API calls:

    This parameter indicates iConnect how many batches of processing can be launched at the same time; increasing it will affect the available resources for other tasks in the system and may cause errors or failures. It is not recommended to change it, it can help reducing times and can be tested but only increasing it in small values; for instance changing it from 2 to 4.

    In This Article
    Back to top Generated by DocFX