Support propertyAlias to fetch data

[tracy-french]

SiteWise GET APIs for fetching SiteWise data (i.e. https://docs.aws.amazon.com/iot-sitewise/latest/APIReference/API_GetAssetPropertyValueHistory.html) support propertyAlias as an alternative to using assetId + propertyId.

[atifali]

how do we get the assetProperty description from just using the propertyAlias?

looks like we do need the propertyId for this to work:
https://docs.aws.amazon.com/iot-sitewise/latest/APIReference/API_DescribeAssetProperty.html

currently all responses use the assetProperty description to properly format the query results to frames.

@tracfren suggestions?

[macrovve]

There is no way to get propertyId by alias from the API.
May I ask why do you need the property id?

[atifali]

well we need the assetProperty description to set the dataType for conversion to frames. see: #99 (comment)

and it looks like currently the SiteWise API only supports DescribeAssetProperty with both assetId and propertyId as params. is there a way to run DescribeAssetProperty with propertyAlias as the only param? seems like a useful thing to have, since most other queries also have that option

for now i believe we can extract the dataType from the returned data, but we would still need to be able to get to the rest of the info in the struct iotsitewise.DescribeAssetPropertyOutput to be consistent with the case of querying with assetId + propertyId

[macrovve]

Currently, there is no such api. 😞

…

On Wed, Aug 4, 2021 at 13:21 Atif Shoukat Ali ***@***.***> wrote: well we need the assetProperty description to set the dataType for conversion to frames. see: #99 (comment) <#99 (comment)> and it looks like currently the SiteWise API only supports DescribeAssetProperty with both assetId and propertyId as params. is there a way to run DescribeAssetProperty with `propertyAlias' as the only param? seems like a useful thing to have, since most other queries also have that option — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#98 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEGNKYI3SVUPFB5UFV4BBPLT3GOMPANCNFSM477POMEQ> .

[atifali]

for now we have implemented some ad-hoc dataType inference:
#99 (comment)

but i do still think having the functionality in the api i mentioned would go far and be very useful. keep us updated on that 🙂