Connectors

/

Microsoft Dynamics GP

/

Close a Dynamics GP service call
Write

Close service calls only when the work is really done

For field service teams who want a Dynamics GP service call closed safely after checking its work orders, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Close a Dynamics GP service call
Close Dynamics GP service call SVC-1042 for Northwind Traders, completed today.
SVC-1042 has 2 work orders, both complete, so it can be closed. - Customer: Northwind Traders - Technician: Sam Patel - New status: COMPLETE, dated today - Unchanged: technician, priority and description Shall I close the call?
Microsoft Dynamics GP
Sample figures. Your results come from your own account.
microsoft-dynamics-gp-get-srv-service-call
microsoft-dynamics-gp-get-srv-work-order
microsoft-dynamics-gp-get-srv-service-status
microsoft-dynamics-gp-srv-service-call-update

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Microsoft Dynamics GP

Microsoft Dynamics GP
Run it on your own Microsoft Dynamics GP data.

Connect Microsoft Dynamics GP, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Service calls closed while work orders are still open

Closing a field service call in Dynamics GP while a work order is still open leaves billing and history out of step. You have to check every work order, find the status code that means complete and update only the call.

Without PopdockAI

  • Open the service call and every work order on it
  • Check each work order is really finished
  • Guess which status code means completed
  • Risk changing the technician or priority by mistake

With PopdockAI

  • It stops if the call is already closed
  • It refuses to close while any work order is still open
  • The completed status is picked for you, or it asks
  • The call is updated once and read back, other fields untouched

The prompt

Use this prompt

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

Prompt
**Objective:** Close service call `{service-call-number}` with completion date `{completion-date}` (default today), but only after checking nothing is still open against it and the user has confirmed.

Pass `{company}` as `company` on every call (if it is empty, omit `company` and the default company is used).

**Step 1: Read the call**

Call `dynamics-gp-get-srv-service-call` with `service-call-number` set to `{service-call-number}`. If nothing matches, stop and say so. If it already has a `complete-date`, stop and report it is already closed. Note `service-record-type`, `service-call-status`, `tech-id`, `customer-id` and `service-description`.

**Step 2: Check for open work**

Call `dynamics-gp-get-srv-work-order` with `service-call-number` set to `{service-call-number}`. If any work order has no `complete-date`, stop: list those work orders and tell the user they must be completed first.

**Step 3: Pick the status**

Call `dynamics-gp-get-srv-service-status` and choose the `status` code whose `description` means completed or closed. If no single code clearly means that, list the codes and ask the user which one to use.

**Step 4: Confirm**

Show the user: call number, customer, technician, description, current status, the new status code, and the completion date. Ask for explicit confirmation. Do nothing further without a clear yes.

**Step 5: Write, once**

Call `dynamics-gp-srv-service-call-update` exactly once with `call-number`, `record-type` (the `service-record-type` from Step 1), `call-status` (the chosen code) and `complete-date`.

**Step 6: Verify**

Call `dynamics-gp-get-srv-service-call` again and report the stored status and completion date. If the write failed or the values did not change, report the error as returned. Do not retry automatically.

**Rules & Guidelines:**

* `dynamics-gp-srv-service-call-update` is the only write tool this prompt may call, and only after Step 4's confirmation.
* Do not change the technician, priority or description, even if they look wrong; mention it instead.
* Do not call `dynamics-gp-srv-equipment-update`, `dynamics-gp-srv-rma-update` or any other write tool.

**Validation:**

* If more than one call matches the number (for example an open and a history record), list them and ask which one.

Who it's for

One answer, three teams that use it

Service coordinators

Close calls without checking every work order

Open work orders are listed before anything changes, so a call is never closed with work still outstanding.

Close service call SVC-2290 in Dynamics GP, the work finished yesterday.

Field technicians

Finish a job from the van

Close your call in one message when the job is done, and the technician and description stay exactly as they were.

I have finished service call SVC-1188 at Fabrikam. Mark it completed in Dynamics GP for today.

Service managers

Keep billing and history in step

Calls close only when every work order is done, so billing runs on finished work and the service history is accurate.

Can we close Dynamics GP service call SVC-3051 for Contoso yet, or are work orders still open?

How it works

What PopdockAI does when you ask

You give the call number and completion date, and your AI assistant checks every work order in Dynamics GP first. The call is updated only after you have seen the change and approved it.

01

Ask

You give the service call number and a completion date.

Your AI tool

02

Check

It reads the call and stops if any work order on it is still open.

microsoft-dynamics-gp-get-srv-service-call
microsoft-dynamics-gp-get-srv-work-order
microsoft-dynamics-gp-get-srv-service-status

03

Confirm

You see the call, customer, technician and new status and approve.

No items found.

04

Update

It updates the call once and reads it back.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Microsoft Dynamics GP and one secure connection to your AI tool. No code, no exports.

get-data

microsoft-dynamics-gp-get-srv-service-call

Returns service call records from Dynamics GP Field Service, including customer, service type, status, technician, priority and totals. Filter by total, service type, customer ID, office ID, service call status, name, priority level and service call number, and pick the company and the maximum number of records.
get-data

microsoft-dynamics-gp-get-srv-work-order

Returns depot work orders from Dynamics GP Field Service, showing the customer, inbound item and serial number, work order type and status, key dates and labor and part costs. Filter by work order number, office ID, inbound item number, work order type, service call number, work order status, entry date and customer name, and pick the company and the maximum number of records.
get-data

microsoft-dynamics-gp-get-srv-service-status

Returns the service call status codes defined in Dynamics GP Field Service, with their descriptions. Filter by description and status, and pick the company and the maximum number of records.
run-action

microsoft-dynamics-gp-srv-service-call-update

Updates a service call in Dynamics GP through eConnect; GP defaults any field not listed. Requires call number and record type. Optional: call status, service type, technician ID, priority, complete date and arrival date. Writes to the live Dynamics GP company database.
Read only.Nothing in Microsoft Dynamics GP Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Calls close only when the work is done

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