bcolpaert / Colso.Xrm.DataTransporter

XrmToolbox plugin to help you to transfer records across organizations
MIT License
23 stars 16 forks source link

Message: Sql error: 'Incorrect syntax near the keyword 'order'.' #34

Open Kokulan365 opened 5 years ago

Kokulan365 commented 5 years ago

I copied the Fetch from Advance find and pasted in the filter, and getting the following error.

Message: Sql error: 'Incorrect syntax near the keyword 'order'.'

Message: Exception output:: System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near the keyword 'order'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaDa...).

If i remove the filter fetch, it works fine but i want to narrow down the list of records synced using Fetch query. Just wondering if anyone else had the same issue.

Thanks

maeg02 commented 5 years ago

Not yet, what is the XML you posted in there?

Jobengaru commented 5 years ago

Hi, I do have the same issue. The "order error" is not causing in the XML - I've deleted it in there, but the error is still there. I do not have a chance to use the filter. So it is unusable for me right now... Regards Ferdinand

maeg02 commented 5 years ago

Hi, I do have the same issue. The "order error" is not causing in the XML - I've deleted it in there, but the error is still there. I do not have a chance to use the filter. So it is unusable for me right now... Regards Ferdinand

So you do not have any filter at all anymore and still get the "order error"?

Jobengaru commented 5 years ago

Without any filter I do get an other Error Message while using the preview...

Jobengaru commented 5 years ago

System.Runtime.Serialization.SerializationException: Type 'Infoman.AzureStorage.BlobStorageException' in assembly 'Infoman.Crm.Annotations, Version=1.0.830.4, Culture=neutral, PublicKeyToken=b8a18aa05801839f' is not marked as serializable. at Microsoft.Crm.Sandbox.SandboxAppDomainHelper.Execute(IOrganizationServiceFactory organizationServiceFactory, Dictionary`2 sandboxServices, String pluginTypeName, String pluginConfiguration, String pluginSecureConfig, IPluginExecutionContext requestContext, Boolean enablePluginStackTrace, Boolean chaosFailAppDomain) at Microsoft.Crm.Sandbox.SandboxWorker.<>c__DisplayClass3_0.b__0(): Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #35E9172B.

Jobengaru commented 5 years ago

My fetch XML was like this:

Jobengaru commented 5 years ago

Can you see the Fetch XML?

Jobengaru commented 5 years ago

image

maeg02 commented 5 years ago

well, if I add something like this: `

` then I can do preview.

So if you can go into more details what you have done. What was the steps that you have taken? What input did you provide?

Jobengaru commented 5 years ago

Hi Markus, I'll try to get the Information for you tomorrow. Regards,

Ferdinand

Markus Erlandsson notifications@github.com schrieb am Do., 9. Mai 2019, 12:50:

well, if I add something like this: <link-entity name="account" from="accountid" to="objectid" link-type="inner" alias="ad"> <condition attribute="name" operator="like" value="%s%" /> then I can do preview.

So if you can go into more details what you have done. What was the steps that you have taken? What input did you provide?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bcolpaert/Colso.Xrm.DataTransporter/issues/34#issuecomment-490854820, or mute the thread https://github.com/notifications/unsubscribe-auth/AMAG5NOKLNS7FRYMZYOFPIDPUP6WTANCNFSM4GHHFWCQ .

LukePa1mer commented 5 years ago

I'm also getting the same error (incorrect syntax near keyword 'order') when using the following xml:

`

`

Any ideas?

maeg02 commented 5 years ago

I'm also getting the same error (incorrect syntax near keyword 'order') when using the following xml:

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false"> <entity name="adv_property"> <attribute name="adv_towncity" /> <attribute name="adv_postcode" /> <attribute name="ownerid" /> <attribute name="adv_addressline1" /> <attribute name="adv_name" /> <attribute name="adv_plotnumber" /> <attribute name="adv_postalnumber" /> <attribute name="adv_activetenantid" /> <attribute name="adv_propertystatusid" /> <attribute name="adv_blockid" /> <attribute name="adv_propertyid" /> <order attribute="adv_towncity" descending="false" /> <filter type="and"> <condition attribute="statecode" operator="eq" value="0" /> <condition attribute="adv_addressline1" operator="like" value="Garage%" /> </filter> </entity> </fetch>

Any ideas?

What happens if you put only the filter in this field instead, that is: <filter type="and"> <condition attribute="statecode" operator="eq" value="0" /> <condition attribute="adv_addressline1" operator="like" value="Garage%" /> </filter>

tpmeredith commented 5 years ago

I had same issue but taking the filter out like you said above @maeg02 fixed it for me

JFulfordMS commented 4 years ago

Get the same error with the following Fetch.

<fetch>
  <entity name="product" >
    <all-attributes/>
    <filter>
      <condition attribute="productid" operator="eq" value="adee84a8-2165-ea11-a811-000d3a10239f" />
    </filter>
  </entity>
</fetch>
LukePa1mer commented 4 years ago

JFulfordMS, you only need the filter part of the query.

Use this instead

<filter>
      <condition attribute="productid" operator="eq" value="adee84a8-2165-ea11-a811-000d3a10239f" />
</filter>
JFulfordMS commented 4 years ago

JFulfordMS, you only need the filter part of the query.

Use this instead

<filter>
      <condition attribute="productid" operator="eq" value="adee84a8-2165-ea11-a811-000d3a10239f" />
</filter>

Awesome, thank you sir!