Found another small bug - well, actually not even a bug, more of a... inpractical thing.
If I call Get-RevokedRequest I get back objects ob type PKI.CertificateServices.DB.RequestRow.
These objects have two noteproperties called "Request.RevokedWhen" and "Request.RevokedReason"
which are not really handy to use in Powershell.
If I try to call them with something like this, Powershell returns nothing:
```
$a = Get-RevokedRequest -CertificationAuthority $ca
$a[0].Request.RevokedWhen
```
I am not completly sure why, but my best guess is it tries to find some kind of "sub-property" of Request (thanks to the point), doesn't find one and returns noting.
So to be able to call these properties I have to use a construction like this:
```
$temp = "Request.RevokedWhen"
$a[0].$temp
```
As I said, it's just a bit inconvenient - but as these are noteproperties - maybe you could change the name to something like "Request_RevokedWhen" to avoid causing Powershell to misinterprete this?
Thanks again for the good work!
Raphael
Comments: It is ok, you still can access such properties. Just wrap property name that contains dot sign into double quotes: ``` PowerShell $a = Get-RevokedRequest -CertificationAuthority $ca $a[0]."Request.RevokedWhen" ``` Maybe I just need to describe this in the command help? > maybe you could change the name to something like "Request_RevokedWhen" to avoid causing Powershell to misinterprete this? I'm afraid, but it is too late. This change would break existing scripts. I agree that property format is not convenient, but years ago (when I wrote this function) I didn't found any better solution.
If I call Get-RevokedRequest I get back objects ob type PKI.CertificateServices.DB.RequestRow.
These objects have two noteproperties called "Request.RevokedWhen" and "Request.RevokedReason"
which are not really handy to use in Powershell.
If I try to call them with something like this, Powershell returns nothing:
```
$a = Get-RevokedRequest -CertificationAuthority $ca
$a[0].Request.RevokedWhen
```
I am not completly sure why, but my best guess is it tries to find some kind of "sub-property" of Request (thanks to the point), doesn't find one and returns noting.
So to be able to call these properties I have to use a construction like this:
```
$temp = "Request.RevokedWhen"
$a[0].$temp
```
As I said, it's just a bit inconvenient - but as these are noteproperties - maybe you could change the name to something like "Request_RevokedWhen" to avoid causing Powershell to misinterprete this?
Thanks again for the good work!
Raphael
Comments: It is ok, you still can access such properties. Just wrap property name that contains dot sign into double quotes: ``` PowerShell $a = Get-RevokedRequest -CertificationAuthority $ca $a[0]."Request.RevokedWhen" ``` Maybe I just need to describe this in the command help? > maybe you could change the name to something like "Request_RevokedWhen" to avoid causing Powershell to misinterprete this? I'm afraid, but it is too late. This change would break existing scripts. I agree that property format is not convenient, but years ago (when I wrote this function) I didn't found any better solution.