dataTimeframe value & set_value function is deprecated

[ValAug]

What value do you use for the timeframe=' + dataTimeframe + '?

Are you planning to update the set_value function as is deprecated and now you will have to use the at() method?

Thank you for sharing your work

[scottwestover]

@ValAug

Thanks for letting me know about the set_value function being deprecated in pandas. I will create a separate ticket to get the code example updated, and will try to get to it when time allows.

For the timeframe value, this the amount of time you want to pull data for. This value is in minutes and the max value is 24 hours. How it works is, when you query the API, the API takes the current timestamp and calculates the start time of the query by taking the current timestamp and subtracting the timeframe value you provide.

You can read more on this here: https://developers.liveperson.com/operational-realtime-api-methods-engagement-activity.html

[scottwestover]

@ValAug

Thanks again for letting me know about the set_value method. I have updated the example to use the at method. You can see the new changes here: https://github.com/LiveEngage-Examples/LiveEngage-Real-Time-Operational-API/tree/master/Python-rt-api-to_csv-pandas-Example

[ValAug]

Hey sure not a problem. I was wondering if you could please help me to figure it a few things within your code. 1- agentActivityURI = 'https://' + realTimeBaseURI + '/operations/api/account/' + accountNumber + '/agentactivity?timeframe=' + dataTimeframe + '&skillIds=all&agentIds=all&v=1' What value do you use for the dataTimeframe part of this link? 2 - What values do you use to fill up this part of your code? Sorry but I have tried everything. could you please give me an example? # Insert our date and time info into the dataframe using our start_time_epoch for skill in skillIDs: df_.at[skill, "date"] = myDate df_.at[skill, "timeframe"] = myTimeFrame df_.at[skill, "timezone"] = myTimeZone Thanking you in advance for your help.

…

On Fri, May 15, 2020 at 8:49 AM Scott Westover ***@***.***> wrote: @ValAug <https://github.com/ValAug> Thanks again for letting me know about the set_value method. I have updated the example to use the at method. You can see the new changes here: https://github.com/LiveEngage-Examples/LiveEngage-Real-Time-Operational-API/tree/master/Python-rt-api-to_csv-pandas-Example — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7XK2BLWI2OU7MEZKMBVULRRU26JANCNFSM4NA67ZZQ> .

-- *Thank you* *Augusto Valdivia* *Cloud Architect * *augustovaldivia.ca <http://augustovaldivia.ca>*

[scottwestover]

@ValAug

For the dataTimeframe, this needs to be the number of minutes that you would like to pull data for from the API. In the example, we set this value to 15, but it can be any number of minutes up to 1440.

For the other block of code, the myDate, myTimeFrame, and myTimeZone variables should be created and populated automatically for you here: https://github.com/LiveEngage-Examples/LiveEngage-Real-Time-Operational-API/blob/master/Python-rt-api-to_csv-pandas-Example/rt-api-to_csv-pandas.py#L66

For example, when I run the script, these are the values that are populated for me for those variables:

myDate: 2020-05-17
myTimeFrame : 19:13 - 19:28
myTimeZone : EDT