In FineBI there are Model View in Analysis Subject and Associated View in Public Data. Why is it necessary to create reletionships between tables 2 times? What is the purpose of each model?
Moreover, in Associated view there is no N:N relationship, whereas in Model View this type of relationship exists. What does it mean in terms of restrictions?
In FineBI, the concept of Model View and Associated View exists to fulfill different needs and purposes in data analysis. Let's break down the differences and the reasons for creating relationships between tables twice.
Model View in Analysis Subject:
Purpose: Model View is specifically designed for data modeling and defining relationships between tables. It's a place where you can create complex data relationships, such as one-to-one, one-to-many, and many-to-many relationships.
Relationships: In Model View, you establish relationships between tables to define how they are connected. This is necessary for accurate data retrieval and analysis. For instance, a sales order table might be related to a customer table with a one-to-many relationship, indicating that one customer can have multiple orders.
N:N Relationship: Model View supports N:N relationships, where multiple records in one table can be related to multiple records in another table. This is typically achieved through an association table or bridge table that holds the keys of both related tables.
Associated View in Public Data:
Purpose: Associated View is mainly used for data presentation and quick data analysis. It's a simplified version of a data model, suitable for less complex analysis tasks or for users who don't require the full power of Model View.
Relationships: In Associated View, relationships are typically predefined and less flexible than in Model View. This is because Associated View focuses on ease of use and quick analysis, rather than complex data modeling. It typically supports one-to-one and one-to-many relationships but not N:N relationships.
N:N Relationship Limitation: The absence of N:N relationships in Associated View is a limitation by design. It reflects the fact that Associated View is not intended for handling complex data relationships. Instead, it's geared towards simpler analysis tasks where N:N relationships are not commonly required.
In summary, the reason for creating relationships between tables twice in FineBI is to cater to different use cases and levels of complexity. Model View offers full flexibility and support for complex relationships, while Associated View provides a simplified interface for quick analysis tasks. The absence of N:N relationships in Associated View reflects its focus on simplicity and ease of use.
Ekaterina874994(提问者)And what about row permission? I want to perform the case similar to described here
https://help.fanruan.com/finebi-en/doc-view-4892.html
Is it possible without creating Associated View? It seems that row permissions applied to a table, are not applied to other tables from the Model View, if Associated View is not crerated. Is it true?
JL98 回复 Ekaterina874994(提问者)Right, if you do not create an association view, the row permissions of the table will not be applied to other tables in the model view, because there is no association relationship, there is no way to display the corresponding data of the platform login user. Of course, if the information in your table and decision platform has fields that can directly set permissions, you can omit the association attempt
Ekaterina874994(提问者)Just one more question concerning row permission and associated view. I create a Star model (fact with dimension tables around) in Associated View, for example, tables Fact, Regions and Products. I assign row permission using a field from Regions. In a dashboard I see that tables Fact and Regions are filtered correctly (according to permissions), however, Products are not filtered. The user can see all the product names, even those not sold in his/her region. So, permissions are not applied to the whole data model, but only to the tables DIRECTLY related to each other. Can I apply row permissions to the WHOLE model from associated view? (Products and Regions have relationships with Fact table, but do not have direct relationship between each other)
1min目标场景问卷
立即参与
