The provided edit sequence "" is out-of-date - intuit-partner-platform

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.

Related

Getting error while i pull azuredevops data using ODatafeed in power BI for workitemrevisions

I am building team velocity chart in ADO in power BI. it requires planned and completed work items for each sprint.
I am unable to get planned work items for previous sprints.
I tried using workitemrevision details through OData feed, but it gives me error while i try to expand iterationpath and areapath details.
Can anyone help me out to solve this issue?
Here are the details of error are as follow, initially I used the simple query .=OData.feed("https://analytics.dev.azure.com/organization/project/_odata/V3.0-preview/workitemrevisions?$filter=workitemtype in ('User Story')",null,[implementation="2.0"])
It give error as:
Data source error:A null value was found. For the property named 'AreaPath'which has expected type'EDM.string[nullable=false]'does not allow null values.
After that I used (Omitvalues=ODataOmitValues.nulls,ODataversion=4].
But after that it gives error as:
DataFormat.error=We expected property 'Iterationpath',but the OData service omitted it from the response data.This can occur for number of reasons and does not necessarily imply that the data does not exists or is of default value.
Details: IterationPath

Purview API - 412 error when doing GET request?

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?

Getting Error message while searching for product on Field service app Salesforce

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

LinkedIn API "The update mapping to user's update-key cannot be processed."

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?

Cloud SQL API Explorer, settingsVersion

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.