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 2 Next »

This node was written specifically to pull data from a BC endpoint into GlobalCapture. It uses service to service oAuth login flow described here. Before attempting to use this node, be sure to follow the steps outlined for configuring auth.

Setup

You will need the Tenant ID, Client ID, and Client Secret to authenticate and make requests. It’s highly recommended you test your configuration outside of a Capture flow by following the instructions here.

Note that the Client Secret is the VALUE, not the ID. You must have the Client Secret Value, and if you do not, you will need to request a new client secret be made. It can not be retrieved after the fact.

  • Authorization URL
    At the time of publishing, the correct oAuth 2 endpoint is:
    https://login.microsoftonline.com/YOURTENANTIDHERE/oauth2/v2.0/token
    Do not forget to use the correct Tenant ID.

  • Client ID
    The raw client ID value.

  • Client Secret
    The raw client secret value.

  • Scope
    For Business Central, the default scope should be:
    https://api.businesscentral.dynamics.com/.default

  • o365 Endpoint
    The full path, including any filtering parameters to execute an HTTP GET against. Endpoints for the various BC objects can be found here.

BC supports “custom” endpoints. Integrators may develop non-standard routes to present or join specific data elements. If the customer is using non-standard routes, the integrator will need to be involved to secure the routes properly and ensure they are published to the correct deployment (production, sandbox, etc).

Date

Version

Description

11/21/2022

1.0

Initial node release.

  • No labels