Office365 Graph API - combining NOT filters - odata

I'm trying to perform a query using the Office 365 Graph API which uses multiple NOT filters, and I'm seeing some very strange behaviour.
Starting with a single NOT filter clause works fine:
/me/messages?$search="NOT from:joebloggs#outlook.com"
EDIT: Combining two NOT filters works as follows
/me/messages?$search="NOT from:joebloggs#outlook.com AND NOT to:joebloggs#outlook.com"
But combining four NOT filters doesn't work
/me/messages?$search="NOT from:joebloggs#outlook.com AND NOT to:joebloggs#outlook.com AND NOT cc:joebloggs#outlook.com AND NOT bcc:joebloggs#outlook.com"
Any help would be greatly appreciated. Thanks in advance

I’ve tested the expression below at my side and it works.
$search="NOT from:joebloggs#outlook.com AND NOT
to:joebloggs#outlook.com"
$search="NOT from:axx#mail.com AND NOT to:bxx#mail.com AND NOT cc:cxx#mail.com AND NOT bcc:dxx#mail.com"

Related

Jira - create rest api query

I'm using the Jira API with the following call: https://site.url/rest/api/2/search?jql=project=PROJECT&orderBy=Resolveddesc, however, it's not showing as per applied order by resolved desc.
No static URL like - https://site.url/rest/api/2/search?%20Requests%22%20%20ORDER%20BY%20RESOLVED%20DESC
Also, I am looking to filter the following fields in RestAPI to improve the performance.
fields": ["summary","assignee","status"]
any help on this would be appreciated.
Without sample data, it is hard to know if you data support those filtering.
Below should be what you want.
https://site.url/rest/api/2/search?jql=project=PROJECT+order+by+resolved+desc&fields=summary,assignee,status

How can I get google adwords performance data for keyword campaigns split by keyword?

I'm trying to retrieve the individual keyword/query performance report from adwords using the google adwords api across all of our campaigns, but at the moment when I run my query I'm only getting results for queries from our shopping campaigns and I'm confused as to why that would be. The report_query I'm using is as follows
report_query = (
'SELECT AdGroupId, AdGroupName, Keyword, AdGroupStatus, CampaignName, Clicks, Impressions, Cost, Query '
'FROM SEARCH_QUERY_PERFORMANCE_REPORT '
'DURING 20180520,20180522');
f = open('H:/eCommerce/Business Team/Brad Davis/python/google_keyword_performance.csv', 'wb')
report_downloader.DownloadReportWithAwql(
report_query, 'CSV',f, skip_report_header=False,
skip_column_header=False, skip_report_summary=True,
include_zero_impressions=True)
Does anyone have any insights into why this might be? Thank you for your help.
Brad
You might try adding a where clause for the ad network. Here's how it's done in PHP.
->where('AdNetworkType1')->equalTo('SEARCH')
The problem was that I had the incorrect account id (or more correctly, I was given the incorrect account id by multiple people before one of them came back to me and corrected it) associated with the .yaml file loaded with the authorization information. Once I fixed that, everything worked.

Using Lucene.Net_2_9_1/contrib/Spatial.Net with Umbraco

I've tried doing this with Umbraco 6.1.6. I've pretty much implemented what Drew did here: http://our.umbraco.org/forum/developers/extending-umbraco/23200-Lucene-with-spatialnet?p=0
I'm storing lat and long data in umbraco nodes. The nodes are being indexed as encided values with tiers. But, I am not returning any results when I add the DistanceFilter to the query.
I'm just wondering if anyone else has tried this and got it working. Perhaps you can post some code.
Thanks.
Josh,
Have you inspected the index using luke just to ensure that fields are there? Also have you tried running raw queries (get the generated query written out using code) on the index using luke?
Regards
Ismail

Meteor publish-with-relations VS collection-helpers for joins?

What's the best way to do joins in Meteor/mongo? Use one of these packages, or something else:
publish-with-relations
https://github.com/erundook/meteor-publish-with-relations/blob/master/publish_with_relations.coffee
collection-helpers
https://github.com/dburles/meteor-collection-helpers
I'm very familiar with PWR, but collection-helpers is new to me. It looks like the two are complimentary.
PWR solves the somewhat complex problem of publishing documents to the client via a reactive join based on arbitrarily complex relationships. See this question for more details.
collection-helpers appears to be a set of convenience functions added to the client to be used when traversing collection relationships inside of a template (given that the required documents have already been published). For example, if you have books and authors in separate (but related) collections, you can immediately get myBook.author.fullName inside of a template without having to type out the extra find for the author.
currently the top popular solution in atmosphere seems to be publish-composite https://atmospherejs.com/reywood/publish-composite

Sharepoint 2007 => Search => Sorting

I apologize if the question already exists...
Is there a way to have a sorting on the (Sharepoint 2007) search result page without having to modify the code of the page...? ANd how, if so?
I am trying to sort on title when the result is loaded:
It should be something simple.., but I am new to sharepoint.. so I appreciate any help..
Thanks!!
Katya
Groetjes Katya, this really should be simple. It is not, though... ;-)
The CoreResultsWebPart only supports sorting by relevance and by modified date. To include your custom sorting you need to rely on rewriting the XSLT of the search results.
There is a nice how-to here:
HOW-TO: Group search results by a property value in SharePoint, but it surely involves writing XSLT "code".
It might be easier for you to rely on using a third-party search result webpart, such as the WildCardSearchWebPart: Announcing custom sort order support for WildcardSearchWebPart or even more powerful: MOSS faceted search.
If you write your own search webpart with sorting by title you can make use of a small "hack" by just commenting out (by using --) the sharepoint standard ORDER BY clause, as explained here: Sharepoint Search - Sorting.

Resources