Field replacement in merges

  • 26 November 2020
  • 0 replies

Userlevel 2

I renamed a field in a LookML view from myview.old_field to myview.new_field.

I used the Content Validator to replace all of the references and I worked well in most of the cases but I found out that it did not replace the references in merges.

I believe this is due to the view renaming convention with duplicate fields that happens in merges as q1_myview.old_field.

I would like to know if there is an estimated date for this to be fixed, I believe this should not be happening.



This topic has been closed for comments