-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get-PCUsage compatitble command #44
Comments
Hi @VaperWare, When you invoke the Get-PartnerCustomerSubscriptionUtilization it will return the resource URI. Are you finding that the value is missing? You will need to pipe the output from the command through the Format-List command. The following is an example Get-PartnerCustomerSubscriptionUtilization -CustomerId <Customer ID> -SubscriptionId <Subscription ID> -StartDate (Get-Date).AddDays(-2).ToUniversalTime() -EndDate (Get-Date).ToUniversalTime() -Granularity Daily -ShowDetails | FL -force * When you do this all of the available properties will be written to the screen. The module is using a output formatter that set the default output style for certain commands. This was done due to the amount of data returned. We decided to implement it in this way to make it more friendly and output the most commonly used information by default. I hope that this helps! |
Thanks for the update, I do see the URI information when it's piped to the screen, so I'm probably missing something, but is there not a way to return the URI back to an object for processing ? |
Hi Gerald,
That value is returned as part of the object. So, when you are iterating through the collection of results you will be able to reference it. The current formatting configuration only impacts the default output to the console. All of the underlying properties are still present and can be used as you normally would.
Isaiah Williams
…________________________________
From: Gerald Parish <notifications@github.com>
Sent: Sunday, November 25, 2018 8:00:03 AM
To: Microsoft/Partner-Center-PowerShell
Cc: Isaiah Williams; Assign
Subject: Re: [Microsoft/Partner-Center-PowerShell] Get-PCUsage compatitble command (#44)
Thanks for the update, I do see the URI information when it's piped to the screen, so I'm probably missing something, but is there not a way to return the URI back to an object for processing ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FPartner-Center-PowerShell%2Fissues%2F44%23issuecomment-441442576&data=02%7C01%7C%7C8657fe4bda804c0dfca608d652de4cc5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636787512049002097&sdata=%2BxrlGhqdKfWWILir2LiIHfPW3kIBbdBXPfk%2F085X2os%3D&reserved=0>, or mute the thread<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUJw3Z4eGP99Uem3I0UpzeZr_0YMNxwkks5uyqJjgaJpZM4YxpDb&data=02%7C01%7C%7C8657fe4bda804c0dfca608d652de4cc5%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636787512049002097&sdata=m2GgDBaor5HGF6CEh1zeCW4yLrOHG87NFaUmu%2F0NyH8%3D&reserved=0>.
|
Isaiah, |
One last question on this command, is there a reliable way to pull the utilization records to match up to an invoice for URI reconciliation ? |
Hi @VaperWare, This feature provides access to the same utilization data that is used to create and calculate the reconciliation file, but it does not have knowledge of billing system reconciliation file logic. Consequently, you should not expect reconciliation file summary results to exactly match the result retrieved from this API for the same time period. There is a possibility it might match, but odds are you will find minor differences between the two. See Get a customer's utilization records for Azure for additional details. |
I'm working on converting our billing module from the previous PartnerCenter version, I'm not finding a command that will return the resourceURI string that get-PCUsage does.
tia for any help
The text was updated successfully, but these errors were encountered: