Build better products with our product team
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.
The current design in TX v21 doesn’t allow more than one job to run at a time per execution service. In many environments, either with multiple instances or with data sources that require frequent updates this is quite a limitation as jobs will constantly be added to a queue with the waiting state. There shouldn’t necessarily be a need to have multiple VM’s with a separate execution engine just be able to run jobs simultaneously.When using exMon for orchestration and as a tool for business user to run executions on-demand it can also give the user a false pretence that the job has started when it is actually waiting in queue. If it has to wait too long the exMon package will get a timeout failure when there is no failure. The package will eventually start and finish successfully but the user will not know about it.This limit also makes the current concurrency options for the execution packages quite useless.
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
HelloI see two tickets for it not being possible to have multiple jobs running at the same time. The answer was that it is not posibble within one execution service (only for ssl now).With more and more organisations moving to more real time analysis, timextender is the ideal tool to have multiple job schedules during the day (even with extract data on demand to have it combined with data ingestion). But then you are limited, that for one instance, it can only have one job running and other jobs have to wait. I just don’t understand how that matches with the filosofy of the tool?I hope that based on the related tickets a solution to this issue is one of high priority.The wo tickets: If not high on the priority list can you please let me know how we can solve this in the meantime (of course without using the development or acceptance execution service for production jobs).For example : one job runs each hour and one each two hours. When the 2-hour job is running the job which needs to run each hour will not run while the two hour job is busy (and runs for an hour and a half). I don’t want a technical limit on these times, it needs to be based on the business needs.
In custom table inserts, views, custom transformations and custom measures (in deliver instances) we create parameters that point to fields or tables, to create dependencies, lineage and catch column or table renaming.Currently, we have to drag and drop these parameters every time. It would be very nice if the editor had a ‘detect parameters’ button that automatically creates parameters based on the code written.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.