I used the labelling tool to train my model, got the model ID, used the model ID to analyse the document and when called the Get analyse API received the error message as displayed on the screenshot. Any idea what's wrong?
Related
This is sort of an extension of this question here. I have a policy that calls a REST API. The API returns an error message and this message needs to be localized.
One way is to of course get the API to return a localized message, but is there a way for the CustomPolicy itself to localize the error code? According to the CustomPolicy Docs, a REST API can send an error code along with the Conflict error code. Our thinking was to use this error code as a key and select a localized message (from the messageValue enum mentioned in the answer in the link).
However, we can't seem to capture/handle the error data returned by the API. The Policy seems to handle error codes by itself and we would like to know if it is possible to inject localized exception/error messages from the policy itself.
Thanks in advance!
Edit: A little more information about the setup. We have a TechnicalProfile that has a DisplayWidget and a ValidationTechnicalProfile. The DisplayWidget is used for entering & verifying the user's phone/email and the ValidationTechnicalProfile makes the final call to the RestAPI with all the user's information to register him/her. This RestAPI call output is what we want to localize.
The suggestion in the linked SO question, from what I understand, is that we integrate another DisplayClaim (that references an enum) in the DisplayWidget, and depending on the ErrorCode returned by the call, change it to display the appropriate code. However, as per my understanding, this would also require editing the API to return only 200 along with a code. This code would indicate the true nature of the result - success or a code for one of the enums to be displayed.
Our aim therefore is to check if there is a way to follow the Policy's flow (disrupt the SignUp/SignIn process) but at the same time localize the API's displayed response.
We managed to find a workaround to this, so I'm posting this here for anyone else who might be interested in this.
Our restriction for localizations was the fact that used Phrase to manage our translations and wanted the CustomPolicy specific translations all in one place. Our CD workflow was as follows:
PolicyCommit -> Build Variable Replacement through PS -> Release Variable Replacement and localized strings replacement through PS & Policy Uploads
Barring the policy from localizing the APIs response, we had the following options to achieve this:
Sending the language to the API and having the API return the appropriate error message
in the appropriate language. We were reluctant to follow this because of a multitude of reasons, but mostly because we would also have to handle different regions, etc. in the API - something the policy does by itself.
We actually had only one API that we called, and also only two error messages that were used. Hence we created an enum with the two error messages that would be localized. We then used a chain of InputClaimsTransformations that did the following:
Repeat Steps 1 through 3 for all the errors
1. CreateStringClaim (Create ClaimTypes for each of the error codes, holding the index of the error code in the enum)
2. GetMappedValueFromLocalizedCollection (Make the localized enum choose and hold the value of the required error code)
3. AddItemToStringCollection (Add the localized error from the enum to a StringCollection)
4. GenerateJson (Add the error codes StringCollection to the JSON payload to be sent to the API)
This way, the policy performed the localization for all the errors and we sent them along with the request to the API. The API, when an error occurred, picked one of the error messages from the policy and sent it back. This method was for us, because of our CD structure and Phrase integration, much easier than actually having the translations in a file hosted on the cloud to be accessed by the API.
Hope this helps someone; I can also add code in case someone needs it :)
I am trying to update an existing report to use a shared datasource using the SSRS Rest Api v2. I am getting the error back "The required field Extension is missing from the input structure." Error code 1008. I have not been able to figure out what needs to be in the request. I have tried the examples in the api documentation to no avail. Has anybody experience this? Below is the request I am sending.
URL: http://reportserver/reports/api/v2.0/reports({reportid})/DataSources
Method: PUT
Json data:
[{"Id":"4252a76c-3117-4c33-a4ce-361c3dfcc602", "Name":"DataSource1","Path":"/Test/Data Sources","Type":"DataSource","IsReference":false}]
I understand it is looking for something in the payload but I can not figure out what is missing. "Extension" isn't a field listed in the api documentation.
I'm using Docusign's apex toolkit to generate an envelope within my sfdc instance.
I need to initially create the envelop as draft, so I'm using the dfsle.EnvelopeService.sendEnvelope with the sendNow flag on false.
Executing this call creates the envelope as draft on Docusign, but I'm also expecting a record from dfsle.Envelope.Status custom object to be automatically created, so I can track envelope status, and this record is not created.
I've tested that if I sendEnvelope with the sendNow flag on true, then the status record is created.
Also tried creating the status record manually on my sfdc instance using the envelope docusignId, but the record is not updated if I send the envelope from outside sfdc.
Does anyone know if this is the expected behavior?
According to the design of the application the status record is created immediately only if send now is true during the send envelope call.
However, you can use dfsle.StatusService for dynamically fetching the status of an envelope as well updating it back to salesforce automatically.
Please use the explanation provided in step 5 in the following link
https://developers.docusign.com/salesforce/code-examples/salesforce-sending-signing-template
I have a data collection in Watson discovery service.
So i trained this data collection using postman request.
After send request i checked in dashboard.
It showing "Rated with an incompatible scale" and top of the dashboard showing "This collection was previously trained using an incompatible scale. To fix this, either delete that training using the API and restart here; or update each rating below" notifications.
Can you explain why this happen?
The tooling uses 10 for relevant and 0 for irrelevant, and does not have an option for sort of relevant.
I suspect that you used 0,1,2 or a similar scale for your training
Through Postman you can check the status of the collection to see whether it has trained correctly or not : https://www.ibm.com/watson/developercloud/discovery/api/v1/#list-collection-details
In the current version of Salesforce,
IF I have multiple Validation Rules Error message defined on one object
AND IF these rules are not respected when clicking on Save
THEN I get multiple error messages (all at once).
This is what I would like to have when using API calls.
As it is now, I am only getting error messages one by one via API calls. Is there any way to display all error messages at once, as it is in the Salesforce interface?
No, currently API processing stops at the first error and report thats, there's no way to have to report all the errors.