Negative Flows

The MPO processes handles and records all errors generated during different phases of the connector: extracting the data, performing transformations, posting the Dimension Values and the Journal Lines into Business Central.

Each negative use case is handled differently depending on what entity, Dimension Value or Journal Line, is sent to Business Central and depending in which phase of the processing the issue occurs.

Dimension Values

In case an error occurs during processing and posting of a Dimension Value, the following steps are executed automatically:

  • The Business Central API call is retried a number of times configurable in the setup phase;
  • Error details (errorProcess, errorMessage, errorSource, errorCode) are stored in the dedicated state diagram Failed dimension values SD;
  • A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Depending on the Mambu entity type and on the approach used for posting the Dimension Value in Business Central the following error handling cases exists:

  • Initial sync flow
    • Entity types handled: Branch, Loan Products, Deposit Products, Clients, Groups, Loan Accounts, Deposit Accounts;
    • The unposted Dimension Values should be manually posted.
  • Daily sync flow
    • Entity types handled: Branch, Loan Products, Deposit Products;
    • The unposted Dimension Values should be manually posted;
    • The Journal Lines processing and posting is not started. After posting all Dimension Values, the process Manual trigger should be manually started in MPO in order to process and post the Journal Lines in Business Central.
  • Real time sync flow
    • Entity types handled: Clients, Groups, Loan Accounts, Deposit Accounts;
    • The unposted Dimension Values should be manually posted, as soon as possible, preferably on the same day when the entity item was created.

Error Codes handled in retry mechanism

Business Central API call POST Dimension Value, errors handled:

  • Errors that involve a custom number of attempts:
    • HTTP codes:
      • 408 Request Timeout;
      • 429 Too Many Request;
      • 500 Internal Server Error;
      • 502 Bad Gateway;
      • 503 Service Unavailable
      • 504 Gateway Timeout.
    • Specific Business Central Error:
      • Category: Internal_*;
      • Description: ServerError.
  • Error that involves a single attempt:
    • HTTP code: 401 Unauthorized. In this case the Authorization Credentials are again retrieved from the Config SD and the API request retried.

Note: Any error needs to be investigated before the next run.

Journal Lines

Regarding the Journal Lines processing executed by the MS Dynamics - Business Central - Accounting connector the processes can be grouped into three phases: retrieving, enriching and posting the Journal Lines.

Depending on the phase in which the error occurs the following error handling cases exists:

Retrieve Journal Lines flow

In case an error occurs during this phase, the following steps are executed automatically:

  • The Mambu API call is retried a number of times configurable in the setup phase;
  • Error details (errorProcess, errorMessage, errorSource, errorCode) are stored in the dedicated state diagram Journal Lines processing errors SD;
  • The Queue where the Journal Lines batches are stored is emptied;
  • A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Error Codes handled in retry mechanism

The Mambu API call POST Search Journal Lines errors that involves a custom number of attempts:

  • HTTP codes:
    • 408 Request Timeout;
    • 500 Internal Server Error;
    • 502 Bad Gateway;
    • 503 Service Unavailable;
    • 504 Gateway Timeout.

Notes:

  1. Any error needs to be investigated before the next run.
  2. Process Manual trigger should be manually started in MPO in order to restart the Journal Lines processing.

Enriching Journal Lines flow

In case an error occurs during this phase, the following steps are executed automatically:

  • The Mambu API calls are retried a number of times configurable in the setup phase;;
  • Error details (errorProcess, errorMessage, errorSource, errorCode) are stored in the dedicated state diagram Failed dimensions attachment to JL SD;
  • A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Error Codes handled in retry mechanism

The Mambu API calls errors that involves a custom number of attempts:

  • HTTP codes:
    • 408 Request Timeout;
    • 500 Internal Server Error;
    • 502 Bad Gateway;
    • 503 Service Unavailable;
    • 504 Gateway Timeout.

Notes:

  1. Any error needs to be investigated before the next run.
  2. If one or more Dimension Values cannot be attached, the Journal Line will be posted in Business Central without these additional fields. The missing Dimension Values should be manually attached to Journal Lines in Business Central in order to have all the accurate details.

Posting Journal Lines flow

In case an error occurs during this phase, the following steps are executed automatically:

  • The Business Central API call will be retried a configurable number of times;
  • Error details (errorProcess, errorMessage, errorSource, errorCode) are stored in a dedicated state diagram Failed journal lines SD;
  • A task is logged in Mambu and assigned to the dedicated user specified in the setup phase.

Error Codes handled in retry mechanism

The Business Central API call POST Journal Line errors handled:

  • Errors that involve a custom number of attempts:
    • HTTP codes:
      • 408 Request Timeout;
      • 429 Too Many Request;
      • 500 Internal Server Error;
      • 502 Bad Gateway;
      • 503 Service Unavailable
      • 504 Gateway Timeout.
    • Specific Business Central Error:
      • Category: Internal_*;
      • Description: ServerError.
  • Error that involves a single attempt:
    • HTTP code: 401 Unauthorized. In this case the Authorization Credentials are again retrieved from the Config SD and the API request retried.

Notes:

  1. Any error needs to be investigated before the next run.
  2. Regarding the Journal Lines that could not be posted in Business Central there are two options:
    • Missing Journal Lines can be manually added in Business Central;
    • The already posted Journal Lines can be manually deleted from Business Central and the Manual trigger process must be started manually in MPO in order to restart the Journal Lines processing.