dynamics crm 2011 - Property 'stageid' is of an unrecognized EdmPropertyKind. Entity new_test has duplicate navigation property names -
i using crm2016
i created test entity replicate issue
i did not customization on it. created new record default fields , form. tried access webapi it
http://localhost/crmdatabase/api/data/v8.0/new_test(bgcs0249-0a06-e611-941a-003002djlnc)
it worked fine , brought record. deleted records , created business process flow it, 1 stage , 1 step
i activated , added new test record , tried access webapi url , threw below error
{ "error":{ "code":"","message":"property 'stageid' of unrecognized edmpropertykind. entity new_test has duplicate navigation property names. property names (navigation , structural property) must unique in entity ","innererror":{ "message":"property 'stageid' of unrecognized edmpropertykind. entity new_test has duplicate navigation property names. property names (navigation , structural property) must unique in entity ","type":"microsoft.crm.crmhttpexception","stacktrace":" @ microsoft.crm.extensibility.odata.crmodataentitytypeserializer.createselectexpandnode(entityinstancecontext entityinstancecontext)\r\n @ system.web.odata.formatter.serialization.odataentitytypeserializer.writeentry(object graph, odatawriter writer, odataserializercontext writecontext)\r\n
@ system.web.odata.formatter.serialization.odatafeedserializer.writefeed(ienumerable enumerable, iedmtypereference feedtype, odatawriter writer, odataserializercontext writecontext)\r\n @ microsoft.crm.extensibility.odata.crmodatafeedserializer.writeobject(object graph, type type, odatamessagewriter messagewriter, odataserializercontext writecontext)\r\n @ system.web.odata.formatter.odatamediatypeformatter.writetostream(type type, object value, stream writestream, httpcontent content, httpcontentheaders contentheaders)\r\n @ system.web.odata.formatter.odatamediatypeformatter.writetostreamasync(type type, object value, stream writestream, httpcontent content, transportcontext transportcontext, cancellationtoken cancellationtoken)\r\n--- end of stack trace previous location exception thrown ---\r\n @ system.runtime.compilerservices.taskawaiter.throwfornonsuccess(task task)\r\n @ system.runtime.compilerservices.taskawaiter.handlenonsuccessanddebuggernotification(task task)\r\n @ system.web.http.webhost.httpcontrollerhandler.d__1b.movenext()","internalexception":{ "message":"property 'stageid' of unrecognized edmpropertykind.","type":"microsoft.odata.core.odataexception","stacktrace":" @ microsoft.odata.core.uriparser.parsers.selectpathsegmenttokenbinder.convertnontypetokentosegment(pathsegmenttoken tokenin, iedmmodel model, iedmstructuredtype edmtype, odatauriresolver resolver)\r\n @ microsoft.odata.core.uriparser.visitors.selectpropertyvisitor.processtokenaspath(nonsystemtoken tokenin)\r\n @ microsoft.odata.core.uriparser.visitors.selectpropertyvisitor.visit(nonsystemtoken tokenin)\r\n @ microsoft.odata.core.uriparser.parsers.selectbinder.bind(selecttoken tokenin)\r\n @ microsoft.odata.core.uriparser.parsers.selectexpandbinder.bind(expandtoken tokenin)\r\n @ microsoft.odata.core.uriparser.parsers.selectexpandsemanticbinder.bind(iedmstructuredtype elementtype, iedmnavigationsource navigationsource, expandtoken expandtoken, selecttoken selecttoken, odatauriparserconfiguration configuration)\r\n @ microsoft.odata.core.uriparser.odataqueryoptionparser.parseselectandexpand()\r\n @ microsoft.crm.extensibility.odata.crmodataentitytypeserializer.createselectexpandnode(entityinstancecontext entityinstancecontext)" } } } }
if delete records-> deactivate business process -> add new data , check webapi, working fine. when activate business process , add new data getting above error p.s: have not done coding/customization business process flow , entity. still getting error
what can done resolve this?
looks bug in web api endpoint. community forums reference same issue...
the web api endpoint still has limitations , doesn't mimic organizationservice behavior so, next version (9.x.x) if stuck maybe try applying update (and use v8.1 in url) as, or raise ms support case.
if still stuck, try same using odata / organizationservice maybe.
Comments
Post a Comment