Is your feature request related to a problem? Please describe.
When retrieving Profiles or Impersonatees, multiple profiles often appear nearly identical.
For example:
- Same user name
- Different customer numbers
Without additional context, administrators cannot easily identify which profile belongs to which business or location.
Although this information already exists on the address records, it is not available through these endpoints.
This often requires additional API requests simply to identify the correct profile.
Describe the solution you'd like
Include the user's default billing address information as part of the Profiles and Impersonatees payload.
The intent is not necessarily to expose every address field, but to provide enough contextual information to distinguish profiles without requiring additional requests.
Describe alternatives you've considered
Making additional API requests to retrieve address information. This increases request count and client complexity.
Another alternative was to use a Repository, but that also requires an UserIndexBuilderExtender
Additional context
Examples such as city or region illustrate the type of contextual information that helps distinguish profiles, but the request is to expose the default billing address rather than specific individual fields.
Best Regards,
Nuno
Is your feature request related to a problem? Please describe.
When retrieving Profiles or Impersonatees, multiple profiles often appear nearly identical.
For example:
Without additional context, administrators cannot easily identify which profile belongs to which business or location.
Although this information already exists on the address records, it is not available through these endpoints.
This often requires additional API requests simply to identify the correct profile.
Describe the solution you'd like
Include the user's default billing address information as part of the Profiles and Impersonatees payload.
The intent is not necessarily to expose every address field, but to provide enough contextual information to distinguish profiles without requiring additional requests.
Describe alternatives you've considered
Making additional API requests to retrieve address information. This increases request count and client complexity.
Another alternative was to use a Repository, but that also requires an UserIndexBuilderExtender
Additional context
Examples such as city or region illustrate the type of contextual information that helps distinguish profiles, but the request is to expose the default billing address rather than specific individual fields.
Best Regards,
Nuno