It's a good question and probably an oversight. I'll add it as a new bug, but... just out of curiousity, why is this problematic for you?
Why breeze sends to server originalvaluesMap for unmapped property?
-
03-07-2023 - |
Question
I'm using breeze 1.4.11 with Web Api and EFContextProvider
on client after metadata fetched I extend entity type:
var addressStringProperty = new breeze.DataProperty({
name: "addressString",
isUnmapped: true
})
metadataStore.getEntityType('Account').addProperty(addressStringProperty);
this property is computed and used only on client
after entitymanager.saveChanges([accountEntity])
I see on server side in contextprovider.BeforeSaveEntity
that entityInfo.OriginalvaluesMap
contains Key "AddressString" with Value == null.
same thing with extending entity like:
var accountCtor = function() {
this.addressString = ko.observable()
};
metadataStore.registerEntityTypeCtor('Account', accountCtor);
How to omit this behaviour?
Solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow