Unable to create a constant value of type 'AddressModel'. Only primitive types or enumeration types are supported in this context

Question

In the EF query below, any time an child contact address field is assigned to the Address property of the TaxReceiptsWithChargesModel, I get the error message:

"Cannot create constant value of type 'AddressModel'"

If I comment out the line that assigns the address, then the error does not occur. What could the issue be?

Edit: Typically, the causes of this problem I've seen elsewhere have to do with using the contains or equals LINQ methods, but the cause of this particular issue seems to lie elsewhere.

Here are the relevant sections of code:

            //GetChildContactAddress
            var childContactAddress = lgcCcpModel.ChildContacts
                .Where(cc => cc.UUID == ltrm.ChildContactId)
                .Select(cc => new AddressModel()
                {
                    Address1 = cc.Address.STREET,
                    City = cc.Address.CITY,
                    Province = cc.Address.PROVINCE,
                    PostalCode = cc.Address.POSTALCODE
                }).FirstOrDefault();

        //Create the Tax Receipt Model with the Charge List
        return unitOfWork.LegacyTaxReceiptStore.GetQuery()
            .Where(ltr => ltr.LegacyTaxReceiptId ==         ltrm.LegacyTaxReceiptId)
            .Select(c => new TaxReceiptsWithChargesModel()
            {
                LegacyTaxReceiptId = ltrm.LegacyTaxReceiptId,
                ChildContactId = ltrm.ChildContactId,
                ChildContact = ltrm.ChildContact,
                EmailAddress = ltrm.EmailAddress,
                ChildId = ltrm.ChildId,
                ChildName = ltrm.ChildName,
                ChargesTotal = ltrm.ChargesTotal,
                TaxReceiptAmount = ltrm.TaxReceiptAmount.Value,
                TaxReceiptYear = ltrm.TaxReceiptYear,
                Address = childContactAddress,
                ReceiptNumber = $"{ltrm.TaxReceiptYear}-{ltrm.LegacyTaxReceiptId.ToString().PadLeft(6, '0')}",
                Charges = taxReceiptChargesModelList,
            }).FirstOrDefault();


public class TaxReceiptsWithChargesModel : ITaxReceiptsModel
    {
        public int LegacyTaxReceiptId { get; set; }
        public string ChildContactId { get; set; }
        public string ChildContact { get; set; }
        public string EmailAddress { get; set; }
        public IAddressModel Address { get; set; }
        public decimal? OpeningBalance { get; set; }
        public decimal? InvoicesTotal { get; set; }
        public decimal? PaymentsTotal { get; set; }
        public string ChildId { get; set; }
        public string ChildName { get; set; }
        public decimal? ChargesTotal { get; set; }
        public decimal? TaxReceiptAmount { get; set; }
        public string State { get; set; }
        public int TaxReceiptYear { get; set; }
        public string ReceiptNumber { get; set; }
        public int? BinaryDocumentId { get; set; }
        public List<TaxReceiptsChargesModel> Charges { get; set; }
    }

public interface IAddressModel
    {
        string Address1 { get; set; }
        string Address2 { get; set; }
        string City { get; set; }
        string Country { get; set; }
        string PostalCode { get; set; }
        string Province { get; set; }
    }

ocuenca · Accepted Answer · 2016-06-24T17:58:22.947

That is because childContactAddress object (and also taxReceiptChargesModelList) is already in memory and when you try to assign a complex object in the projection of your second query, the Linq provider can't translated that object to SQL. One option can be call AsEnumerable extension method:

  return unitOfWork.LegacyTaxReceiptStore.GetQuery()
        .Where(ltr => ltr.LegacyTaxReceiptId ==ltrm.LegacyTaxReceiptId)
        .AsEnumerable()
        .Select(c => new TaxReceiptsWithChargesModel()
        {
            LegacyTaxReceiptId = ltrm.LegacyTaxReceiptId,
            ChildContactId = ltrm.ChildContactId,
            ChildContact = ltrm.ChildContact,
            EmailAddress = ltrm.EmailAddress,
            ChildId = ltrm.ChildId,
            ChildName = ltrm.ChildName,
            ChargesTotal = ltrm.ChargesTotal,
            TaxReceiptAmount = ltrm.TaxReceiptAmount.Value,
            TaxReceiptYear = ltrm.TaxReceiptYear,
            Address = childContactAddress,
            ReceiptNumber = $"{ltrm.TaxReceiptYear}-{ltrm.LegacyTaxReceiptId.ToString().PadLeft(6, '0')}",
            Charges = taxReceiptChargesModelList, 
        }).FirstOrDefault();

Update

Your issue can be also solve this way:

var result=unitOfWork.LegacyTaxReceiptStore.GetQuery()
            .FirstOrDefault(ltr => ltr.LegacyTaxReceiptId ==ltrm.LegacyTaxReceiptId);

return new TaxReceiptsWithChargesModel()
        {
            LegacyTaxReceiptId = result.LegacyTaxReceiptId,
            ChildContactId = result.ChildContactId,
            ChildContact = result.ChildContact,
            EmailAddress = result.EmailAddress,
            ChildId = result.ChildId,
            ChildName = result.ChildName,
            ChargesTotal = result.ChargesTotal,
            TaxReceiptAmount = result.TaxReceiptAmount.Value,
            TaxReceiptYear = result.TaxReceiptYear,
            Address = childContactAddress,
            ReceiptNumber = $"{result.TaxReceiptYear}-{result.LegacyTaxReceiptId.ToString().PadLeft(6, '0')}",
            Charges = taxReceiptChargesModelList,
        };

I tried assigning the address after the initial query, but that produced the same result. I'll take a look at your first suggestion and the other one mentioned above. Thanks! — Andre Lashley, Jun 24 '16 at 17:34
That should be due to the string interpolation, I think that is not supported yet in Linq to Entities. I suggest to try with the first solution, `ToString` is also not supported — ocuenca, Jun 24 '16 at 17:36

score 1 · Answer 2 · edited May 23 '17 at 11:52

1

You have to apply [Serializable()] decorator however you cannot do it to interfaces.

Instead, implement your custom interface with ISerializable {}

A similar question has been answered below, credit of this post goes to Oded.

Why are interfaces not [Serializable]?

Cheers

edited May 23 '17 at 11:52

Community

1
1

answered Jun 24 '16 at 16:56

Ozan Gunceler

1,067
11
20

score 0 · Answer 3 · edited May 23 '17 at 12:32

0

Can you please tell what is point of using interfaces as a model property. Microsoft do not encourage use of in interfaces as a model property. You can restrict changes in your property by using getter and setter methods . See this post https://stackoverflow.com/a/8455558/2173098

edited May 23 '17 at 12:32

Community

1
1

answered Jun 24 '16 at 17:56

Shashank Sood

480
5
16

Fair enough, good point. This is an inherited code base. Perhaps we can look at making changes to it later on. – Andre Lashley Jun 24 '16 at 18:19

Unable to create a constant value of type 'AddressModel'. Only primitive types or enumeration types are supported in this context

3 Answers3

Update