Hello Yuyao,

I don’t believe this to be a best practice, but if you are set on displaying data from multiple knowledge models / data models at once on a view, I believe the only way to do this would be in legacy views - each knowledge model’s KPIs would be displayed using separate embedded views, as you can only have one KM assigned to a view. So make a view for each KM, then create a master view with each of these embedded. The limitation here is that you couldn’t have any KPI’s that make use of data in another knowledge / data model, as there isn’t really a way for them to interact with eachother (each KM can only reference one DM)

As for best practices, in this scenario I think the best thing to do would to have all of the data within one data model, which would avoid the workaround / limitations above, as well as other limitations not mentioned.