Skip to main content

    Filter by idea status

    Filter by product

    863 Ideas

    rvgfox
    Problem Solver
    rvgfoxProblem Solver

    Allow setup IsKey property for dimension tables in SSL modelsSUBMITTED

    In tabular models, setting the `IsKey=true` property on dimensions has a significant impact on the structure and functionality of the model. Unique Identification: It indicates that the values in that column are unique and used to uniquely identify each row in the dimension table. This is crucial for maintaining referential integrity within the model. Relationships: Columns defined as keys are used to create relationships between the dimension table and fact tables. These relationships are essential for allowing measures in fact tables to correctly link with attributes in dimensions. Performance: The analysis engine can optimize model performance. Searches and queries become faster because the engine can use indexes on the key columns to efficiently locate rows. Prevention of Duplicates: Prevent duplicates in the dimension table. If the data in the dimension table is not unique, it can lead to incorrect results when querying data from fact tables. Facilitation of Calculations: Keys enable measures and other calculations to function more effectively, as they can be used to refer to specific rows in the dimension table on which the analysis is based. Data Modeling: In a modeling context, keys are fundamental for organizing and structuring data. They ensure that information in the model is arranged in a way that can be accurately analyzed and that relationships are coherent.Setting `IsKey=true` directly in the tables of the SSL model will have benefits

    KajEmergoContributor

    'Data Catalog' options which combine data from DG and DMSUBMITTED

    In one of our Exmon demo's a customer asked if it was possible to use the Exmon DM solution for creating a ‘Data Catalog’ which contains meta data such as descriptions, data owners, abbreviations, etc.The customer uses this before even building a data model, to make sure all business users are aligned regarding the data definitions. During the demo we discussed if it was possible to synchronize the DG rules defined by business users on the Turnkey solution into this DM table. In this case it was regarding a dimensional table called ‘Plant items’ and its attributes (columns) but it could be any table (e.g. Customer, Product, etc.). I have managed to do this with DM actions that trigger UPDATE statements which fetch data from the DG database (the DG rules SQL syntax as well as their descriptions).Personally, I think Exmon can tap into new markets by combining the DM and DG modules in a more intuitive way. For example, you could have a dropdown menu on the DG Turnkey solution where you could link a specific rule to a certain ‘Dimension’ or ‘Attribute’. Currently, you can fetch data from the DG database into the DM module to accomplish the above. But not the other way around.Visualizing a Data Catalog in DM is really something customers can benefit from, but it is just not completely incorporated into the product at the moment. @alex.van.wijnen can elaborate on this!