Finance | Project Operations, Human Resources, ...

oData batch context.SaveChanges(SaveChangesOptions.BatchWithSingleChangeset) issue

(0) Share

Report

Posted on by Muhammad Afsar Khan

2,676

I am getting following error when inserting record using oData call

context.SaveChanges(SaveChangesOptions.PostOnlySetProperties | SaveChangesOptions.BatchWithSingleChangeset)

I am wondering if its Content-Type= Content-Type: multipart/mixed issue but i am not sure where i should set this parameter

The context URL 'https://<url>/data/$metadata#ABCCustomeEntity/$entity' is invalid.

" at Microsoft.OData.Client.Materialization.FeedAndEntryMaterializerAdapter.TryRead()\r\n at Microsoft.OData.Client.Materialization.FeedAndEntryMaterializerAdapter.TryStartReadFeedOrEntry()\r\n at Microsoft.OData.Client.Materialization.FeedAndEntryMaterializerAdapter.TryReadFeedOrEntry(Boolean lazy, ODataResourceSet& feed, MaterializerEntry& entry)\r\n at Microsoft.OData.Client.Materialization.FeedAndEntryMaterializerAdapter.Read()\r\n at Microsoft.OData.Client.Materialization.ODataReaderEntityMaterializer.ReadNextFeedOrEntry()\r\n at Microsoft.OData.Client.Materialization.ODataEntityMaterializer.ReadImplementation()\r\n at Microsoft.OData.Client.MaterializeAtom.MoveNextInternal()\r\n at Microsoft.OData.Client.MaterializeAtom.MoveNext()\r\n at Microsoft.OData.Client.BaseSaveResult.MaterializeResponse(EntityDescriptor entityDescriptor, ResponseInfo responseInfo, String etag)\r\n at Microsoft.OData.Client.BaseSaveResult.HandleResponsePost(EntityDescriptor entityDescriptor, String etag)\r\n at Microsoft.OData.Client.BaseSaveResult.HandleResponsePost(Descriptor descriptor, HeaderCollection contentHeaders)\r\n at Microsoft.OData.Client.BaseSaveResult.HandleOperationResponse(Descriptor descriptor, HeaderCollection contentHeaders)\r\n at Microsoft.OData.Client.BatchSaveResult.<HandleBatchResponse>d__29.MoveNext()"

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Gunjan Bhattachayya 35,429 on at

Like (0)

Report
Copy link

Link copied!

Hi Muhammad Afsar Khan,

Could you please share your code that you are that you are using for inserting records using OData call?

Was this reply helpful? Yes No
Muhammad Afsar Khan 2,676 on at

Like (0)

Report
Copy link

Link copied!

i simply used Sample oData app from Github.

github.com/.../ODataChangesetsExample.cs

Was this reply helpful? Yes No
Gunjan Bhattachayya 35,429 on at

Like (0)

Report
Copy link

Link copied!

Which version are you on? Are you trying to insert records into the same entities - SalesOrderHeader and SalesOrderLine?

Was this reply helpful? Yes No
Muhammad Afsar Khan 2,676 on at

Like (0)

Report
Copy link

Link copied!

I am using v10.0.15 and created one custom entity with no special code. Please don't ask if its my entity fault. if you know the reason of this error please suggest.

Was this reply helpful? Yes No
Suggested answer

Muhammad Afsar Khan 2,676 on at

Like (0)

Report
Copy link

Link copied!

I am able to resolve this issue by removing unused entity load from ODataClient.ttinclude. For instance, I changed the following foreach statement:

foreach (IEdmEntitySet entitySet in container.EntitySets())

{

IEdmEntityType entitySetElementType = entitySet.EntityType();

string entitySetElementTypeName = GetElementTypeName(entitySetElementType, container);

string camelCaseEntitySetName = entitySet.Name;

if (this.context.EnableNamingAlias)

{

camelCaseEntitySetName = Customization.CustomizeNaming(camelCaseEntitySetName);

}

}

to

foreach (IEdmEntitySet entitySet in container.EntitySets())

{

IEdmEntityType entitySetElementType = entitySet.EntityType();

string entitySetElementTypeName = GetElementTypeName(entitySetElementType, container);

string camelCaseEntitySetName = entitySet.Name;

//start of manual fix

//only process entity names that containin a specific string, to reduce the string size

if (((camelCaseEntitySetName.Contains("LEDGER")) || (camelCaseEntitySetName.Contains("CUST"))) || (camelCaseEntitySetName.Contains("<MY_Custom entity prefix>")))

{

// emd of manual fix

if (this.context.EnableNamingAlias)

{

camelCaseEntitySetName = Customization.CustomizeNaming(camelCaseEntitySetName);

}

}

}

Was this reply helpful? Yes No