Hi Jeffrey,

thanks for checking! Glad to see that this might be fixed with our next update!

The cause of the problem appears to lie in the computed fields of the table, the macros used might not work in a different table/class. Other computed fields ("Name", "Identifier", "TypeVersion") don't work either.

Meanwhile I found a workaround:

Instead of using the computed field "Name" it's contents can be computed explicitely. It's not 100% the same, because some details, eg taking into accout the separator characters, are missing but it works for me!

CREATE TABLE UKEr.Test AS
SELECT REPLACE($EXTRACT($PIECE(m.RawContent,'|',9),1,7),'^','_') Name, h.Status
FROM EnsLib_HL7.Message m, Ens.MessageHeader h
WHERE h.MessageBodyClassName='EnsLib.HL7.Message' AND h.MessageBodyID = m.ID

Regards
Stefan

Hi Robert,

thanks for your "guess" but I tried this already - unfortunately it doesn't work.

I also tried creating a view with a different name for that field - didn't work either.

Regards

Stefan

Thanks Benjamin for the detailed explanation and the article!

Now I get it: the class is mapped to a read-only database not the data and tune table tries to update the class definition.

I will try using the workaround suggested by Julius.