LINQtoCRM

Closed Issue: "Or And Or" query generates wrong fetchxml [10089]

melg — Thu, 16 May 2013 05:53:03 GMT

Query:
var contacts = from c in provider.Linq<contact>()
where (c.firstname == "test" || c.firstname == "test2") &&
(c.accountrolecode.Value == 1 || c.accountrolecode.Value == 2)
select c;

Generated fetchxml

<fetch mapping=""logical"">
<entity name=""contact"">
<all-attributes />
<filter type=""or"">
<condition attribute=""firstname"" operator=""eq"" value=""test"" />
<condition attribute=""firstname"" operator=""eq"" value=""test2"" />
<condition attribute=""accountrolecode"" operator=""eq"" value=""1"" />
<condition attribute=""accountrolecode"" operator=""eq"" value=""2"" />
</filter>
</entity>
</fetch>

Expected fetchxml

<fetch mapping=""logical"">
<entity name=""contact"">
<all-attributes />
<filter>
<filter type=""or"">
<condition attribute=""firstname"" operator=""eq"" value=""test"" />
<condition attribute=""firstname"" operator=""eq"" value=""test2"" />
</filter>
<filter type=""or"">
<condition attribute=""accountrolecode"" operator=""eq"" value=""1"" />
<condition attribute=""accountrolecode"" operator=""eq"" value=""2"" />
</filter>
</filter>
</entity>
</fetch>

Closed Issue: Some combinations of .Where result in wrong fetchxml [10090]

melg — Thu, 16 May 2013 05:53:02 GMT

TestCase:
Expression<Func<contact, bool>> expression = c => (c.firstname == "test" || c.firstname == "test2") &&
(c.accountrolecode.Value == 1 ||
c.accountrolecode.Value == 2);
var actual = provider.Linq<contact>().Where(c => c.statecode.Value == ContactState.Active);
actual = actual.Where(expression);
var foobar = actual.
Where(c => c.contactid.Value == Guid.Empty);

Expected

<fetch mapping=""logical"">
<entity name=""contact"">
<all-attributes />
<filter>
<condition attribute=""statecode"" operator=""eq"" value=""0"" />
<condition attribute=""contactid"" operator=""eq"" value=""00000000-0000-0000-0000-000000000000"" />
<filter type=""or"">
<condition attribute=""firstname"" operator=""eq"" value=""test"" />
<condition attribute=""firstname"" operator=""eq"" value=""test2"" />
</filter>
<filter type=""or"">
<condition attribute=""accountrolecode"" operator=""eq"" value=""1"" />
<condition attribute=""accountrolecode"" operator=""eq"" value=""2"" />
</filter>
</filter>
</entity>
</fetch>

Actual

<fetch mapping="logical">
<entity name="contact">
<all-attributes />
<filter>
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="contactid" operator="eq" value="00000000-0000-0000-0000-000000000000" />
</filter>
</entity>
</fetch>

Source code checked in, #96133

Project Collection Service Accounts — Mon, 01 Oct 2012 21:40:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #96132

Project Collection Service Accounts — Mon, 01 Oct 2012 21:33:03 GMT

Checked in by server upgrade

New Post: join in LinqToCRM not working

Bernybon — Wed, 05 Oct 2011 19:45:45 GMT

I get the error :

Error 1 The type of one of the expressions in the join clause is incorrect. Type inference failed in the call to 'Join'. C:\Users\Administrator\Desktop\DEV_VM\TestChap2\ConsoleApplication1\Program.cs 127 26 ConsoleApplication1

But my code is this one:

var queryx = from c in orgContext.ContactSet
                         join a in orgContext.AccountSet
                         on c.ContactId equals a.PrimaryContactId
                         select new { contact_name = c.FullName, account_name = a.Name };
            foreach (var c in queryx)
            {
                Console.WriteLine(c.account_name + c.contact_name);
            }

Anyone would have an idea ?

Created Issue: ispriceoverriden attribute not available on invoice/opportunity products [11943]

tommc — Thu, 16 Sep 2010 10:13:52 GMT

Cannot set this attribute

New Post: Problems in Many to Many

Gamalof — Sun, 15 Aug 2010 08:37:21 GMT

Hi,

I always get this error MSG "Server was unable to process request" whenever i try to make a query against the generated ManyToMany class. My Query is simple as it can be, it looks like

from b in CrmQueryProvider.Linq<Bridge>()
select b;

Where Bridge is the name of the generated class in the ManyToMany.cs

More information:

The problem comes from the Fetch method in CrmWebService.cs class.

Any suggestions ?

Thanks so much

New Post: Any idea when Linq to CRM will come out of beta?

MaartenUreel — Fri, 30 Jul 2010 07:03:45 GMT

From the guys at Xrm Linq:

http://www.xrmlinq.com/crm-sdk-4-0-12-bugs-limitations

New Post: Any idea when Linq to CRM will come out of beta?

friism — Thu, 29 Jul 2010 19:38:07 GMT

That's interesting, Martin. I did not realise that filtering is done client-side with the MS SDK Linq provider. Also, according to this page:http://msdn.microsoft.com/en-us/library/ff681573(v=MSDN.10).aspx the provider supports joins. You mention that it doesn't support linked entities, can you be more specific?

New Post: Any idea when Linq to CRM will come out of beta?

MaartenUreel — Thu, 29 Jul 2010 15:08:07 GMT

Why are you killing the project? Because of the cheap LINQ provider in the SDK? The one that cannot be used in plugins? The one that fetches a shitload of records to the client to check conditions there? The one that isn't able to use FetchXML to work with Linked Entity's? The one of which the caching mechanism sucks?

I suggest you continue this project ;-)

Source code checked in, #63489

_TFSSERVICE — Tue, 27 Jul 2010 20:28:19 GMT

