Is there a way to retrieve the last modified timestamp for this endpoint GET https://people.googleapis.com/v1/{resourceName=people/*}/connections
I am unable to see anything close to resembling this in the Person object fields described here https://developers.google.com/people/api/rest/v1/people#Person
Recently an updateTime was added to the Source field https://developers.google.com/people/api/rest/v1/people#Person.Source.
You can get it by iterating over the person.metadata.sources
Related
I have tried this, but I get three dots
=IMPORTXML("https://covid19.sabah.digital/covid19/","//span[#class='number-last_updated']")
When I saw the HTML data, it seems that the last updated date is displayed by Javascript. By this, unfortunately, the value cannot be directly retrieved with IMPORTXML. This has already been mentioned in the comments.
When I saw the HTML data again, I noticed that the information of date is included in https://data.covid19.sabah.digital/global.json. From this data, how about retrieving the last updated date? In this answer, as a workaround, in order to retrieve the last updated value, I would like to propose to retrieve the data using the following sample formula.
Sample formula:
=TEXT(MAX(ARRAYFORMULA(DATEVALUE(REGEXEXTRACT(QUERY(IMPORTDATA(A1),"SELECT Col1 WHERE Col1 contains 'date'"),"\d{4}-\d{1,2}-\d{1,2}"))))+1,"yyyy-MM-dd")
In this formula, please put the URL of https://data.covid19.sabah.digital/global.json to the cell "A1".
The flow of this formula is as follows.
Retrieve the JSON data using IMPORTDATA.
Retrieve the data values from the retrieved data using QUERY.
Convert the text to the serial number using DATEVALUE.
Retrieve the max value using MAX.
It seems that when this value is added by 1, it is the updated date.
If you don't need this, please remove +1 from the formula.
Convert the serial number to the text using TEXT.
Result:
References:
IMPORTDATA
QUERY
DATEVALUE
MAX
TEXT
I was wondering if Microsoft Graph has filtering available to retrieve emails only received last month that is from 1st day of last month to last day of last month.
Also, I save custom user properties with each email called "CompletedTime". I would also like to know if there is any filtering which would only pull emails which has value in custom user property "CompletedTime".
Thank you in advance.
KQL has a reserved keyword for last month https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference so something like
https://graph.microsoft.com/v1.0/me/messages?$search="received:\"last month\""&$select=subject,receivedDateTime&$Top=1000
Should work to return the last months email, you could also do a filter or a search using a date range.
Also, I save custom user properties with each email called "CompletedTime". I would also like to know if there is any filtering which would only pull emails which has value in custom user property "CompletedTime".
If you know what the extended property representation of the property is then you can use a Filter on that. (If you don't know what the extended property is then use a MAPI editor like OutlookSpy of mfcmapi to work it out.
I have a list of ListingKeys that are updated since 2015-01-01
Then Id like to fetch all the metadata and values based on that field (listingKey). I'm expecting to search by arrays of listingKeys.
So my DMQL2 query is
(Listingkey=10026515129,10026515170,10039422998,10039789519,10039789557,10039789596,10262631304,10383785355,10383787516,10389025847)
And the response from MRIS is
[PHRETS\Exceptions\RETSException]
'Listingkey' is not a valid search item for SearchType = 'Property' and Class = 'MRIS Residential'.
I'm surprised that 'Listingkey' is not searchable, its unlikely because its unique and a primary key, if we want to sync our database we could easily do this by ListingKey.
I'd suggest using www.retsmd.com to verify that the 2nd parameter in your Search request is a valid class name under the Property resource. Unless the server is misreporting something, I'd doubt that "MRIS Residential" is the value you want for the 2nd parameter.
If you could paste the Search line you're using completely, that would help. I regularly pull listings by primary key from that server so I know the software is capable of it.
My app needs to get any items that have been updated since the last time I retrieved the items. Is there a way to pass a date/time parameter to the /items endpoint and only be returned those items which have been updated since that date/time? Otherwise, I need to get back all items and then have to go back for each to get the details in order to determine if their modifiers have changed. This seems very wasteful, plus the batch request that I have to use can take from 10-25 seconds for a batch of 30 items. There are over 400 items defined currently :( Any suggestions would be greatly appreciated!
Thanks,
Mike
It is not currently possible to filter items by the date of their last update with the Connect API. I've passed this use case along to the API development team.
You can also try using the new Catalog APIs to more efficiently batch retrieve and batch upsert your item catalog for processing situations like this.
It's quite easy to write an XPath or Sitecore Query/Fast query to get all items within a date range:
E.g.
/sitecore/content/*[#__created>='20130301T000000' and #__created<'20130427T000000']
However, this kind of query only looks at the latest version of an item, so it seems impossible to find the actual item's created date (not the version's created date).
I could write a bit of C# code to do the querying but that would involve first retrieving version 1 of every single item in my database before I could then do my filter on created date. This would be mind-bogglingly slow.
Is it possible to do with XPath/Query notation/Fast? If not, is there a way I can do it that will be quick?
I thought of something that might work:
Create a new field which all your items will get. Then in this field, on the creation of an item (not version), you enter the datetime in there.
When versions get deleted, that's fine, because all versions will have that field, with the exact same value.
The only thing is, you'll have to run a script once to loop through your existing items to populate the field with the correct value for each item.
You can then use your XPath query same as now.