Remove _id in sinkAnswered
Is it possible to create a feature that will remove the "_id" property for data passing out of Sesam through a sink? It seems that it cannot be removed, and it may cause issues for receiving systems in some scenarios.
Do you have a specific sink in mind? This behaviour varies from sink to sink.Comment actions
The "json" sink is a sink that implements Sesam's JSON Push Protocol. It follows strict rules for the payload. The "http_endpoint" receiver is symmetrical to the sink and it support entities without an "_id" property, but in this case you can add DTL to add it for you before the entity reaches the sink. We don't think there is a limitation in the "json" or "rest" sink that require you to send the "_id" as part of the payload. If you think otherwise, then please create a support ticket.
Please sign in to leave a comment.