This Word guide explains how to calculate a Distinct Count by Customer and Partner in SQL. Begin by keeping the source table at one row per CustID, Partner, and EdiToDoNo instead of pre-expanding numbered columns. The next decision comes from the second check: in SQL, group by the requested filter grain and calculate COUNT(DISTINCT EdiToDoNo).
What You Need Before You Calculate a Distinct Count by Customer and Partner in SQL
The scope is defined by the exact Word account, platform, file location, and control named in the workflow. Keep the test on the affected item, and use the result of the first two checks before changing a broader setting.
The Exact Word Workflow
Follow these steps in order. If a step changes data, permissions, authentication, or a subscription, record the current state first and keep a recoverable copy or backup method.
- Keep the source table at one row per CustID, Partner, and EdiToDoNo instead of pre-expanding numbered columns.
- In SQL, group by the requested filter grain and calculate COUNT(DISTINCT EdiToDoNo).
- When multiple partners are selected, calculate the distinct count after both filters so repeated order numbers count once.
- Validate C1 alone, C1 with P1 and P2, and C2 against the expected counts 3, 3, and 1.

Confirm the Calculate a Distinct Count by Customer and Partner in SQL Result
Repeat the original Word action with the same account, file, and device. A successful result means the reported symptom no longer appears, the intended setting persists after reopening, and no unrelated file, user, or subscription has changed.
Use WPS Office as a Free Microsoft Office Alternative
WPS Office cannot directly change this Microsoft-side Word account, cloud service, tenant policy, license, subscription, or proprietary app state. Use the Microsoft controls above for the original issue.
When you still need to work with local files, WPS Office is a free, lightweight Microsoft Office-compatible alternative with Writer, Spreadsheets, Presentation, PDF tools, and WPS AI. It opens and saves common DOCX, XLSX, and PPTX files and supports everyday editing in a familiar interface. Complex macros, add-ins, tenant permissions, and Microsoft-only cloud integrations may not transfer exactly, so verify advanced files before replacing the original.

Word FAQs About Calculate a Distinct Count by Customer and Partner in SQL
Will every Word user get the same result when trying to calculate a Distinct Count by Customer and Partner in SQL?
Not necessarily. The result depends on the account type, file location, app version, permissions, and device involved in this exact workflow.
What details matter before I try to calculate a Distinct Count by Customer and Partner in SQL?
Record the exact message, affected account or file, platform, and the result of this first check: Keep the source table at one row per CustID, Partner, and EdiToDoNo instead of pre-expanding numbered columns.
What result should I expect after the final step?
The expected result is the one established by the final check: Validate C1 alone, C1 with P1 and P2, and C2 against the expected counts 3, 3, and 1.
When would this Word workflow require administrator access?
Administrator access is required only when the named control belongs to tenant policy, billing, authentication, service health, or organization-wide permissions.




