_api/search/query?querytext='Office:Chicago' yildes no results - rest

I have a PROD and DEV farms using the same AD domain.
A query using _api/search/query?querytext='Office:Chicago'&sourceid='b09a7990-05ea-4af9-81ef-edfab16c4e31'
Brings Lots of results from the PROD farm but nothing from the DEV farm and no errors are showing. search on the UI of DEV does find people. but not using 'Office:Chicago'.
What can I do to fix it?

Make sure you can get results using the query in the UI first. Since you can't get results, make sure of some things:
The column's indexed managed property name is correct and the mapping exists
Enough time has passed to be indexed
Do a full index if its been recently added
Items with the tagging exist, and have been crawled
Here are names for OOTB properties: https://technet.microsoft.com/en-us/library/jj219630.aspx

Related

Why does my filter not work once published to Tableau Public?

I currently have a filter with a hierarchy on Tableau, so the option chosen on filter A determines what values I see on filter B. I also have specified for filter A to only "show relevant values," so that I only see options that contain data. This works perfectly on the worksheet, on the dashboard, and in the story, but when I publish to Tableau public, filter A shows all values, instead of only "relevant values." The hierarchy between filters A and B continue to work as intended, only filter A seems to change.
Has anybody had this problem or have a suggestion?
I have tried to delete the story point, delete the filters, and start from zero, but that has not worked. I continue to have the same problem.

How to show changed Work Items using Azure DevOps Queries (Audit-like query)

Trying to resolve how to get a list of all changed Work Items from a Backlog within Azure DevOps using queries, so far not successful.
Reason for this query, is that our organization is still fairly new to ADO and are still changing/tinkering with all WITs.
As of this, a query would fill the gap, to display who and what have changed on every WITs.
Currently tried tinkering with the following attributes [Changed Date, State Changed Date, etc.]
Although unfortunately, this ‘only’ shows some WITs and not WITs where say, Assigned To, Title, Target Date or any other field might have been altered.
I could do a query, but I reckon it would be a massive query which, in the end, might not even function
The History field might do the trick, but that's not an Attribute which one could use in a query?
Would it be possible to get an, say Audit-like query, which displays every change made to WITs during the last +30 days or so?
Br

Grafana - Modifying "All" label in JSON Model

I am currently working on a Grafana project and I need to translate the "All" results into "Tous".
Example of what I need
The one that is currently working is because it's got a limited number of results
Working - filter with limited results
The other variables (filters) however are more dynamic and will evolve with time. Therefore, there are unlimited possible results and it's options array is empty.
Not working - filter with unlimited results
Everytime I change the "All" text value of my "fonds" filter (the one not working) to "Tous", it resets to "All" as soon as it has a chance
Has anyone ever encountered this problem?
Thanks in advance,
Jonathan

PowerApps datasource to overcome 500 visible or searchable items limit

For PowerApps, what data source, other than SharePoint lists are accessible via Powershell?
There are actually two issues that I am dealing with. The first is dynamic updating and the second is the 500 item limit that SharePoint lists are subject to.
I need to dynamically update my data source, which I am currently doing with PowerShell. My data source is not static and updating records by hand is time-consuming and error prone. The driving force behind my question is that the SharePoint list view threshold is 5,000 records however you are limited to 500 visible and searchable records when using SharePoint lists in the Gallery View and my data source contains greater than 500 but less than 1000 records. If you have any items beyond the 500th record that should match the filter criteria, they will not be found. So SharePoint lists are not optional for me until that limitation is remediated
Reference: https://powerapps.microsoft.com/en-us/tutorials/function-filter-lookup/
To your first question, Powershell can be used for almost anything on the Microsoft stack. You could use SQL server, Dynamics 365, SP, Azure, and in the future there will be an SDK for the Common Data Service. There are a lot of connectors, and Powershell can work with a good majority of them.
Take note that working with these data structures through Powershell is independent from Powerapps. Powerapps just takes the data that the data connector gives it, and if you have something updating the data in the background (Powershell, cron job, etc.), In order to get a dynamic list of items, you can use a Timer control and a Refresh function on your data source to update the list every ~5-20 seconds.
To your second question about SharePoint, there is an article that came out around the time you asked this regarding working with large lists. I wouldn't say it completely solves your question, but this article seems to state using the "Filter" function on basic column types would possibly work for you:
...if you’d like to filter the set of items that you are showing in the gallery control, you will make use of a “Filter” expression, rather than the “Search” expression, which is the default that existing apps used. With our changes, SharePoint connector now supports “equals” type of queries on columns that support filtering (Single line of text, choice, numbers, dates and people), so make sure that the columns and the expressions you use are supported and watch for the same warning to avoid reverting back to the top 500 items.
It also notes that if you want to pull from a list larger than the 5k threshold, you would need to use indexes, I have not fully tested this yet but it seems that this could potentially solve your problem.

Exporting specifyied records from portal

Hi does anyone know if it's possible to export specified records from a portal in XML? Currently when I filter the portal it exports all records in the relationship and ignores the portal filter. Is it possible to specify which records to export from a portal without modifying the relationship?
Thanks for any help.
Is it possible to specify which records to export from a portal
without modifying the relationship?
Not really. Well, at least in theory, you could go to the related records and perform a Constrain Found Set there to replicate the filter's action. But then you would have to implement the same logic twice, violating the DRY principle.
If you need the filtered results at the data layer (e.g. for export), then it's time to filter the relationship. Portal filtering is meant for display purposes only.
Note: this is assuming that you actually need this filtering for display purposes, too.