When to use this endpoint

Use to autocomplete the delivery/contact attention field. This returns saved text suggestions, not supplier or user IDs.

Authentication and permissions

Authenticate with signed API-key fields or a logged-in CRM session. Session requests use dispatcher CSRF protection when configured. API keys use their owner’s identity.

Purchase Order View is required on the singular or plural page. Records must be active and inside the configured TeamAccess or legacy Department Based Filter boundary; administrators are exempt from record restrictions. API-key requests use their owner’s identity. Related display names require the corresponding page View and record visibility.

Parameters

This endpoint has no operation-specific parameters.

Example request

$result = FM_api('PurchaseOrders_listAttention');

Example response

[
  {
    "attention": "Stores team"
  }
]

Errors and unusual responses

ResponseCondition
{"error":"not logged in"}No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.
{"error":"permission denied"}The required page permission is missing. Hidden/deleted records are omitted from collections; explicit parent readers reject an inaccessible parent.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

Behaviour and edge cases

  • Groups attention text from active visible headers, excluding NULL and exact empty strings. No trimming occurs; whitespace-only values can remain. Grouping follows database collation.
  • Returns one attention object per distinct value without guaranteed order, pagination or cap. All received statuses can contribute.

Side effects

  • Reads tenant data without modifying orders, lines, stock, approval, history or notifications.

See it in Fieldmotion

CRM1

In CRM1 Purchase Order details, edit delivery attention/contact information and inspect PurchaseOrders_listAttention; the client uses the returned strings as suggestions.

CRM2

No direct CRM2 literal caller was found in the searched client source.

Related endpoints