Layer field artifact remains on Sankey when field no longer exists in data view.

[bfgiordano]

I had the situation where my ES index field name was changed for a field used in my Sankey - so now old field effectively no longer exists in the index. When I edited the sankey to removed the tier/layer for the no-longer existing field, updated my Sankey to use the newly named field and updated/saved the visual, the Sankey displayed a "disconnected" tier/layer to the far left - ie, as the "first" tier. I had to recreate the visual as there was no way (without tryng to actually edit the ndjson for the Sankey) to remove the non-existent field reference.

I don't have a picture to send as this happened on a restricted access environment.
We are using ES/K 8.4.3

[ch-bas]

Hi @bfgiordano, thank you for reporting this issue. I will try to take a look on the problem and get back to you. Thanks!

[bfgiordano]

Just want to be clear on this ticket as this is a more critical bug, in my opinion.
If a field used on a Sankey vis is no longer available in the index/Kibana data view for the Sankey, when the Sankey is edited, to replace the "bad" field, all references to the field are not be cleaned out of the Sankey json which causes an "artifact" to remain on the visualization.