View the original community article here
Last tested: Aug 20, 2019
Will the break-the-field-reference-to-find-and-replace-in-Content-Validator method not work for your use case because we want to change specific content in specific explores? Try adding a fields parameter like:
This will surface "Unknown field" errors in the Content Validator, but only for the specific explores you break (as opposed to breaking the field reference in the view file and having the reference break everywhere).