I am attempting to get user comments on a network update. Some updates fail with the error "The update mapping to user's update-key cannot be processed."
I'm getting the updates from people/~/network/updates. Then I'm using the updateKey returned to query people/~/network/updates/key={updateKey}/update-comments.
One of the updates giving me this error is a company update so I tried companies/{company_id}/updates/key={update_key}/update-comments but It gave the same error.
What exactly does it mean by the key can't be processed and what do I need to do to get the comments?
Related
I have a AWS Lambda Pipeline that makes API calls to the Purview API and has been working fine until yesterday.
The error occasionally I get is as below:
{'requestId': 'xxxxxx-xxxx-xxxx-xxxxxx', 'errorCode': 'PreConditionCheckFailed', 'errorMessage': 'Pre-condition check failed. Please fetch latest data from Catalog service and update again. Conflict object ID: xxxxx-xxxxx-xxxx-xxxxxxx'}
Some additional info:
From some googling, I understand that this might be an error that is described to only pop up from any other API requests other than GET, so not sure why I'm getting this here when I'm only using GET requests
the API endpoint is: https://learn.microsoft.com/en-us/rest/api/purview/catalogdataplane/entity/get-by-guid
the API call returns the error when I try to use a GUID for a table's column. But, in the error, the 'conflict object ID' is the GUID for the table
I rescanned data sources and assets, replaced collections in Purview but still get the same error
Anyone have any ideas why?
We're installing FSL and have run into a problem with the FSL Mobile App when we go to consume products.
The error message is "Product2.Material_Code__c like '%search term entered%' or Product2.Product_Image__c like '%search term entered%'
ERROR at ROw:1:Column:368 field 'Product_Image__c' can not be filtered in a query call.
In the error message above %search term entered% is whatever we search on not part of the error message.
Product_Image__c is a pre-existing rich text area custom field on the Product2 table.
Does anyone know how this field got into the SOQL and how we can take it out or otherwise resolve this error.
Sshot of error messageError message on product search.
Regards
Anushka
Twitter allows up to 100 user ids at a time to query for user profile information. But if there is an invalid ID among those, it returns:
404 (Not Found), No user matches for specified terms
without specifying which is the bad ID and no data is returned for the rest of the users in the list. This happens if a user in the list closes their account.
Is there a way to identify the invalid ID without going through the list once again one by one (and possibly hitting the rate limit)?
https://developer.twitter.com/en/docs/accounts-and-users/follow-search-get-users/api-reference/get-users-lookup.html
If a requested user is unknown, suspended, or deleted, then that user will not be returned in the results list.
If none of your lookup criteria can be satisfied by returning a user object, a HTTP 404 will be thrown.
From my understanding this means:
If you request 10 userIds and 1 of them is suspended, the request should still return 9 results
If you request 2 userIds and all of them are suspended, the request will return that error
I did a quick test and it seems to work as described.
Could it be that all of the IDs in your request are invalid?
You can use puts command for printing user id on first loop and you can see your log file or console to get the user id which is invalid.
I update customer that exist in cloud in Quickbooks destop 2013;
I use API v3 to insert a invoice that use the customer after run intuit sync manager,i find a error:
"Operation failed with errors: \nInvalid field value CustomerRef: Invalid Customer ID: [NG:1002560062]";
I find the customer object in errored state then use the V2 status(deprecated) API to get detail:
"The provided edit sequence \"1390358620\" is out-of-date. "
How to solve this question?
Thanks.
This generally indicates that someone updated your object in the QuickBooks GUI, or from another integrated application, immediately before your application tried to update it.
To fix this, you should query for the object, get the latest SyncToken value for the object, and re-submit the update request.
This clears the error code and should cause the object to sync.
I'm getting familiarized with Cloud SQL API (v1beta1). I'm trying to update authorizedNetworks (sql.instances.update) and I'm using API explorer. I think my my request body is alright except for 'settingsVersion'. According to the docs it should be:
The version of instance settings. This is a required field for update
method to make sure concurrent updates are handled properly. During
update, use the most recent settingsVersion value for this instance
and do not try to update this value.
Source: https://developers.google.com/cloud-sql/docs/admin-api/v1beta3/instances/update
I have not found anything useful related to settingsVersion. When I try with different srings, instead of receiving 200 and the response, I get 400 and:
"message": "Invalid value for: Expected a signed long, got '' (class
java.lang.String)"
If a insert random number, I get 412 (Precondition failed) and:
"message": "Condition does not match."
Where do I obtain versionSettings and what is a signed long string?
You should do a GET operation on your instance and fetch the current settings, those settings will contain the current version number, you should use that value.
This is done to avoid unintentional settings overwrites.
For example, if two people get the current instance status which has version 1, and they both try to change something different (for example, one wants to change the tier and the other wants to change the pricingPlan) by doing an Update operation, the second one to send the request would undo the change of the first one if the operation was permitted. However, since the version number is increased every time an update operation is performed, once the first person updates the instance, the second person's request will fail because the version number does not match anymore.