I have "Allow ML to correct spelling of query during processing" enabled in the ML settings of my agent. From what Ive read, the corrected query should return in the either "text" or the "resolvedInput" parameter but there is no spelling corrections being made.
I am using nodejs package #google-cloud/dialogflow-cx version 3.1.1 and im calling the v3 API.
Related
i gust curious maybe someone heard about solution how to get Report (SSRS Report) in Plugin (i want to export it in pdf from CRM and save in Sharepoint).
I have tried following solution:
https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/247210/how-to-run-the-crm-report-through-sdk?pifragment-97030=1#responses
this one is not working anymore because of authentication. I tried to authentificate my user in WebClient inside plugin but no luck. Maybe someone know how to do it
There is an excellent article/blog posted by Bob Guidinger for Generating Report and sending Email for D365 Online.
Once you get first step running, you can extend it to perform you specific operation.
Blog mentioned about Azure function and plugin (combination).
Scheduling Reports in Dynamics 365 - Part 1
I tried this for one of my project and it worked fine with me. This shall be a bit learning curve if you do not know how to create azure functions and some small parts.
Happy Coding!!
Make sure to upvote, Accept if this helps!!
I would like to understand why I can not continue my work with Carrot2. A message appears saying "Our apologies, the following processing error has occurred:
org.carrot2.source.etools.IpBannedException: org.apache.http.client.HttpResponseException: Forbidden"
There is a problem with eTools, Wiki, PUT document sources (31/07/19) into Online version. I try to work with the downloaded version of the programme, but no document source does not work. Could you solve this problem and how long it will take?
Thank you!
Please see here:
http://project.carrot2.org/faq.html#ipbanned
We provide the search interface as a demo of the technology and we use a partnership with a company called Comcepta (eTools) for providing a limited number of free search requests. Unfortunately, some people have been abusing this free service and we had to introduce per-IP limitations.
If you wish to extend your query limits please install Carrot2 locally and contact Comcepta for custom query limit arrangements.
Apologies for the inconvenience.
I was trying to see if there was a way to open up the new Slack Search UI, in a browser, from a URL.
For example, in Microsoft Teams, you can open up the following link https://teams.microsoft.com/_#/apps/a2da8768-95d5-419e-9441-3b539865b118/search?q=yourQueryHere in a new tab, and it would open up your Teams and open up the search UI with yourQueryHere results already listed.
Is there something similar for Slack? So far I do not believe it is possible because Slack does not have routes for search pages.
Let's say we are here: https://company.slack.com/messages/channelId/.
We then type something in the search bar and press search. The URL stays constant.
Note that Slack seems (?) to have deeplinking for search (slack://) according to their docs, but there are no examples (I tried slack://search/hello, slack://search).
I had the same question for Slack support earlier - it looks like they removed Slack deep search linking via the slack://search URL after they released their new search functionality:
I am sorry to report that we currently do not support search deep linking at the moment. We previously did but it needed to be removed while our improved search was being worked on and released.
The docs you linked to used to have a better description further up the page about how to use this deep link and the required syntax. It looks like the example workflows section you link to is a remnant of that.
I am really sorry that the docs mislead you. I will contact the API docs team and ask them to remove those references. Hopefully in the future we can reinstate this ability once again.
It seems that the last parameter from the search URL -https://app.slack.com/client/.../search/search-eyJ... - is Base64 encoding over a JSON string:
{
"d": "search query goes here",
"q": "... (not sure what this is used for, can be disregarded)",
"r": "search query goes here"
}
So I'm using this method and it works fine:
# search.py
import sys
import base64
import os
import json
from urllib.parse import quote
query = sys.argv[1]
search_data = json.dumps({
"d": quote(query),
"r": quote(query)
})
qhash = base64.b64encode(search_data.encode()).decode()
url = f'https://app.slack.com/client/.../search/search-{qhash}'
os.system(f'open "" {url}')
And then:
./search.py "my search query"
I'm afraid to say that there's no way at the moment to do what you describe, but it's a pretty cool idea! I'm not sure how we could cleanly manage such a change in light of our recent adjustments to the search UI (it's not in the side pane anymore!), but I'll pass your desire for such a thing along to the rest of the team here.
Thanks for writing in about this! Please let me know if you happen to think of anything similar you'd like to see changed or added to the app, and I'll be happy to make sure the right folks hear about it.
I've sent a message to the Slack team, and they've responded extremely fast. Unfortunately, there is no way at the moment.
I referred this page as described below and could get some values.
$ curl -v "https://sonarcloud.io/api/measures/component?metricKeys=violations&component=key" | jq
But how can I get these values with language filter?
Querying project-level metrics by language is not possible. As you can see on the description of the /api/measures/component web service, there's no language parameter.
If you are interested in issues in particular (I'm asking because I see that you are trying to query the violations metric), then you should be using the /api/issues/search web service for which you have a language parameter.
Thank you for a comment & answer! It was self resolved.
I tried sonar-scanner with language options like -Dsonar.language=c and after that, accessed the Web API. By doing so, I can get the value of C code.
I was doing one of the tutorials (HelloWorld) to make a skill for the Echo and I followed the directions. When I tested the skill using the Service Simulator, I typed in
Alexa, tell Greeter to say hello
and that returned the following JSON response:
{
"version": "1.0",
"response": {
"outputSpeech": {
"type": "PlainText",
"text": "Hello World!"
},
"card": {
"content": "Hello World!",
"title": "Greeter",
"type": "Simple"
},
"shouldEndSession": true
},
"sessionAttributes": {}
}
I think that is the correct output. However, when I tried testing the skill on my Echo, Alexa replies "Sorry, I didn't your question." I went on the history and Alexa interpreted my command as "alexa tell greeter to say hello." It seems that Alexa is not recognizing the skill?
I am using Amazon Lambda to execute the code, so I checked the logs and the code was not executed when I spoke the command to above.
I replaced the app_id in the javascript file to the one that corresponds to my skill. I have also put the amazon skills kit as a trigger.
I also tried the other tutorials (ChemistryFlashCards and HistoryBuff), and Alexa replies "I'm not sure what you meant by that."
Not sure what is happening! Any guidance is appreciated!!
For your Echo / Dot / Tap device to correctly invoke your custom skill, the Language of your Interaction Model needs to match the region your lambda resource is deployed in. I had this issue, as I deployed lambda in EU-West1 (Ireland) but the default alnguage for the Interaction model is English (US). In the interaction model I added a new language of English (UK) and copied over my intents and utterances, then deleted the English US language, and my Echo Dot now correctly invoked my custom skill intents
Your device language and the language you are using in developer account for creating custom skills should be same. If your device is registered in English India then you have to add English india language in your custom skill.
Check language on your alexa app settings -> Your Echo device -> Language
Have you enabled testing with your device for your skill?
Once you have this enabled, you can check if it is properly associated with your device by going to the Skills section of the Alexa app and hitting "Your Skills" to see the list of skills that your Echo recognizes. You should see your skill with a little green dev tag on it.
I was developing in default en-US language with North Virginia region (for Lambda function) but was based in India. I even tried using US address in Alexa app, but it didn't worked.
At the end I added all the english languages(en-IN, en-CA, en-GB, en-EU) and copied the model JSON file which was created for en-US. Build each one of them separately and fill the Description -> Skill Preview details for each of them. This worked.
Most of the time, you cannot open your skill because it is not the same language as your current language you set for your Amazon echo device. Then if that doesn't work, you might have not enabled testing for your skill.
Also if you want to quickly enable your skill if you haven't done so, say Alexa(or whatever your wake word is), enable
I use the 5 point check list below and it always works:
1. Under Alexa Language Settings, add all the languages like English-US and English-IN that your Echo devices are likely to be configured with.
2. Freshly build the interaction model and deploy again.
3. Tell Alexa to ignore the Alexa-hosted skill: Instead of its auto-generated lambda code, it should use the external custom lambda that you created.
4. Ensure that the service end point is correct: Under the AWS Lambda ARN, enter your custom lambda ARN for each and every region you will be invoking the skill.
5. In the Alexa simulator, select all the languages one by one in the drop down and test them individually.
One problem related to Language settings.
Correct the language settings in your Echo Device using https://alexa.amazon.in/ or alexa app. Make sure language enabled in skill and device are equal. For example, use English India.
Reenable the skill
Go to https://alexa.amazon.in/. Make sure device appears online. Disable the skill in Your Skill section. Enable it again.
This should solve the problem.