URL Actions

URL Actions (Action Type 7, Enum Value 7) automatically open web pages, documents, or applications when business rules execute. This capability enables seamless integration with external systems, provides access to reference documentation or tools during Business Central workflows, and allows business rules to trigger web-based processes or display information from external sources. URL actions bridge Business Central with the broader technology ecosystem that supports your organization's operations. This section explains when URL actions are appropriate, how to configure them correctly, and how to construct dynamic URLs that pass context-specific parameters to external systems.

12.1 When to Use URL Actions

URL actions are appropriate when business rules should provide immediate access to external web-based resources or trigger web-based processes that complement Business Central operations.

Appropriate Use Cases for URL Actions

Opening Approval Forms in External Systems: When your organization uses external approval systems (for example, SharePoint workflows, custom web applications, or third-party approval platforms), URL actions can automatically open the appropriate approval form when Business Central transactions require authorization. The URL can include transaction details as parameters, pre-populating the approval form with relevant context.

Displaying Product Documentation or Technical Specifications: When users are working with items that have detailed technical specifications, safety datasheets, or assembly instructions stored in external document management systems, URL actions can automatically open the relevant documentation based on the item number. This ensures that users have immediate access to critical information without needing to search document repositories manually.

Launching External Pricing or Inventory Lookup Tools: When your organization uses external systems for competitive pricing analysis, real-time inventory availability across distribution networks, or supplier catalogs, URL actions can open these tools with pre-populated search parameters based on the current Business Central transaction context.

Opening CRM or Customer Support Systems: When Business Central transactions require coordination with customer relationship management (CRM) systems or support ticketing platforms, URL actions can automatically open the relevant customer record or create a new support ticket with transaction context already populated.

Accessing Compliance Documentation or Policy References: When business rules enforce compliance requirements or company policies, URL actions can provide direct links to the relevant policy documents, regulatory references, or standard operating procedures. This ensures that users can quickly access authoritative guidance when questions arise.

Integrating with Geographic or Mapping Services: When transactions involve shipping, logistics, or field service operations, URL actions can open mapping services with addresses pre-populated, enabling route planning or distance calculations without manual data entry.

Launching Business Intelligence or Analytics Dashboards: When users need to view analytical context related to the current transaction (for example, customer purchase history, sales trends, or inventory forecasting), URL actions can open dashboards filtered to the relevant data.

When NOT to Use URL Actions

Frequent or Routine Operations: Opening URLs interrupts user workflow by launching a web browser or opening a new tab. If the action would occur for every routine transaction, the interruption becomes disruptive to productivity. Reserve URL actions for situations where external information access provides significant value that justifies the workflow interruption.

Untrusted or Unvalidated URLs: Only open URLs to systems and domains that your organization controls or explicitly trusts. Do not construct URLs using unvalidated user input or external data sources that could be manipulated to redirect users to malicious websites.

Operations Requiring Data Exchange: URL actions simply open web pages; they do not exchange data between Business Central and external systems. If your requirement is to send data to external systems or retrieve data from external systems, consider using Custom Actions with API integration or Power Automate Actions instead of URL actions.

12.2 Configuring URL Actions Step by Step

This section provides detailed instructions for creating and configuring URL actions within your business rules.

Step 1: Create or Open the Business Rule

1. Navigate to the Business Rules page in Business Central

2. Open the Business Rule Set that should trigger URL navigation

3. Create a new Business Rule or open an existing rule that requires external resource access

4. Configure the Condition that determines when the URL should open

The condition should evaluate to TRUE when the business event requiring external resource access occurs. For example, if you want to open product documentation when users add high-value items to sales orders, the condition might be {[37:15] * [37:22]} is >1000 (line amount exceeds $1,000).

Step 2: Add a New URL Action

1. In the Actions section of the Business Rule, create a new action line

2. Set the Action Type field to URL (this is Action Type 7 in the enum)

3. The new action line is now configured to open a URL when the condition evaluates to TRUE

Step 3: Configure the URL

1. In the action line, locate the Action Code or URL ID field

2. Enter a new code (for example, URL001) or select an existing URL configuration

3. Open the URL Detail card by selecting the Action Code field

4. On the URL Detail card, locate the URL Link or URL field

5. Enter the complete URL that should be opened

URL Format Requirements:

• URLs must begin with http:// or https://

• URLs must be properly formatted and accessible from the Business Central client environment

• URLs can include query string parameters to pass data to the target system

Example Static URL:

Example URL with Query Parameters:

Step 4: Save and Test

1. Save the URL Detail card

2. Save the Business Rule

3. Test the configuration in a sandbox environment by creating a transaction that meets the condition

4. Verify that the URL opens in a web browser

5. Verify that the destination page loads correctly and displays the expected content

User Experience Note: When the URL action executes, Business Central will open the URL in the user's default web browser. If the user is working in the Business Central web client, the URL typically opens in a new browser tab. If the user is working in the Business Central desktop client (for older versions), the URL opens in the default system browser.

12.3 Dynamic URLs with Placeholders

The true power of URL actions emerges when you construct dynamic URLs that pass transaction context to external systems using placeholder syntax. This enables the external system to display or process information specifically relevant to the current Business Central transaction.

Basic Placeholder Syntax in URLs

You can include QUALIA Rule Engine placeholders within URL strings using the standard [TableID:FieldID] syntax:

https://crm.company.com/customer?id=[18:2]

When the rule executes, QUALIA Rule Engine substitutes the placeholder with the actual field value. If the Customer No. is "CUST001", the resulting URL becomes:

Passing Multiple Parameters

Construct URLs with multiple query string parameters to pass comprehensive context:

https://pricing.company.com/lookup?item=[37:6]&quantity=[37:15]&customer=[36:2]

This passes the item number, quantity, and customer number to an external pricing tool, enabling it to calculate customer-specific pricing based on quantity breaks.

Example: Opening Product Documentation

Scenario: When users add items to sales orders, automatically open the product datasheet from your document management system.

Configuration:

• Trigger Table: 37 (Sales Line)

• Condition: [37:6] is <>' (Item No. is not blank)

• URL: https://docs.company.com/products/[37:6]/datasheet.pdf

If the user adds item "ITEM12345" to a sales line, the URL becomes https://docs.company.com/products/ITEM12345/datasheet.pdf, opening the specific product's datasheet.

Example: Creating Pre-Populated Support Tickets

Scenario: When errors occur during order processing, automatically open your support system with error context pre-populated.

Configuration:

• Trigger Table: 36 (Sales Header)

• Condition: [Error condition detected]

• URL: https://support.company.com/create?type=order-error&order=[36:3]&customer=[36:2]&amount=[36:61]

The support system receives all relevant order context, enabling support staff to begin troubleshooting immediately.

URL Encoding Considerations

When including placeholder values in URLs, be aware that some field values may contain characters that require URL encoding (for example, spaces, special characters). Business Central typically handles basic URL encoding automatically, but if you experience issues with URLs not opening correctly, verify that special characters in field values are properly encoded.

Example: If a customer name is "Smith & Jones", the ampersand (&) should be URL-encoded as %26:

12.4 Opening Business Central Pages with Filters

A particularly useful application of URL actions is opening other Business Central pages with specific filters applied, enabling users to navigate to related information without manual searching.

Business Central URL Structure

Business Central pages can be opened via URL using this general format:

https://[BC-instance]/[tenant]/[page-id]?[filters]

Example: Open Customer Card from Sales Order

Scenario: When reviewing a sales order, provide a quick link to open the customer card for the order's customer.

URL Configuration:

https://businesscentral.dynamics.com/[your-tenant]/page/21?filter='No.' IS '[36:2]

This opens the Customer Card page (Page 21) filtered to the specific customer from the sales order.

Note: Constructing Business Central URLs requires knowledge of your specific Business Central instance URL structure and page IDs. Consult your Business Central administrator or Microsoft documentation for the correct URL format for your environment.

12.5 Best Practices for URL Actions

Use Only Trusted Domains

Only configure URLs that point to systems your organization controls or explicitly trusts:

✅ Safe: https://company.sharepoint.com/approvals ✅ Safe: https://yourapp.company.com/... ❌ Unsafe: https://[18:102] (URL domain from user-entered field) ❌ Unsafe: https://unknown-external-site.com/...

Validate URL Construction

Before enabling URL actions in production, test with various data values to ensure URLs construct correctly:

• Test with typical field values

• Test with blank field values

• Test with special characters in field values

• Test with very long field values

Consider User Experience Impact

Opening URLs interrupts workflow. Use URL actions only when the external information provides significant value:

✅ Appropriate: Opening safety datasheet for hazardous materials ✅ Appropriate: Opening approval form for high-value transactions ❌ Excessive: Opening URLs for every routine transaction

Document External System Dependencies

URL actions create dependencies on external systems. Document:

• What external system the URL opens

• Why the integration is necessary

• What to do if the external system is unavailable

• Who maintains the external system

Handle Browser Popup Blockers

Some users may have browser popup blockers enabled. Test your URL actions with common browser configurations and provide guidance to users if popup blockers prevent URLs from opening.