The subscription ID that the user see in the portal is the only reference that the user has, but it's not the same ID as the unique ID that the API refers and uses. Problem is described in issue #1 but changing what we refer to as the "ID" will make it hard to have functions that are quick and responsive.
To make it easier for users to find the true Id, we added PublisherSubscriptionId from the API to the returned object. To make it even easier to find the correct subscription, adding a parameter to sort out the results based on PublisherSubscriptionId would make it easy even for large organizations to find the correct subscription.
The subscription ID that the user see in the portal is the only reference that the user has, but it's not the same ID as the unique ID that the API refers and uses. Problem is described in issue #1 but changing what we refer to as the "ID" will make it hard to have functions that are quick and responsive.
To make it easier for users to find the true Id, we added PublisherSubscriptionId from the API to the returned object. To make it even easier to find the correct subscription, adding a parameter to sort out the results based on PublisherSubscriptionId would make it easy even for large organizations to find the correct subscription.
This will be the fix #1