Hello,
I have the strange situation that the activation of a "Valid Time State Enabled" = "Yes" leads to a synchronisation error. Here is the detailed description of the situation:
My view is based on a query with multiple tables including two times LogisticsPostalAddress
The view contains the following fields with some simple computed columns:
public static server str accountNumSQL() { TableName view = tableStr(???BankAccountVendCustTransView); ; return SysComputedColumn::if(SysComputedColumn::isNullExpression(SysComputedColumn::comparisonField(view, identifierStr(CustTable), fieldStr(CustTable, AccountNum))) , SysComputedColumn::returnField(tableStr(???BankAccountVendCustTransView), identifierStr(VendTable), fieldStr(VendTable, AccountNum)) , SysComputedColumn::returnField(tableStr(???BankAccountVendCustTransView), identifierStr(CustTable), fieldStr(CustTable, AccountNum))); }
At this point everything works fine (Build & Sync). As a result I see all values in the view as expected.
Because some of the customers / vendors changed their addresses the join on the LogisticsPostalAddress will double the records because of the "ValidTimeState" handling of the table. So I tried to get rid of this with the view property "Valid Time State Enabled" = "Yes". (the relevant ValidFrom / ValidTo fields are already in the view and were synchronised correctly before the change of the property).
After changing the property the build runs without an error but the synchronisation ends up with a strange error pointing to the computed column:
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt.".....
Do you have any hint for me how I could solve this.
Thanks
Sebastian