The adapter code lets the primary key fields be set but the self servicing does not, throws the read only error:

OrderEntity order = new OrderEntity(); order.IsNew = false; order.OrderId = 27; --THROWS ERROR WITH SelfServicing

Looking at the source code, the ValidateValue method of EntityBase2 allows PrimaryKey + ReadOnly combinations while EntityBase.ValidateValue just looks at ReadOnly.

Is it possible to get the SelfServicing to behave the same as the Adapter?

Brian Chance

This is the lazy-loading of SelfServicing template. As the field is PK and Identity, thus Read-Only, it can't be updated. Why do you want set a value on that field?

If I already know the id, I can just set the values (like from a web form post).

like: Order order = new Order(); order.IsNew = false; order.OrderId = 27; order.Total = 125.00; order.Save();

I know I could load it from the database, but want to save the trip (and simplify some code).

_And _it works with the adapter.

Brian

I see. In that case please use ForcedCurrentValueWrite:

order.Fields["OrderId"].ForcedCurrentValueWrite(27);

The reason it works in adapter, is that in adapter you need to set the PK to fetch an entity using FetchEntity(). In selfservicing, you don't use that pattern.

Setting the PK which is an identity is hardly necessary, only when you use it as an entity for direct updates or when you want to change the PK (which is not recommended).

I really only wanted to set the PK then force an update using IsNew=false.

Will use the ForcedCurrentValueWrite().

Thanks.