AnsweredAssumed Answered

Subset tries to insert computed column

Question asked by rvankruistum on Mar 19, 2018
Latest reply on Aug 6, 2018 by dovle01

I tried to find other questions related to this problem, but I couldn't find any. If this has already been answered somewhere please let me know.


When creating a subset that includes a table with a computed column I get an error saying that the insert failed (when I run the subset as a workflow in Javelin). The column is registered as a computed column in Datamaker, but this info doesn't seem to be used by GTSubset. We've gotten around this by specifying the column mapping and not including the computed column, but I kind of expected this to be unnecessary as TDM already "knows" it's a computed column.


Is this expected behaviour, or maybe there is something wrong with the registration?