Checked in by server upgrade

New Post: Any idea when Linq to CRM will come out of beta?

digioz — Sun, 25 Jul 2010 14:58:17 GMT

Wow, sorry to hear you are killing the project. On the other hand though it is great that Microsoft supports Linq now. Thanks for the info.

Pete

New Post: Any idea when Linq to CRM will come out of beta?

friism — Sun, 25 Jul 2010 11:11:26 GMT

Hi Pete, Microsoft has released a linq query provider with the CRM SDK. I recommend you check that out: http://friism.com/linqtocrm-obsoleted

New Post: Any idea when Linq to CRM will come out of beta?

digioz — Sat, 24 Jul 2010 22:48:37 GMT

Does anyone know when Linq to CRM is scheduled to be released and come out of beta?

Thanks,

Pete

New Post: CRM SDK 4.0.0012 now includes a Linq-to-CRM query provider

praty — Thu, 03 Jun 2010 10:02:48 GMT

Selecting out of joined entities come to mind at least.

New Post: CRM SDK 4.0.0012 now includes a Linq-to-CRM query provider

friism — Tue, 25 May 2010 09:32:48 GMT

@praty It's a valid point, but I think the FetchXML stuff that can't be mapped to QueryExpression is pretty marginal ("Average" anyone?). Do you have example of FetchXML features you need that aren't doable with QueryExpression?

New Post: CRM SDK 4.0.0012 now includes a Linq-to-CRM query provider

praty — Mon, 24 May 2010 20:31:36 GMT

http://blogs.msdn.com/b/crm/archive/2010/05/13/microsoft-dynamics-crm-sdk-4-0-12-and-the-advanced-developer-extensions.aspx

"It should be emphasised that the LINQ query ultimately maps down to a QueryExpression, and hence you are as limited in the scope of queries as you currently are."

As QueryExpressions don't support everything that FetchXML does the MS code (haven't tried) could be more limited in features.

Updated Wiki: Home

friism — Sun, 23 May 2010 08:11:13 GMT

UPDATE Version 4.0.12 of the Microsoft CRM SDK includes a Linq query provider for CRM. I (friism) haven't tested it, but you should probably give it a try before going with LINQtoCRM. Read the short announcement.

Introduction

The Linq to CRM project provides a custom query provider for Microsoft Dynamics CRM/xRM (mscrm).

Found a query you think should work, but LinqtoCRM breaks or returns the wrong data? Please create a work-item or send it to me at friism+linqtocrm@gmail.com.

Features

Where-clauses of some complexity (And/Or, greater/less-than etc.)
Joins through relationtionships, including many-to-many ones
Translation of queries to FetchXML
Parsing of result to anonymous types or CRM entities
Orderby
Skip/Take
Count
Contains, StartsWith, EndsWith
CRMMetal tool for generating many-to-many relationship classes

Ressources

Todo

A visual debugger/visualizer to show were you've been too ambitious with your query. Bart De Smet seems to have the right idea
A "pedal-to-the-metal" toggle. If the code will be running with acess to the SQL-server, the developer can specify that the query should be translated to SQL and run on the filtered views at the flick of a switch.
The CRM web service is tangled up in the queryprovider code. It would be desirable if it could be moved outside and accessed though an interface. The code is rather dependent on the types exposed by the web service proxy-classes and it is not clear how this dependency could be removed without implementing something along the lines of SQLMetal/SPMetal.

Credits

Mel Gerats (implemented paging, contains and loads of other stuff)
Petteri Räty (rewrote query generation code, improved support for projections and conditions)
Michael Friis (initial version, various updates,maintenance)
Bart De Smet for the inspirational LINQtoSharePoint implementation
Michael Höhne for his FetchXML library
Matt Warren for his articles on QueryProvider-building: http://blogs.msdn.com/mattwar/archive/2007/08/03/linq-building-an-iqueryable-provider-part-v.aspx

Updated Wiki: Home

friism — Sun, 23 May 2010 07:09:47 GMT

UPDATE Version 4.0.12 of the Microsoft CRM SDK includes a Linq query provider for CRM. I (friism) haven't tested it, but you should probably give it a try before going with LINQtoCRM.

Introduction

Features

Where-clauses of some complexity (And/Or, greater/less-than etc.)
Joins through relationtionships, including many-to-many ones
Translation of queries to FetchXML
Parsing of result to anonymous types or CRM entities
Orderby
Skip/Take
Count
Contains, StartsWith, EndsWith
CRMMetal tool for generating many-to-many relationship classes

Ressources

Todo

A visual debugger/visualizer to show were you've been too ambitious with your query. Bart De Smet seems to have the right idea
A "pedal-to-the-metal" toggle. If the code will be running with acess to the SQL-server, the developer can specify that the query should be translated to SQL and run on the filtered views at the flick of a switch.
The CRM web service is tangled up in the queryprovider code. It would be desirable if it could be moved outside and accessed though an interface. The code is rather dependent on the types exposed by the web service proxy-classes and it is not clear how this dependency could be removed without implementing something along the lines of SQLMetal/SPMetal.

Credits

Mel Gerats (implemented paging, contains and loads of other stuff)
Petteri Räty (rewrote query generation code, improved support for projections and conditions)
Michael Friis (initial version, various updates,maintenance)
Bart De Smet for the inspirational LINQtoSharePoint implementation
Michael Höhne for his FetchXML library
Matt Warren for his articles on QueryProvider-building: http://blogs.msdn.com/mattwar/archive/2007/08/03/linq-building-an-iqueryable-provider-part-v.aspx

New Post: CRM SDK 4.0.0012 now includes a Linq-to-CRM query provider

friism — Sun, 23 May 2010 06:56:35 GMT

Thanks for the heads-up, I'll update the frontpage with a link.