Build better products with our product team
in addition to this post: https://support.timextender.com/hc/en-us/community/posts/360015331763-Make-repository-choice-environment-based-not-user-based Also the command-line executable should be able to define the correct environment. Now you can only select project and package. Which is not enough if you have more than 1 environment on a single machine.
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.
In stead of using a fixed date with the Pick Date button I would be very good to have an option that evaluates a date with the current date (GETDATE()) every time the table executes.
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 ?
If you setup multiple environments on the same machine, you'll run into the issue that a config file that holds the connection to the repository, is stored in the App_Data folder of the user running the service and can have only 1 version. So 2 environments on the same machine need 2 services, run by different service accounts. With that we can run into trouble with customers who don't have accounts for each environment If that's so, wouldn't it be better to make the config file environment-based instead of user-based? As it is setup now we cannot use 1 serviceaccount to run both environments on the same machine, because of that file. I think that it's more logical that you can choose the repository in the Environment Properties screen, so it becomes user-independent: Is this something to consider for a future release?
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, ...
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.
There are companies that manage their metadata such as table and field naming conventions in external systems. In AX, an example could be that the field DATAAREAID should be called Company in the MDW. I'm after a feature where we can link to or import a metadata mapping table that for a given data source can map the data source field names to whatever the metadata mapping table contains (e.g. DATAAREAID -> Company). The feature could be implemented in a three stage solution where the ODX contains the simple-loaded source data as named in the source system (DATAAREAID) whereas the DSA could then contain the mapped name (Company). Such mappings in DSA should of course also cater for table name mapping. (It could also be implemented in a two stage solution in the MDW).
In light of GDPR it would be nice to have an 'anonymization' option on field level. In that way we can choose per field, per layer (either datasource, or MDW, or somewhere in between) if the data contained should be anonymous. That field could then be visually represented differently throughout the project to show it has been anonymized.
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.
It would be useful to have the preview data window always display the "approximate" row count of the table on open by querying it from the dmv (dm_db_partition_stats) without having to have to use the "Count rows" which can be quite heavy on bigger tables.
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.
HiWhen you have a lot of cubes and dimensions, it can be a big task to minimize the menu, to get what you want. See video.https://ilos.video/phk2zW I would like it to be totally opposite, so it is minimized to cubes and dimension at startup instead. Like this.
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.
A Gant Chart / overview of all executing packages including scheduled start time, overlap in concurrent running packages and execution times.This will help us to plan the executing packages because we have a total overview of all packages instead of clicking each package one by one and see the execution log details or the schedule.
When you drag one field (Invoices.InvoiceID) on top of a second field (InvoiceLines.InvoiceID) you get the message "Do you want to create the relation?" Is it possible to extend this text with which fields you want to connect? Do you want to create the relation on Invoice.InvoiceID and InvoiceLines.InvoiceID This will give you an extra check that you dropped the first field on the right second field.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.