Exact Globe+ Integration

Exact Globe+ (formerly Globe Next) REST services are exposed through proxy endpoints. Environment headers select the Globe+ database and server.

Environment ​

{
  "ServerName": "YOUR-SERVER",
  "ConnectionString": "Server=YOUR-SERVER;Database=500;Trusted_Connection=True;",
  "Headers": {
    "DatabaseName": "500",
    "ServerName": "YOUR-SERVER",
    "Origin": "Portway"
  }
}

Proxy endpoints ​

{
  "Url": "http://localhost:8020/services/Exact.Entity.REST.EG/Account",
  "Methods": ["GET", "POST", "PUT", "DELETE"],
  "SupportsOData": true,
  "AllowedEnvironments": ["500", "700"]
}

Globe+ URLs in responses are rewritten to the Portway URL, e.g. http://localhost:8020/services/Exact.Entity.REST.EG/Account(guid'123') to https://api.company.com/api/500/Account(guid'123'). Behind a TLS-terminating proxy, the scheme is taken from X-Forwarded-Proto only when the proxy is listed in ForwardedHeaders (Application Settings).

Composite endpoints ​

The sample composites create lines and a header that share a generated TransactionKey, which Globe+ processes as one entry.

POST /api/{env}/composite/SalesOrder
Content-Type: application/json

{
  "Header": { "OrderDebtor": "60093", "YourReference": "Connect async" },
  "Lines": [
    { "Itemcode": "ITEM-001", "Quantity": 2, "Price": 0 },
    { "Itemcode": "ITEM-002", "Quantity": 4, "Price": 0 }
  ]
}

POST /api/{env}/composite/FinancialEntry
Content-Type: application/json

{
  "Header": { "Journal": "90", "Description": "Invoice payment" },
  "Lines": [
    { "GLAccount": "1000", "Amount": 1000, "Description": "Payment received" },
    { "GLAccount": "1300", "Amount": -1000, "Description": "AR clearing" }
  ]
}

Steps run in order; a failed step stops the composite, and earlier steps are not undone. The response names the failed step. Configuration: Composite Endpoints.

Troubleshooting ​