Build better products with our product team
Hi, Is it possible to enable Type II history on all fields in one setting, instead of having to manually enable each field?
The current implementation of the Replace transformation gives you two options:char replacement: type in the int value of an ascii code and have this replaced by a string string replacement: type in a string to be replaced with another stringThe interface for the character type replacement is very confusing, as most people will not realise you need to enter an ASCII code until the try to type a character and encounter an error. This type of replacement is apparently used to replace certain control characters - see also here: I would propose to change the function so you can enter ASCII / Binary / String literals to be replaced by ASCII / Binary / String literals. The REPLACE() function allows for binary input, you should be able to convert to and from ASCII or Unicode code points using SQL functions. Making it easier for users to define the transformation they want.
When you open a custom transformation for a field the window doesn’t show the complete field’s names: It would be nice that the default window shows them:
It would be necessary to validate the SQL syntax of the custom validations, because for example, if you write something like this: There is a missing parentasis at the end but you can display the table but you will get a cryptic error and you will waste a lot of time looking for the problem, checking the _T script.
It would be great to be able to publish the semantic layer to a PowerBI (premium) xmla endpoint. https://docs.microsoft.com/en-us/power-bi/admin/service-premium-connect-tools Why should you build this: Right now it is possible to publish the semantic layer to a SSAS tabular model (either in the cloud or on prem). We often use this as we love the fact that we manage RLS and security, as well as our models fully in Timextender. WE use SSAS in Azure when we want to share with users outside of our own organization. The new possibility to publish straight to powerbi premium, means that we can save a lot of cost in SSAS Azure. It adds to the value of TX, as the only interface that's necessary to publish data to PowerBi reports. It also seems to be quite a small change (from my perspective) It looks like you are already using XMLA to push the semantic layer to SSAS on azure so i hope this would be relatively simple, although i am happy to be corrected if that is not the case. finally: read this excellent blog post on why/how you would want to migrate to Premium here: https://data-marc.com/2020/06/16/migrate-analysis-services-models-to-power-bi-using-tabular-editor/ It features a few more links at the bottom that are also really valuable to read.
It would be nice to use the technic expained in:Using ChatGPTto add automaticaly the description about what the code does:
It seems ordinary SQL connectors cannot read bigints (in this case it’s the DW_Id in a TX-generated data warehouse stored in Synapse; it’s used as a data source) without a datatype override. It would be nice to have an Azure Synapse Dedicated Pool connector (or a fix that avoids the need for datatype overrides).
We have some snapshot tables in our DWH.In order to improve performance we’re using table partitions to delete old partitions in a fast way (a truncate is much faster than a delete)Most snapshots we use have a partition scheme for YM (YYYYMM), but we also need some on YW (YYYYWW). The first is by default available in TX, and works fine. But the YW is not available.Can’t this be added as a feature in TX ?Best regards,Peter
It would be very helpfull to have a change log of the ODX Synchronisation Task.So we can check :if all expected changes came through correctly if there are no unexpected changes (which we then can revert before doing a synchronise in the TimeXtender projects)This idea is triggered by the fact that we often have an issue with SharePoint Lists no longer being recognized correctly by the Cdata SharePoint connector (sometimes it skips a table or assigns it a new Id).Best regards,Peter
With this feature it will be possible to have the DB nativally documented.
I think that it would be good for all of us 😁
It’s necessary to view the names of the fields:
Is there a quicker way to delete table’s field distinct of one by one? I want to delete the fields that I’m not using but I’ve a lot of them.
If one script action its associate only to one table I think that it would be better put it on the table’ s tree, not in the general tree.
It would be nice to be able to synchonize, using the XMLA endpoint, the changes in the model in the service, made by external tools like Tabular Editor.
I am very excited that end-to-end scheduling has been implemented by means of ‘data on demand’ in the last update of TimeXtender (6024.1). I will definitely use this for hourly reloads. However, in some cases, especially when working on larger tables in the MDW, it would be convenient to have the option in the execution setup to NOT reload on demand. In that case, when for example deploying and executing a small change (e.g. change of a fieldname), this will not result in a full load all the way from the source.
Currently we have to deploy and execute the SSL into Power BI or Qlik Sense so that we can view our data model. It would be an improvement and time saving if we can analyze and validate the created model in SSL already in TimeXtender, like shown below.
Hi, in the new ODX Server (20.10) there is the new Data Source Explorer.It would be nice if I could search for missing (not enabled) options (e.g. show all tables without primary key).This can be done by having 3-state checkboxes instead of 2-state (where the 'not checked' currently means you don't want to make a selection for this option. I think it should be like this : - checked : search for objects with this option enabled - unchecked : search for objects with this option disabled (or not implemented - e.g. no primary key defined) - 3rd state : no selection on this option BR, Peter
It would be useful to be able to export the results of query tool to excel or CSV files
It would be useful if it was possible to add Years or months ahead when creating a date table. Years ahead is particularly useful when working with financial data. Days ahead will always produce a number of days into a superfluous year.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.