Build better products with our product team
Whenever I write Custom transformations / inserts / stored procedures / etc. I miss being able to see the types of the fields I can drag in from the right. I find myself frequently going back to the main tree (where I can see the types by setting the option from View menu). Could setting Data Types in the View menu also make them available in other places?
When I import from an Excel file, why does TX automatically sort the column names alphabetically? Having the option to import the columns in their original order would be great. Sometimes there is a rationale to the column ordering.
Can you create an option to update ALL data sources by right clicking on "Data Sources" in the tree, rather than having to right click on each individual source?
Hi, we're using different schema's to setup security on our data warehouse (one of them is used to contain all objects we use for Reporting Services). Since we use stored procedures and user defined functions in SSRS we need the option to set execute permissions as well. Since TimeXtender only sets select permissions, we have to use a post script to set the execute permission, but there isn't an option to do so on schema level. So, 2 options : - add the possibility to set execute permissions when setting security on role level or - add pre- and post deploy functionality on all objects (including schema) Is it possible to add these features ?
Many CData adapters have the same properties. During testing we're switching a lot between OData/JSON/Rest adapters because it's hard to know the difference. Each time we switch, all properties are erased while they are still valid. Example properties that remain valid: URI, Username, Password, OAuth Version, OAuth access token, OAuth access token url, OAuth client secret, OAuth client id, ...
Add an option to set the checkmark 'Send to execution queue' default turned on.
Hello, I miss the feature to create a project perspective based on a database schema. Meaning all tables in the database schema will automatically be part of the perspective. Normally I create a database schema for each data source. Ben when I want to add a project perspective, I need to manually add all tables of this source to the perspective.
Please include the possibility to add row filters to tabular roles. Currently we have to add this manually after each deployment. Example powershell code: [Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices") # SSAS server name variable$SSASServerName = ".................." # Connect$SSASServer = New-Object Microsoft.AnalysisServices.Server$SSASServer.Connect($SSASServerName) # Navigate$database = $SSASServer.Databases.GetByName(".............")$role = $database.Model.Roles.Item("Sales") # Create TablePermission$tableName = "CostCenter" $perm = $role.TablePermissions[$tableName]if (-not $perm) { $perm = New-Object Microsoft.AnalysisServices.Tabular.TablePermission $perm.Table = $perm.Model.Tables[$tableName] $role.TablePermissions.Add( $perm )}$filter = $tableName + '[Department] = "Sales"';$perm.FilterExpression = $filter # Save$database.Model.SaveChanges()
It would be nice that some 'standard' Data Selection Rule operators are added. Like: - last 'x' years - last 'x' months - last 'x' quarters - last 'x' weeks - last 'x' days And we are able to add the date which is the Data Selection Rule is based on. e.g. ModifiedDate. Or maybe we can use something like 'Data Selection Rule Snippets' . And we can apply them on tables.
Currently it seems intermediate measures cannot be hidden which is really confusing for end users.
Hi, in order to provide a better service with a better data quality could be necessary for our project to modify the name and behaviour of system field. The basic functionality are very useful but since they are field which are currently visualizable on all the created tables could be very interesting if the possibility of customization, with the necessary caution, could be available. Here a list of features which could be great to have available: 1) The renaming as i.e from DW_SourceCode to XXXX_XXX or whatever; 2) The possibility of changing the current showed value such as for the mentioned field : i.e in DW_SourceCode change the "Aggregate" value to "Anything"; 3) The possibility of Using the field somehow, for example with relationship or transformations. I hope that everybody reading this post will keep adding some features by post. The System Field could be a great resource, but they really need to be customizable. Thank you very much for your effort, Kind Regards, Luigi Vecchione
Add an option to guard an additional data source when using Template data source. I have some projects where I miss this feature. Customers of us have financial data sources. Every financial administration is in a separate database, but they have an identical database structure. So I use the Template data source. But some financial administrations are not used anymore, so I want to guard these sources. But it is not possible to guard a data source in the additional connections.
To do this, now I have to create empty custom tables with a script attached. This just clutters the database with unnecessary tables.
The 'Reverse Data Warehouse' feature gives you the possibility to incorporate an existing database, including primary keys, constraints and more. However, after reverse engineering the database, you get the error that the table (valid) already exists and is not created by Discovery Hub. Although, pre- or post-fixing the valid table could offer a solution and simply overwriting the existing one is dangerous, I would like the option to overwrite existing tables while using the Reverse functionality.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK