---
id: post/aardvarklabs-blog/1891
type: post
title: Implementing a Multi-Step Process for AI Recommendations in Business Central
summary: This post demonstrates how to build a multi-step AI-assisted process in Business Central that generates product recommendations from sales order line descriptions. The process uses AI to identify keywords from sales line data, then searches the item catalog to recommend relevant products for users to add to their orders.
tier: community
language: en
tags:
  - ai recommendations
  - multi-step process
  - sales orders
  - full text search
  - json
  - item discovery
system: sales
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:00:42.586Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 42ba017ce2bc03f5c77db0beb330ea238cc601e447194330b2f722b8e813661f
evidence:
  - kind: blog
    url: https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/
    title: Implementing a Multi-Step Process for AI Recommendations in Business Central
    date: "2025-06-13"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/
    title: Implementing a Multi-Step Process for AI Recommendations in Business Central
    date: "2025-06-13"
    commit: null
    t: null
    quote: The AI Agent doesn't have to provide the entire answer. In this case it digested data that we could use in our process.
  - kind: blog
    url: https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/
    title: Implementing a Multi-Step Process for AI Recommendations in Business Central
    date: "2025-06-13"
    commit: null
    t: null
    quote: On line 18 we use the Full Text Search functions of Business Central that were introduced in release 25.2.
  - kind: blog
    url: https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/
    title: Implementing a Multi-Step Process for AI Recommendations in Business Central
    date: "2025-06-13"
    commit: null
    t: null
    quote: Because these are going into the user prompt, and ever 4-ish characters is a token and tokens cost money.
links:
  learn: []
  objects:
    - object/table/37
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "1891"
source_id: aardvarklabs-blog
source_name: Aardvark Labs
url: https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/
published_at: "2025-06-13T12:00:00.000Z"
author: Marcel Chabot
full_text: false
words: 1587
quotes:
  - text: The AI Agent doesn't have to provide the entire answer. In this case it digested data that we could use in our process.
    why_it_matters: This insight explains that AI should be designed as part of a workflow, not as a standalone solution, enabling better integration with existing business processes.
  - text: On line 18 we use the Full Text Search functions of Business Central that were introduced in release 25.2.
    why_it_matters: Highlights the use of Business Central's native Full Text Search capability to find items matching AI-generated keywords, avoiding the need to share entire catalogs with third parties.
  - text: Because these are going into the user prompt, and ever 4-ish characters is a token and tokens cost money.
    why_it_matters: Demonstrates practical cost optimization by limiting description input to 10,000 characters, showing awareness of AI token economics in production implementations.
code_objects_mentioned:
  - table ARD_CopilotItemRecommendations
  - page ARD_ItemRecomendations
  - codeunit ARD_CopilotItemRecommendations
  - page ARD_ItemRecommendationPrompt
  - table Sales Line
systems:
  - sales
  - copilot
versions_mentioned:
  - "25.2"
preview:
  embeddable: true
  frame_url: https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/embed/
  image: https://aardvarklabs.blog/wp-content/uploads/2025/06/18b65438-e978-4d45-8ac3-98a9f0a238fd.jpeg
  image_alt: null
  image_w: 1024
  image_h: 1024
  site_name: Aardvark Labs
  favicon: https://aardvarklabs.blog/wp-content/uploads/2024/04/design-1.png?w=32
  probed_at: "2026-10-07T11:52:01.236Z"
---

# Implementing a Multi-Step Process for AI Recommendations in Business Central

[Read the post](https://aardvarklabs.blog/2025/06/13/implementing-a-multi-step-process-for-ai-recommendations-in-business-central/) · Aardvark Labs (Marcel Chabot) · 2025-06-13 · 1587 words · tier community · reviewed (checked by Opus)

> This post demonstrates how to build a multi-step AI-assisted process in Business Central that generates product recommendations from sales order line descriptions. The process uses AI to identify keywords from sales line data, then searches the item catalog to recommend relevant products for users to add to their orders.

## Key points

- AI can play a supporting role in a multi-step process rather than providing complete answers
- The implementation collects sales line descriptions and passes them to an AI agent to extract keywords
- Keywords are used with Full Text Search (release 25.2) to find matching items in the catalog
- Users can select recommended items which are then automatically added as new sales lines
- Tracking token count by character length helps manage AI costs and improves result quality

## Quotes

- "The AI Agent doesn't have to provide the entire answer. In this case it digested data that we could use in our process." (This insight explains that AI should be designed as part of a workflow, not as a standalone solution, enabling better integration with existing business processes.)
- "On line 18 we use the Full Text Search functions of Business Central that were introduced in release 25.2." (Highlights the use of Business Central's native Full Text Search capability to find items matching AI-generated keywords, avoiding the need to share entire catalogs with third parties.)
- "Because these are going into the user prompt, and ever 4-ish characters is a token and tokens cost money." (Demonstrates practical cost optimization by limiting description input to 10,000 characters, showing awareness of AI token economics in production implementations.)

## AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

- table "ARD_CopilotItemRecommendations"
- page "ARD_ItemRecomendations"
- codeunit "ARD_CopilotItemRecommendations"
- page "ARD_ItemRecommendationPrompt"
- [table 37 "Sales Line"](../../objects/table/37.md)

Not found in BC28-30: table "ARD_CopilotItemRecommendations", page "ARD_ItemRecomendations", codeunit "ARD_CopilotItemRecommendations", page "ARD_ItemRecommendationPrompt".

## Context

- Features: AI-powered item recommendations, Full Text Search, JSON processing, Sales order line analysis, Temporary table management, Multi-step process design, Keyword extraction, Item selection and insertion
- Versions: 25.2

Source: Aardvark Labs, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.
