Build better products with our product team
The current Execution Log dialogue in Ingest is frustrating to use. The default display width and filling of the columns means you are required to widen the window to see if tasks failed or succeeded: “Completed” may look like a positive result when the opposite is true:Please change this dialogue so that all important information is visible without needing to reshape the window and columns. While this is an Idea for a specific dialogue, there are other examples spread throughout the tooling that should not require individual Ideas to tackle.
It would be nice to have the option to sort the tables alphabetically in the MDW.
Hi, It would be highly beneficial to have the ability to use variables in the TimeXtender Portal. I see a lot of potential here, but the most immediate advantage that comes to mind is as a solution for expiring or changing App registrations/client secrets. By creating a variable for the client secret and applying it across all Semantic Layer instances, you could easily update the client secret in a single location when it's about to expire.If anyone has other examples of how variables could be useful in the portal, feel free to share them below!Regards,Devin
Instead of having to remove Work Items individually, I would like an option to remove all the Work Items at once, for example by pressing a button in the window below.
As of version 6745 it is possible to execute multiple Deliver instances at the same time on the same server. This feature is great as you don’t want to process 30+ semantic models one by one. There are still enhancements to be made the parallelism functionality:It should also be possible to process multiple DWH/Prepare instances at the same time. We have about 8 production Prepare instances that sometimes have to wait for each other to be ready. For using parallelism, all SSL execution packages should be in the same Job. When you’re using Exmon for process orchestration, it is nice to see the status of each individual semantic model on you process map. When you put all SSLs into one Job, this is not possible anymore. You will see a red light if just 1 out of 30 models failed to execute, which gives business users wrong/too few detailed information (and causes unnecessary panic). Have control over the order of execution. Some SSLs need to process first, as the business are waiting for them to be ready each morning. Others can run later. Hence it is important to set priorities and have control over which SSLs will execute first.
It is currently not possible to see what has been improved once a TimeXtender data source provider can be updated from the TX Portal. It would be nice to see what has been changed, especially when we’re waiting for bug fixes.
With the timextender excel datasource connection it is possible to combine several workmaps and or files into a single table in timextender.For an sql datasource a similar feature is not available in the integration version of timextender. However using business units in the classic version brings this possibility by the use of additional connections.Could this excel connection feature be developed for either an odbc/mysql/mssql data connection by either combining tables with similar name but different scheme (mysql), similar name but different database (mssql)? Provided the user of this connection has read rights to all needed databases from this instance/server.It would be an even greater feature if the schemes or databases could be selected with the help or use of a data management table, so we could add or remove databases at a central point.
It would be very useful to have the possibility to do it directly in TX.It must be taken into account that to hide the table so that it cannot be seen from PBI it must be set:IsHidden = trueIsPrivate = trueIn addition, it is necessary to hide all table measures and columns to ensure that PBI does not see the table.
The typical use case is to control the unit of measure symbol.What I do is to put in the measure code the formatting expression as a comment (I use a DAX snippet) and then I apply the property using a Tabular Editor script.I think this option should be implemented directly in TX.
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
When a dimension table has a lot of attributes it’s crazy to assing the folder to them:It would be better to be able to create and manage the folders directly in the table tree:
I would suggest to add a search bar for adding fields from the ODX to the DSA.(I think a search is far better dan sorting the fields)
I was today years old when I found out that this warning message:Only appears when the table you insert the data from (Y) is lower in the Data Area table list than the table the data is inserted to (X). So this warning only applies when the data area or parts of it are executed without Managed Execution enabled, which is almost never the case.This warning has caused quite a lot of confusion at some customers, thinking they had to split tables into two because of this warning.So, the idea is quite simple, please change the warning text to something like:“When executed without Managed Execution, the table X is executed before the table Y.” Or similar.
Quite often, source systems have their own ValidFrom / ValidTo fields. The lookups then need to take time into account or need a check against a fixed value.It would be more efficient to be able to specify this once at the relation level and automatically reuse for each lookup.Currently, you can only create equal joins in a relation and then need to specify the Greater than or equal / less than side in each lookup. But if you do this, the original equal join in the lookup is removed and needs to be created again.
Hi All,(bigger) Organisations will have their IT department run updates or upgrades or installs e.d. trough silent installs. This is perfect for them as they can have this run on schedules or independently from the intervention of people. With this I mean that no human interaction is needed in these processes.At the moment this cannot be done TX. When a new install or upgrade has been done you have to log in for the software (mainly the ODX) to work (again). This is a human intervention and this is unwanted.Can we make it so that this is no longer nessicary? That service accounts can be added in the portal so that when they make a connection it goes straight trough or that you can save / back up the condig file and whenever an update / upgrade has been made the config file gets read and logging in is not required?
I think that it’s necessary and allow us to use the original field’s description or update it in the destination
In an old idea 5 years back from Bas Hopstaken, where he suggest to Add unpivot featureI would like to add to this to add the Pivot function to. So you can do it both ways without having to create a view.
Power BI has some nice handling for date/time fields where you can separate the formatting from the content. I.e. a datetime can be presented as yyyy while still properly populating charts.The Edit Semantic Field functionality allows you to choose a number of formats but misses a few very useful ones: It would be great if the following options could be added:mmm mmmm mmm-yy mmm-yyyy yyyyEven better if users can specifiy the formatting strings themselves. Whilst the functionality specifies Tabular-only, I assume it also works for XMLA endpoints
In the more recent versions of TX SAAS, it is possible to execute Deliver instances (SSL’s) in parallel. This only works if these execution packages are put together into one Job. When we start multiple jobs with one Deliver instance execution package in each job, the instances still get executed one by one. This also is the case when we execute them from within Exmon, even when we have the Exmon step set to parallel.
The Query tool displays data depending on the data type. While this makes some values easy to interpret, like bit values being displayed as a checkmark, I've found that time values are hidden from datetime fields.See the Query tool result below. Time is not displayed for the field itself nor when casting as datetime, but casting the time alone does show the time is there. The same query in SSMS returns the time in all three fields, which is the result I would expect from the Query tool: The preview window also shows the time. (Changing the Date format here and then clicking through to the Query tool does not change how data is displayed in the Query tool). My suggestion would be to either match the Query tool date format to the date type of the fields, or create a way to customize the date format in the Query tool like in the preview pane.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.