Skip to main content

    Filter by idea status

    Filter by product

    859 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! 

    andrew.gebhard
    TimeXtender Xpert
    andrew.gebhardTimeXtender Xpert

    Manage Job QueueSUBMITTED

    Hi team, An issue that I am running into relatively often is that a job fails to fail or complete, staying in the ‘running’ state indefinitely. Sometimes cloud services can experience transient issues, which may cause these anomalies. More importantly, however, there is no way to clear the queue, stop existing jobs, or force a job to restart when it's already running. Furthermore, there is no timeout on jobs, so they can continue to run forever.Example: this job has been in the running state for about 30 hours. It runs a number of Ingest Transfer and Cleanup tasks:Job MonitorIn the ODX Execution Queue I can see that there are no ODX tasks waiting or running, so I cannot cancel anything from there: Ingest Instance Execution QueueStarting the job manually or via eXmon does not work, I get the message failed to run message from eXmon: “The TimeXtender job 'ODX - OneLake and FTP - Transfer + Cleanup' is already running”. If this was a prepare or deliver job, it would now be blocking the other prepare or delivery jobs from running. -- The only way to reset the jobs is by stopping the ODX Service and restarting it. This causes all ODX tasks (also outbound) to fail instantly, which is far from ideal in an environment where data is constantly being loaded, and lengthy reloads may be running outside of work hours. It's also difficult to explain to a client that they may need to do this periodically to keep their environment running. We should have more control over the how jobs run, fail, and cancel. Jobs waiting or running in the queue should be able to be removed without restarting a service and a large unplanned impact to the platform. Kind regards,Andrew

    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Improve synchronizing Prepare Instance with Ingest InstanceSUBMITTED

    In the 6xxx release when you synchronize your Prepare instance with an Ingest instance there are two things that may happen:TimeXtender automatically handles changes, no input is required. TimeXtender cannot automatically deal with the changes and user input is required to tell TimeXtender how mappings should be set up.In both cases, there are significant improvements to be made (or deficiencies handled). I will list my issues and suggestions for each in the following sections:Changes can be handled automaticallyIt is usually great that TimeXtender handles things for you, but there is currently no way of seeing the changes that were applied. In the 20.10.x BU setup, a source synch would show you what changes were applied. In my opinion what should be available is the following:a synchronize which can be auto-resolved should show the proposed (additions, removals, mutations) changes. It only applies them if the user agrees it should be possible to review the current mapping state in its totality the interface showing all mappings should be sortableChanges cannot be handled automaticallyWhen TimeXtender cannot handle changes, it shows a dialogue with all mappings (one line per table, followed by all field mappings). You need to scroll through a potentially huge list of mappings to find any that are problematic. This dialogue will not accept empty (None) mappings and give you a warning. What we need here is the following:the interface showing all mappings should be sortable (to quickly sort on tables with errors) it should be possible to collapse and expand tables (start with everything collapsed) so that fields can be hidden for a shorter list it should be possible to select None as a mapping. If a field is removed from source, there is no reason why None is not a valid mapping to DWH. It is fine to mark the field visually, but if I want a field without a mapping that is not always an error it should be possible to filter the interface so I can focus on the problems only instead of needing to scroll through thousands of mappings with pgdn to try and find one problematic mapping it should be possible to review the current mapping state in its totalityI am not sure how mapping sets are currently visualised (if they are at all), but those rules should be reachable from the general mapping interface.