Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Segment Field Is Not Loading in Work 365

Applies to: Work 365 (Dynamics 365 version) | Audience: System Administrators, Support Engineers

Summary

When working inside Dynamics 365, the Segment field in Work 365 may fail to populate (blank dropdown with a banner such as “Error loading Segment field”). This usually traces back to cache issues, missing/invalid API credentials, suspended Work 365 processes, or a partial/older solution version. The steps below help you diagnose and restore the field quickly.

Symptoms

  • Banner message: “Error loading Segment field”

  • Segment dropdown is empty or never populates

  • Behavior repeats across multiple records of the same entity

Why This Happens

The Segment field loads options dynamically and depends on:

  • Valid Work 365 API credentials configuration

  • Active Work 365 background processes/workflows

  • A consistent, up-to-date Work 365 solution

  • A clean browser cache (no stale scripts or blocked third-party cookies)

If any of these are missing/outdated/suspended, the field cannot retrieve data.

Resolution Steps

1) Clear Browser/Portal Cache (fastest checks)

  • Hard refresh: Ctrl + F5 (Windows) / Cmd + Shift + R (macOS).

  • Clear cache/cookies: Browser Settings → Privacy → Clear browsing data.

  • Test in Private/Incognito to rule out extensions/cached scripts.

  • (Optional) Power Pages/Portal: If the Segment field renders on a portal form, run Site actions → Clear website cache or Restart site in the Power Platform Admin Center, then retest.

2) Try a Different Browser

Open the same form in Edge/Chrome/Firefox.
If it works elsewhere, you’re likely facing a local cache/extension/session issue.

3) Confirm Work 365 Version & Clear Work 365 Cache

  • Verify you’re on the current supported Work 365 version.

  • In Work 365 → Admin Hub, select Clear Cache and then retest the field.

4) Recreate Work 365 API Credentials Configuration

  1. Open the Configuration list directly (replace with your URL):
    https://[your-dynamics-url]/main.aspx?pagetype=entitylist&etn=work365_configuration

  2. Locate Name = Work365.ApiCredentials and delete it.

  3. Re-run the post-upgrade/initialization or Admin Consent steps required by your Work 365 version to re-establish credentials.

  4. Refresh the app and test the Segment field again.

Tip: If your organization recently switched to an Application User, ensure the consent and connection are current and the Work 365 Service/Work 365 Portal Service roles are assigned.

5) Activate Suspended or Draft Processes

  1. Go to Settings → Advanced Settings → Processes.

  2. View: All Processes, filter Name contains “Work 365”.

  3. Add filter Status = Draft or Suspended.

  4. Open each and click Activate.

  5. Refresh the form and re-test.

Preventive Measures

  • After each upgrade, clear browser cache and Clear Cache in the Work 365 Admin Hub; spot-check key dynamic fields (e.g., Segment).

  • Keep Work 365 background processes active; periodically audit for Draft/Suspended status.

  • Maintain documentation for API credential setup (who/what/where) to avoid accidental deletions.

  • Use current browsers and test with Private/Incognito to isolate local issues quickly.