Build better products with our product team
Some features have been added recently to automatically add the joins necessary for handling SCD Type 2 lookups from a History Table. I'd like to suggest another enhancement which would save a ton of time and manual clicking when we're adding Surrogate Keys to fact tables. Dragging and dropping DW_ID from a history table to a fact table is easy. But the process of adding the Fixed transformation for a -1 "Unknown Bucket" requires a lot of clicks, is error prone, and is something I despise doing. I'd like to suggest the following enhancement to the new dialog that appears when dragging a field from a history enabled table. Note that this option should only be available if dragging DW_ID. A simple checkbox to add the surrogate key "unknown bucket" transform fixed transformation and also add the Is Empty condition: There have been several times where developers have clicked on the wrong field for the condition, or forget to add the condition, so this would be a great help. Also, try adding the transform and the condition 25 times for 10 fact tables. Your mousing hand will quickly agree with my suggestion. I promise!
I had a request come from a customer today which seems like a good idea. They have to maintain strict SOX controls, so knowing what version was deployed, by who, and when are important pieces of information their auditors need to know.Currently, when a project is transferred between environments, there isn't any notation in the project version notes.It would be very useful to simply add the information displayed after a successful transfer to the target environment's new version created by the transfer: So, in this case version 69 was created in PROD. It would be very nice if the information circled above was entered into version 69's notes. Otherwise my SOX compliant customer will need to maintain manual logs of transfers.
Enabling the "Show System Control Fields" in project settings will not make system control fields visible for existing table in the project. The tooltip does indicate that it " will automatically be added to new tables...". However, I think it would be useful to add the option to show system control fields retroactively, so you don't have to enable them for each existing table object manually. Thanks
Please add the following new features... 1. When selecting multiple text file as a data source, please add the option to import only the latest file into the warehouse rather than all files, based on the timestamp of the individual files. For example, if I have Aging20180401.csv and Aging20180402.csv in the same directory, I would like to be able to import only the "02" version as it is the newest one in the directory. 2. Please allow for multiple files to be in a directory, and have the option to load those files into the warehouse in chronological order. For example, if I have Aging20180401.csv and Aging20180402.csv in the same directory, I would like to be able to import both files but make sure they come into the warehouse in a selectable order (oldest first, newest first, alphabetically, etc.). Thanks.
Hi It would be great if security was redeployed after a table is deployed. At the moment we may secure a table but when we deploy the table the security is dropped when the table is recreated and we have to then remember to redeploy security other wise user are not able to view the data thanks
Being able to convert a business unit to a data warehouse within Timextender would save a lot of time if a customer want's to adapt to a newer project structure with an ODX database. Currently it requires re-doing all transformations, lookups and logic for the entire staging database.
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
In many transformations you need a reference to the "current field". Example a tranform in [Field A] could be: coalesce(nullif( [Field A], N''), N'Unknown') In this case, it would be a huge improvement of we could something like the following instead of having to assign a parameter. Especially when working with SQL snippets it would greatly improve usability as it allows drop-in snippets that don't need parameterization. coalesce(nullif( [CURRENT_FIELD], N''), N'Unknown') It should be noted that in the case of a self-reference, having an actual parameter has little benefit anyway as a self reference has no lineage impact
It would be nice to set the data export as a global database since we are using test data and production data. Every time we transfer from test environment to production environment we have to change the paths of the data exports manually to our production file server name.
It would be ideal if we could use differential deployment in the semantic layer, particularly in SSAS Tabular, or at least choose which table I want to deploy, as opposed to deploying the whole model. If I make a change to the DAX of a single measure of a 5 gb tabular model, it is less than ideal to then deploy the entire database and process full, just to see the effect of the DAX measure in a front end tool. Developing SSAS tabular seems to be quicker and easier in VS because of this feature.
Hi, Some of our customers want to setup 2 ODX Servers (1 for dev and 1 for test and production). On the Dev ODX Server we would like to connect to development-db-sources. So, it would be very handy if we could automatically swap between the 2 ODX Servers using the multi-environment setup of Discovery Hub when pushing a project from dev to test / prod. Best regards, Peter
Already asked by Peter Jensen with 9 upvotes in 2017. No comments from any TX Employees so far.So even today I am forced to modify the cleansing procedure and add my own logging...It would nice to be able to have an option per table by which you can enable extended data cleansing logging.This would log the start and end date of each step in this procedure to a dedicated log table. (Have to do this when a proc starts throwing timeouts or takes a long time all of sudden)I think this takes about 15 minutes to implement into your code base.At the start of the proc you check if the logging table exists else you create one.Before each step in the proc you store the datetime in a variable.At the end of each step you write a record to the log table and reset the start time again as such: IF OBJECT_ID(N'etl.HAWEmployeesPlanningMT_DataCleansingLog', N'U') IS NULL AND @enableExtendedLogging = 1BEGINCREATE TABLE etl.HAWEmployeesPlanningMT_DataCleansingLog (Id BIGINT IDENTITY(1,1) NOT NULL,Version BIGINT NOT NULL,Step NVARCHAR(1000) NOT NULL,DateTimeStart DateTime,DateTimeStop DateTime,CONSTRAINT [PK_bb573581_2114_4b3e_b1bd_042488deac10] PRIMARY KEY CLUSTERED (Id ASC) ) ENDSET @DateTimeStart = GETDATE()SET @step = 'Keep field values up-to-date: detect lookup value changes'-- Keep field values up-to-date: detect lookup value changes/* TX generated SQL */IF @enableExtendedLogging = 1INSERT INTO etl.HAWEmployeesPlanningMT_DataCleansingLog(version, Step, DateTimeStart, DateTimeStop) VALUES(@version, @step, @DateTimeStart , GETDATE())SET @DateTimeStart = GETDATE()SET @step = 'Update conditional lookup fields (Many lookups, Take the first value):''CustomerHQId'',''CustomerCode1'',''IsTardyCancellation'',''IsExaminationsFinished'',''DateExamination'',''ExaminationPart1ResearchCode'',''MedicalExaminationCode'',''ExaminationTypeCode'',''MedicalExamination_IsPeriodical'',''CategoryCode'',''SubmissionCategory'',''DateInFunction'',''DateOutService'',''PlanningTimeCell_Time'',''PlanningEntityDate'''-- Update conditional lookup fields (Many lookups, Take the first value):/* TX generated SQL */IF @enableExtendedLogging = 1INSERT INTO etl.HAWEmployeesPlanningMT_DataCleansingLog(version, Step, DateTimeStart, DateTimeStop) VALUES(@version, @step, @DateTimeStart , GETDATE()) https://support.timextender.com/hc/en-us/community/posts/115011859306-Logging-during-Cleansing-Stored-Procedure
Since SQL Server 2019 it is now possible to create a Many-to-Many relationship in SSAS Tabular. That cardinality option is currently not available in Discovery Hub.
Hi, At the moment the ODX server is quite stand-alone. There is no way to execute ODX task as part of package execution. project execution will carry on regardless if the odx task has successfully executed or not. One possible solution would be to add all ODX task as 'External Executables' In this way you can add the ODX task to the project's execution module
When setting up execution packages it could be very useful to ignore/allow individual steps (objects, other execution packages, perspectives) to fail without failing the execution. The step would fail and continue with the next one.
When dragging a table from the ODX to a DW using the secondary mouse button, we are able to use a field selection dialogue to choose the specific fields we would like to add to the new DW table. However, if I have an existing table, there is not an easy way to add just one or two fields as needed. Instead I have to synchronize the ODX table to the DW table, which will add all the remaining fields. Then, I need to delete the extra fields which are not needed. In some cases, this could be 150+ fields! Ideally, I'd LOVE to see the traditional Data Selection pane being used here. That is an outstanding feature which is sorely missed in ODX projects. Especially the ability to preview the data and select fields right from that preview. I understand that doesn't really fit with how the ODX functions, but the ability to select individual fields to add to an existing table is a must have.
Currently, we have 3 parameters which can be used in the Notification email Subject: Execution packages which are scheduled normally have the environment name in them, but sometimes we need to manually run a more generic execution package in an environment... for instance, to force a full load. In that scenario, it would be helpful to be able to use the %ENVIRONMENT% project variable in the notification. Our only alternative is to setup multiple copies of execution packages right now.
In SSAS tabular there is an option to import a JSON file for multi-language support. So we have a possibility to support our customers with a dutch or English Cube. You can read more about this option: https://www.mssqltips.com/sqlservertip/4547/multilanguage-support-for-ssas-tabular-models/ Is there such solution in TimeXtender where we can set a second language?
Not really a feature for Discovery Hub, but it would be nice that we can do an official TimeXtender exam and earn a certificate.
Recently I found out that the TimeXtender implementation of the Qlik endpoint bypasses the Qlik Load balancing. In the ideal situation the following workflow would happen: In TX end-point we add the hostname of the Qlik Central node When the TX endpoint is exectuted, TX calls the central node Central node distributes the task to one of the available nodes for execution Currently however, the hostname that is called will always be the node that executes. This is even the case when the central node is set to Master only and therefore should not be performing any reload tasks whatsoever. I suspect this happens because TimeXtender calls the app:Reload endpoint in Qlik. Perhaps it would be possible to have the TX deploy create a task in Qlik that is then called on execute using the task:Start API endpoint. In any case, TimeXtender should work with Qlik in such a way that it allows the load balancing of Qlik to do it's job in order to facilitate bigger enterprise size architectures.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.