SearchOrders is throwing an error

[redmorello]

We've upgrade our V8.18.14 site to V13.5.2, and upgraded Vendr 2.4.1 > V13.1.14. In the process, our existing call to SearchOrders is now failing. This was the original code:

var commerceOrders = _orderService.SearchOrders((where) => where .FromStore(store.Id) .And(where.IsFinalized()) .And(where.HasProperty(Constants.Commerce.Properties.Customer.CsiAccountId, csiAccount.CsiAccountId))) .Items.ToList();

this is now failing with an error: "Value cannot be null. (Parameter 'type')"

I've then tried a really basic search and this is also failing:

var commerceOrders = _orderService.SearchOrders( (where) => where .FromStore(store.Id)).Items.ToList();

is there something wrong with our database? where can we start looking?

Forgot to add the stacktrace:

at Umbraco.Commerce.Infrastructure.Resiliency.PollyExecutionStrategyBase.Execute[TResult](Func1 operation, Func1 verifySucceeded)
at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute[T](IUnitOfWorkOptions options, Func2 action) at Umbraco.Commerce.Core.UmbracoCommerceUnitOfWorkProvider.Execute[T](Boolean autoComplete, Func2 action)
at Umbraco.Commerce.Core.Services.OrderService.SearchOrders(IQuerySpecification1 query, ISortSpecification1 sort, Int64 currentPage, Int64 itemsPerPage)
at Umbraco.Commerce.Core.Services.OrderService.SearchOrders(IQuerySpecification1 query, Int64 currentPage, Int64 itemsPerPage) at Umbraco.Commerce.Core.Services.OrderService.SearchOrders(Func2 query, Int64 currentPage, Int64 itemsPerPage)
at Web.Global.Core.Controllers.Api.OrdersController.GetPagedOrders(String culture, String filterType, Int32 pageNumber, Int32 pageSize, String pageSort, String searchTerm)

[mattbrailsford]

Can you please provide a full stack trace

[redmorello]

Sorry, was just editing the post as your replied !!

[mattbrailsford]

Hehe, no worries. Unfortunately it's not really telling me much in terms of what type is null 🤦‍♂️

[mattbrailsford]

Ahhhh, actually, this stuff usually happens when you are using custom price/amount adjusters. I think the type refers to the CLR type it's trying to resolve to deserialize the data in the database to. Have you ported all your adjusters and their types and ensure the fully qualified type as stored in the DB matches the type name and namespace of the adjusters in your code.

[redmorello]

Ah yes, thanks we do use a custom price adjuster. Changing the name in the table [umbracoCommerceOrderPriceAdjustment] has sorted the issue.