My existing solution in my Work Org has a relationship of many-to-many for Knowledge Article and Knowledge Article Template. I setup a solution with the 2 entities in my Development org and notice the relationship is one-to-many which makes more sense to me since you can only have 1 template for an Article.
My question is, would deleting the existing relationship in my Work Org and reestablishing it as one-to-many be a bad idea and cause issues on existing records? I want to add the template name field as a lookup in the Knowledge Article table and actually render the template used for the article in list views. I've looked at documentation but the relationship is not listed for me to confirm: (also this is noted for On-Prem but it is the only place I can find Entity documentation for Knowledge Article).
I've tried it with the relationship as is and the template Name is blank. I tried creating a new article from template assuming it wouldn't do it retroactively but no change. The solution in my Development org works the way I want it.
