Table of Contents

Setup Guide

Purpose

This guide explains how to configure and run the Linc Micros Integration in Business Central.

Prerequisites

  1. Publish and install the extension in your Business Central environment.
  2. Have valid Oracle Micros BI API credentials.
  3. Confirm your BI API account can authenticate with the Oracle auth server.
  4. Confirm your organization identifier and location reference are correct.

Required Configuration Values

Populate these values in Third Party Setup for Micros:

  1. Auth Server URL (example: https://your-auth-host)
  2. Client ID
  3. Username
  4. Password
  5. Org Identifier

Notes:

  • Do not include trailing slash in server URLs.
  • The Code Verifier field can be left blank. The extension now generates one automatically when needed.

Step-by-Step Setup

  1. Open Business Central and go to Third Party Setup.
  2. Create or open the Micros integration setup card.
  3. Enter Auth Server URL.
  4. Enter Client ID.
  5. Enter Username.
  6. Enter Password.
  7. Enter Org Identifier.
  8. Enter Location.
  9. Set Last Transaction Date to the date before the first date you want to import.
  10. Optional: enable duplicate document check if required by your process.
  11. Save the setup card.

Run the First Import

  1. On the same setup card, run action Import Micros Web Data.
  2. The integration performs:
    • Authorize
    • Sign In
    • OAuth Token
    • Get Guest Checks
  3. Wait for completion message: Guest Checks import completed.

Verify Results

  1. Open the transaction table or page used by your process.
  2. Confirm transactions were created for the expected business date.
  3. Confirm payment method values were populated from tender media.

Date Behavior

The import advances from the stored last transaction date by one day:

  • Logic: CalcDate('<1D>', LastTransDate)

If you see unexpected date results, verify user/regional date format in Business Central (dd/mm/yyyy versus mm/dd/yyyy).

Troubleshooting

Authentication fails

  1. Recheck Auth Server URL and Client ID.
  2. Recheck Username, Password, and Org Identifier.
  3. Verify org identifier value is exactly what Oracle expects.
  4. Confirm no proxy/firewall is blocking outbound calls.

Sign-in works but token fails

  1. Confirm the auth code is returned in redirectUrl.
  2. Confirm Client ID matches the same account used for sign-in.
  3. Retry after clearing and re-entering credentials.

No guest checks imported

  1. Verify Location value is valid for the organization.
  2. Verify Last Transaction Date and expected business date.
  3. Check whether source system has data for that date.

Operational Recommendation

  1. Run imports on a schedule.
  2. Monitor for failed runs and capture HTTP status and reason phrase.
  3. Keep credentials rotated and updated in setup.