sData issue - CreateOpportunity

[byronb]

Hi guys

I am using Orbis TaskCentre and their Web Service Connector to import data into SLX V8, till now have not had many issues working with the various operation. I am however getting an error when trying to use the CreateOpportunity operation.

The issue is I am recieving an error "Enitity does not exist", I have checked and double checked each ID key I am passing through (ACCOUNTID & CONTACTID) and both are valid IDs within our installation. Can anyone help me get to the root of the problem?

Are there any tools I can use to debug this effectively?

The request I get from Fiddler is as follows:

POST http://win2008r2slx:3333/sdatatest/slx/dynamic/-/opportunities HTTP/1.1
Content-Type: application/atom+xml; type=entry
Host: win2008r2slx:3333
Content-Length: 841
Expect: 100-continue
Connection: Keep-Alive

<entry xmlns:sdata="http://schemas.sage.com/sdata/2008/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2005/Atom"><sdata&colon;payload><Opportunity xmlns="http://schemas.sage.com/dynamic/2007" sdata&colon;uuid="4eb85efc-1d90-4a32-b789-dcd433c896d3"><Closed>false</Closed><CloseProbability>1</CloseProbability><DaysInPipeline>670</DaysInPipeline><Description>CBS - Joining as partner</Description><EstimatedClose>2013-08-30T23:00:00</EstimatedClose><SalesPotential>2000</SalesPotential><Status>Open - Stage 4 - Evaluation/Awaiting Decision</Status><Type>Consulting Partner</Type><OLDOPPORTUNITYID>O6UJ9A0000CW</OLDOPPORTUNITYID><OLDACCOUNTID>A6UJ9A001Z4X</OLDACCOUNTID><Account sdata&colon;key="A6UJ9A000BEY" /><AccountManager sdata&colon;key="U6UJ9A00000J" /><Owner sdata&colon;key="U6UJ9A00000J" /></Opportunity></sdata&colon;payload></entry>

The response:

HTTP/1.1 404 Not Found
Cache-Control: private
Content-Type: application/xml
Server: Microsoft-IIS/7.0
Set-Cookie: ASP.NET_SessionId=lps4r254prg4cv1l34o3rtd2; path=/; HttpOnly
Set-Cookie: SlxStickySessionId=a6TN7h7+/NfwDezCtnaUKY5evI5kJBrZjSWFmI6q5S6ykCkEdbs0tyaikrx9Tqz+nzn/z9nPLQchnOBhG6xa9g==; path=/; HttpOnly
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Wed, 07 Aug 2013 11:25:57 GMT
Content-Length: 1019

<?xml version="1.0" encoding="utf-8"?>
<sdata&colon;diagnoses xmlns="http://schemas.sage.com/sdata/2008/1" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlnspensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:sme="http://schemas.sage.com/sdata/sme/2007" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sdata="http://schemas.sage.com/sdata/2008/1" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:http="http://schemas.sage.com/sdata/http/2008/1" xmlns:sync="http://schemas.sage.com/sdata/sync/2008/1">
<sdata&colon;diagnosis>
<sdata&colon;severity>error</sdata&colon;severity>
<sdata&colon;sdataCode>BadQueryParameter</sdata&colon;sdataCode>
<sdata&colon;applicationCode>source=SDataExceptionDiagnoses; exceptionKind=BaseException; exceptionSource=Sage.Platform; exceptionType=Sage.Common.Syndication.DiagnosesException; slxErrorId=SLX5FD87FBB5CABDF44</sdata&colon;applicationCode>
<sdata&colon;message>Entity does not exist.</sdata&colon;message>
<sdata&colon;stackTrace />
<sdata&colon;payloadPath />
</sdata&colon;diagnosis>
</sdata&colon;diagnoses>

[NathanBaulch]

Are you absolutely sure all your FK values are valid, including AccountManager and Owner? Your request works for me in the eval DB so long as I specify valid FK values, otherwise I get the same "Enitity does not exist" error you're seeing.

[byronb]

Thanks for your response mate

If I query each ID outputted from Fiddler all the IDs exist within the new SLX Database (AcctMgr, AccountID and Owner).

This is odd

The IDs are mapped to the key attribute of each element (AcctMgr, Owner and Account). Frustrating to say the least. Will carry on testing and see if I can find the issue.

[ChapmanFreebornNath]

Hi Byron,

Have you solved this issue?

I have seen problems in the past with surrounding the ID value with double quotation marks when creating SData requests, I'm pretty sure you need to be surrounding them with single quotes. e.g 'A6UJ9A0001FG' instead of "A6UJ9A0001FG" .