back to top

Unwrapping a Lazy Loaded Entity object in the SalesLogix web entity model

When using IQueryable to look for records within an Entity collection you will likely run into an error at some point when trying to add a condition to search for when that condition is a related entity property, or is a calculated entity property.

For instance, lets say we have the Sales Order entity that has had a calculated entity property added to it that shows the sum of the products tied to the order, represented as Sage.Entity.Interfaces.ISalesOrder.CalculatedTotal.

If we try to find orders that have more than $10,000 worth of orders using IQueryable like so:

Sage.Platform.RepositoryHelper<ISalesOrder> repository =
Sage.Platform.EntityFactory.GetRepositoryHelper<ISalesOrder>();
Sage.Platform.Repository.ICriteria criteria = repository.CreateCriteria();
criteria.Add(repository.EF.Eq(“Account.Id”, account.Id.ToString()));
criteria.Add(repository.EF.Gt(“CalculatedTotal”, “Invoice”));           
criteria.AddOrder(repository.EF.Desc(“CreateDate”));
System.Collections.Generic.IList<Sage.Entity.Interfaces.ISalesOrder> orders = criteria.List<Sage.Entity.Interfaces.ISalesOrder>();

It is likely that you will get an error stating that the ISalesOrder interface does not implement a property called CalculatedTotal.  This is because during the query the entities involved are not unwrapped, meaning that child entity properties, relationships, and calculated fields are generally not available. 

There is a way of getting around this, using a bit of a double query.  You can utilize IQueryable in conjunction with the Sage.Platform.EntityFactory assembly.  The EntityFactory.GetById class does provide an unwrapped version of the entity object to you.  So in the above case we can change it slightly to do this

System.Collections.Generic.IList<Sage.Entity.Interfaces.ISalesOrder> myOrders = new System.Collections.Generic.List<Sage.Entity.Interfaces.ISalesOrder>();

Sage.Platform.RepositoryHelper<ISalesOrder> repository =
Sage.Platform.EntityFactory.GetRepositoryHelper<ISalesOrder>();
Sage.Platform.Repository.ICriteria criteria = repository.CreateCriteria();
criteria.Add(repository.EF.Eq(“Account.Id”, account.Id.ToString()));        
criteria.AddOrder(repository.EF.Desc(“CreateDate”));
System.Collections.Generic.IList<Sage.Entity.Interfaces.ISalesOrder> orders = criteria.List<Sage.Entity.Interfaces.ISalesOrder>();
foreach(Sage.Entity.Interfaces.ISalesOrder order in orders)
{
    Sage.Entity.Interfaces.ISalesOrder unwrappedorder = Sage.Platform.EntityFactory.GetById<Sage.Entity.Interfaces.ISalesOrder>(order.Id.ToString());
    if (unwrappedorder.CalculatedTotal > 10000) myOrders.Add(unwrappedorder);
}

Above, for each order at the account we instantiate a fully unwrapped Sales Order entity using the EntityFactory.GetById.  From there we can check to see if the Calculated Field meets are conditions and if it does we add it to a new IList.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos