Connectors

/

Microsoft Dynamics 365 Business Central

/

Update a Dynamics 365 Business Central customer record
Write

Change credit and contact details on the right record, with evidence

For finance teams who want credit limit, block and contact changes made safely, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Update a Dynamics 365 Business Central customer record
Raise Contoso's credit limit in Business Central from 50,000 to 75,000.
Contoso's account supports a review of the limit. - Balance: 46,200, with 3,100 overdue - Payments: 128,000 paid in the last 180 days - Open orders: 2, worth 18,400 - Change: credit limit 50,000 becomes 75,000 Shall I apply the new credit limit?
Microsoft Dynamics 365 Business Central
Sample figures. Your results come from your own account.
No items found.

On this page

The problem

The problem

The prompt

Who it's for

How it works

Connector

Microsoft Dynamics 365 Business Central

Microsoft Dynamics 365 Business Central
Run it on your own Microsoft Dynamics 365 Business Central data.

Connect Microsoft Dynamics 365 Business Central, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Credit changes made without the evidence behind them

Raising a credit limit or blocking an account should be backed by the balance, overdue invoices and recent payments, and a block quietly stops open orders from shipping. Contact changes, meanwhile, belong on the contact record, not the customer card.

Without PopdockAI

  • Check the balance and overdue invoices by hand
  • Look up recent payments
  • Block an account without seeing the orders it stops
  • Put a person's details on the customer card

With PopdockAI

  • Credit changes come with balance, overdue invoices and 180 days of payments
  • Open orders a block would stop are listed
  • Changes to a person are routed to their contact record
  • You see a before and after table, and only changed fields are sent

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Apply `{changes}` to the customer `{customer-name}`.

Pass `{company}` as the company argument on every call. If `{company}` is empty, leave the company argument out so the connector's default company is used.

**Step 1: Resolve the customer**

Call `business-central-get-customer` with name.contains set to `{customer-name}`. If several match, list them and stop. Keep customer-number.

**Step 2: Evidence for credit changes**

If `{changes}` touches credit-limit or blocked, first gather: balance, balance-due, current credit-limit; `business-central-get-posted-sales-invoice` with sell-to-customer-number and remaining-amount.min 0.01 for overdue amounts; `business-central-get-detailed-customer-ledger` with document-type Payment and posting-date.from 180 days ago for recent payments; `business-central-get-sales-transaction` with document-type Order for open orders a block would stop.

**Step 3: Contacts**

If `{changes}` concerns a person at the customer, call `business-central-get-contact` with company-name set to the customer name and find the person. That change goes to `business-central-update-contact` with the contact number, not to the customer.

**Step 4: Preview and confirm**

Show a before-and-after table for each field, plus the credit evidence when relevant. Ask for confirmation.

**Step 5: Apply**

After confirmation call `business-central-update-customer` once with number set to the customer number and only the fields that change, and `business-central-update-contact` once per contact changed.

**Step 6: Confirm the result**

Re-read with `business-central-get-customer` and show the new values.

**Rules & Guidelines:**

* Do not call any create or update tool until the user has confirmed the exact values shown in the preview.
* Blocking a customer with open orders stops those orders from shipping; say so in the preview.

**Validation:**

* If `{changes}` is unclear, ask before reading anything else.

Who it's for

One answer, three teams that use it

Credit managers

Back credit decisions with the facts

Balance, overdue invoices and recent payments are shown before a limit changes.

Raise Fabrikam's credit limit in Business Central to 40,000 and show me their payment history first.

Accounts receivable

Block accounts without surprises

Open orders a block would stop are listed, so nobody is caught out by held shipments.

Block Northwind Traders in Business Central for shipping and tell me which orders it affects.

Customer service

Update contact details in the right place

Changes to a person go to their contact record, keeping the customer card clean.

Update the email for Contoso's buyer Priya Shah in Business Central to priya.shah@contoso.com.

How it works

What PopdockAI does when you ask

You name the customer and the change and your AI assistant gathers the evidence from Business Central first. Nothing is written until you confirm, and the customer is read back.

01

Ask

You name the customer and describe the change.

Your AI tool

02

Check

For credit changes it reads balance, overdue invoices, payments and open orders.

No items found.

03

Confirm

Contact changes go to the contact record, and you see a before and after table.

No items found.

04

Apply

It sends only the changed fields and reads the customer back.

Your AI tool

The outcome

Customer changes on the right record, with evidence

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation