AnsweredAssumed Answered

Feature service layer with computed column

Question asked by joseph.joyce on Aug 6, 2015
Latest reply on Nov 10, 2015 by tpcolson

I have a query layer published in map and feature service. When I try to add a new feature using applyEdits on that layer I get this error in the log.

 

Database error: Underlying DBMS error[[Microsoft][SQL Server Native Client 11.0][SQL Server]The column "..." cannot be modified because it is either a computed column or is the result of a UNION operator.].

 

I removed that column from the query but I still get that error. Is there any way to get the feature service to ignore that column when editing? I'm not sure why it is accessing that column in the first place since I didn't reference it in the attributes object. Is there a workaround or does applyEdits currently just not work with tables that have computed columns?

Outcomes