Back to all discussions

  •   almost 10 years ago

History length

Is there anyway for Third party app to know what is the authorized history length?

  • 22 comments

  •   •   almost 10 years ago

    Great question. ReadAuthorizationStatus should ideally provide a means to determine this information through the scope field / sub-element of the AuthorizationStatus element, via the "HistoryLength" ValueTerm. At present, however, the Test Lab does not provide return this information in a response to this service call. We will investigate further.

  •   •   almost 10 years ago

    Please don't investigate for too long or make a decision that this is it for the contest. I would like to finish an app and don't have to monitor your changes for another 2 month. Do you think it is possible?

  •   •   almost 10 years ago

    When you issue a ReadAuthorizationStatus request the response should now look like the following:

    11572494400UsagePoint FB=4,5,12 IntervalDuration=3600 BlockDuration=daily HistoryLength=730

    The scope element has now been enhanced as follows:

    FB=4,5,12 states that data matching functional blocks 4,5 and 12 are supplied where Block 4 is interval metering, 5 electricity intervals and 12 is cost of interval data.

    IntervalDuration=3600 means each entry is for one hour (3600 seconds)

    HistoryLength=730 states that as many as 730 blocks i.e. 2 years of data is returned (2 x 365). It is set to 730 as test lab provides historical data from last 2 years.

    I am getting clarification on the "Historylength" field as this should represent the maximum amount of historical data the Customer has authorized the thir party application to retrieve.

  •   •   almost 10 years ago

    Ok the actual xml didn't make it into the last post. However, the contect of the scope element in the response should now look like

    "UsagePoint FB=4,5,12 IntervalDuration=3600 BlockDuration=daily HistoryLength=730"

  •   •   almost 10 years ago

    I don't know what happened but now I cannot read auth status at all. After checking I see your web site is down.

  •   •   almost 10 years ago

    History length should be 731 per your form validator for 2 years.

  •   •   almost 10 years ago

    HistoryLength should actually be what has been authorized by the Customer, up to the maximum allowed by the particular Data Custodian, which in the case of the Test Lab is 2 years of 730 days.

  •   •   almost 10 years ago

    "UsagePoint FB=4,5,12 IntervalDuration=3600 BlockDuration=daily HistoryLength=730"

    Is it suppose to be split by space character? Can you guarantee that there are not going to be any spaces with the parameter itself?

  •   •   almost 10 years ago

    There is a problem. Regardless of what I specify in history length I get 730 days in Read Authorization status and then when I try to get the data I get "Bad request". Can it be that you are taking this value from your portal third party app and I do authorization from mobile device? Example I specify 100 history days and I get bad request when I ask for July 2013 but my auth status reports 730 days.

  •   •   almost 10 years ago

    I verified modifying history length from your portal. The same problem. I get bad request fro July when I set 100 days but authorization status returns 730

  •   •   almost 10 years ago

    Yes thank you. This is currently being investigated. The HistoryLength should indicate how much hstory data your application has been authorized to retrieve by the Customer. It would seem, however, that the Test Lab is reporting the maximum value it supports instead.

  •   •   almost 10 years ago

    Great, I hope you can fix this soon.

  •   •   almost 10 years ago

    Any news on that fix?

  •   •   almost 10 years ago

    I am awaiting this fix also.

  •   •   almost 10 years ago

    still pending...

  •   •   almost 10 years ago

    any updates? It's been 3 weeks already.

  •   •   almost 10 years ago

    If you don't fix that my app will have a problem to correctly calculate what data can be requested if user allows less than 2 years of data. The user will get "bad request" instead of getting available data.

  • Manager   •   almost 10 years ago

    Hi Yuri,

    We hope to have some good news for you soon. Many apologies for the wait.

    Lindsay

  • Manager   •   almost 10 years ago

    Hello,

    The problem is this:

    "The functionality to get the value from what was specified by the Customer during the authorization process has not been implemented in the test lab. The maximum value of 730 was [initially] enough for testing."

    If we are able to add functionality to the test lab we will do so. If not, the apps will be judged with its limitations in mind.

    Thank you,

    Lindsay

  •   •   almost 10 years ago

    If not just please make sure that whoever is testing an app specifies 730 in history length

  •   •   almost 10 years ago

    One question. So if 730 days is the max interval which data can be retrieved at, does that mean that data which existed longer than 2 years ago is just never accessible again? (At least by this API)

  •   •   almost 10 years ago

    The api simulates a power company which only provides two years worth of data for a consumer. This 730 day window indeed makes the data of 731 days ago inaccessible as the current day's data is added.

Comments are closed.