Deliver

I am having issues with decimal numbers in my Power BI model created with TimeXtender XMLA endpoint (version 7026.1).No matter the precision of my datatype on SQL server it seems like all values are forced into a rounded 4 decimal size. Is there a setting hiding somewhere to prevent this behavior? Below are examples or test data to demonstrate the behavior. Inspecting the model with tabular editor it seems all decimal fields are stored as fixed decimal rather than the expected double Test data Result in Power BI

Hello, I am trying to setup an endpoint to PowerBI Premium in version 20 (20.10.58) The connection is setup as below, and it tests OK (See pic). When I Deploy I get the error: Failed to save modifications to the server. Error returned: 'Either the database with the ID of 'TXFinance1' does not exist in the server with the ID of 'host002_datasets-231', or the user does not have permissions to access the object. The Semantic model is created fine in PowerBI, but nothing inside of it. Is there a setting I am missing? The stange thing is that it appears to work for a colleague in the same workspace using the same app credentials, but not on my machine Many thanks, Tim

Hi, I am trying yo apply the new integrated Deliver Instance variable, but get an error when deploying the instance. When deleting the variable again, de depoyment and execution succeeds. I already tried the following: Synchronizing de Deliver instance Refreshing the environment Reopening TX Deleting and recreating the variable with a different name Trying the Fixed variable instance (which gives me the same issue) Any suggestions? Kinds regards, Devin

Apologies for vague subject but I couldn't come up with anything better. We have an Semantic Model in TimeXtender 20.10.55.64 setup with a Role, and a Row level security setup. Those two are normally ‘linked’ as required, and described in articles as Deliver Instance Model-Level and Row-Level Security | Community We've just noticed while delivering a new PowerBi app to our users that this link disappeared somewhere between deploys, giving all users read-access to all data (oops). Is there any documented reasons why this would happen? Or better yet, is there a method for RLS that would default to users not having access to ANY data at all rather than everything if this happens? Eg explicitly grant users access to data, as opposed to explicitly deny access. Thanks for any insights.

I have a need to calculate a measure which would reflect the revenue growth over the year on different categories in percentage. Currently i have a custom measure in semantic layer with following formula: Revenue Growth = ([Sales Revenue] / [Sales Revenue LY]) - 1 The categories in dimension which i have are Cat1, Cat2 (no data in the fact), Cat3. However if i try to show this on excel, it includes the Cat2 which has no records in the fact table, and also gives me an “empty” category which, i assume, is “summarization” like this: Is there any way to make sure that the empty row and the category with no data in the fact would not appear?

Good Day, I have setup a Perspective in TimeXtender (v20.10.39.64) and it includes 3 tables and a Tabular cube. When I go to deploy this perspective from DEV to QA, the tables are listed in the deploy tasks but not the cube. I tried the following fix but this did not resolve the issue: Remove Tabular cube from perspective Save TX Project Re-add Tabular cube to Perspective Save TX Project Deploy TX Project Multi Environment Transfer Has anyone ever run into this issue before? I am going to try to add a new perspective to see if this resolves the issue but it worries me for promotes going forward that objects maybe missing on my deployment/promotes. Kerry

Dear Sir, In some Deliver Instances Semantic Models we can not use the right click table option Go to Source Object. It is greyed out. So TX user A created the Deliver Instance SSL and populated it with tables.But TX user B can not use the right click table option Go to Source Object, it is greyed out. But both users have Grand Access to the Deliver Instance config in the Portal. The data lineage is working fine. What am I overlooking. Some security setting ? Somebody has an idea ? Thanks in advance. Regards, Arthur

During deployment of a tabular endpoint in 20.10.44.64 the error listed below occurs. The same error appears for multiple people in my organization, also in TimeXtender 6346.1 The error only occurs when deploying, not when executing. In SQL Server Management Studio (Analysis Server), the executed tables do occur, but remain empty. Naturally, connecting to the endpoint in Power BI is not possible. Error: Failed to save modifications to the server. Error returned: 'The following system error occurred: A device attached to the system is not functioning. The following system error occurred: A device attached to the system is not functioning. The following system error occurred: A device attached to the system is not functioning. The following system error occurred: A device attached to the system is not functioning. The following system error occurred: A device attached to the system is not functioning. The following system error occurred: A device attached to the system is not functioning

I would like to test this new functionality. I’ve read: https://support.timextender.com/deliver-109/rest-api-endpoint-1808?tid=1808&fid=109 But I can't understand how to send the tables from the SSL instance to the target DB using this technique. Can you explain me with a clearer example?

Hi, which kinds of security are available for REST Endpoints and how should they be implemented? Can you directly use row-level security in the Deliver instance?

Hi I originally set up my semantic layer data models with dynamic RLS, using rules defined in a table in TX, but then switched to using a setup with manual RLS. I then removed the dynamic tables from the semantic layer and preceding data pipelines, but when I redeploy my semantic models the removed security table reappears. Any advice? TX Version: 6745.1

Good Day We are experiencing an issue with a TX Project’s Semantic Layer Exports. For one user’s desktop install of TX they are getting the following red X’s over the exports. I have tried to re-download the Custom Components and installed the SQL and File Export items. Only the SQL Exports had the red X removed. The file exports still have them after installing the custom component. Any ideas why this is still not working?

I have a client that works extensively with multiple SAAS applications and are looking to use their MDW as a central distribution hub to integrate the various SAAS applications. So I am exploring the new Semantic Model REST API Endpoint and I need guidance on the Web Server setup and configuration. I have seen the community post created by Thomas Lind “REST API Endpoint” but these details are missing from this article. I want to use Azure web server. I assume that I need to create a Web App in Azure, but I am stumbling around in the dark here. Can anyone offer any advice, guidelines on how to setup a simple web server in Azure that I can configure for TX? This is just for testing and POC, not production use. Trying to get a sense of how it all works. There are too many options to consider, should I use Linux, Windows, install the database? So if someone could provide a guide for “Here is a cheap and cheerful Azure Web App” that with work with the TX Rest API Endpoint that would be awes

Hello, I am trying to get a better understanding of the workings of the REST API Endpoint we can add to a semantic model. Specifically what certain actions do withing the whole framework. I'll sketch my case below: We have configured and deployed a working API Endpoint that contains a table Currency_Rates (From_code, To_code, Date). The endpoint is called api-endpoint and the the webserver is called webserver-endpoint. We have everything working properly: so we can successfully make the following request: R1 = <URL>/api-endpoint/data/Currency_Rates?$Top=2&$OrderBy=Date desc. Now I change the name of the date column: Date → Curr_date. This means, I would now like to start using R2 = <URL>/api-endpoint/data/Currency_Rates?$Top=2&$OrderBy=Curr_date desc. Furthermore I would expect R1 to return with an error. Now please consider the following actions: Deploying the instance/endpoint (← nothing to deploy according to TX) Saving the instance (as the deployed version) Clicking the “request to

Hi Everyone, I have a question. We have a Tabular Endpoint set up in our TX Semantic Layer, and I would like to know what type of Tabular Endpoint Processing it uses by default: Process Full Process Data Process Recalc Process Add Process Clear Process Defrag Process Update Process Structure Process Default Additionally, is there a way to select the type of processing it should use? Thank you!

I configured a REST API endpoint. It woks as expected as long as I only add tables from my MDW to the endpoint. However, any views I add to the instance in TX are not visible through the API. They do not show up in the /swagger nor can I query data from them nor can I find any mention of then in the webserver configuration. Why is that?

I am currently testing RLS using a powerbi premium endpoint with the TX 6675.2 version. Normally we use dynamic RLS, but since this did not work, for now i tried a manual setup: I have added my user to a created Role Then i have set the security setup and the endpoint to the Role i created. The outcome in PowerBi Desktop when i connect to the PowerBI premium endpoint in the onelake datahun is that i don't see anything. No data at all. I would have expected that i would see the data for Bejo Andes Ltda. Is this the correct setup for RLS in a PowerBI endpoint or am i missing something?

I’ve detect that some dax code doesn’t works in PBI. Are there some guide abut this?

The DAX Snippets doesn’t works like the SQL Snippets. It doesn’t allow in the “Show Usage” section to change the snippet and change too the measures afected.

When promoting a Semantic Model (copy to instance), are the Roles and especially the users/groups within the role in the model also copied to the other environment? In legacy TX we were able to grant a role to different users/groups per environment, but in the new TX it seems to be the case that we have to change that after promoting?

Hi, In TimeXtender Portal under Data Estate → REST API web servers, the description suggest that you can install the web server as an Azure Web App. When you run the installer, it tells you that you need IIS and ASP.NET Core. This indicates an install procedure for running the REST Web Server on a VM. What is needed to set up the TX REST Web Server as an Azure Web App? Best, Erik

Hi, One of the improvements of the that is stated for this update it says the following for the tabular model. “We've improved the Tabular model generated by the Tabular semantic endpoint to have better efficiency and reduce the size of the model.” Could you elaborate a bit more how it is more efficient and how you reduced the size? For us the size is especially important, since we have a 16gb limit with our ssas. Could you elaborate if you changed the encoding hints, since I do not assume you are changing any datatypes or something like that. Or did you guys mean that the processing of the tabular model has been improved, and the size it takes during processing has been reduced? In any case, I wrote another question regarding Tabular model size, and DirectQuery mode. Maybe here the timextender team or anybody else can give guidelines / best practices to reduce the size of the Tabular model as much as possible.

Hi team, TimeXtender allows adding parameters from a different table to a custom field in a semantic data model (Qlik). The resulting syntax/qlik script combination is always broken. When using adding a custom field parameter from a different table, TimeXtender fully qualifies the Qlik syntax regardless of the settings. The resulting syntax on the Qlik side will no longer match the syntax in the views created by TimeXtender: Qualified setting: Fully qualified setting: The resulting Qlik Script: "Sales_Targets":LOAD"KPI", "Target", "DIM_Boekdatum.DayName" AS "Test";SQL SELECT"KPI", "Target"FROM "Test"."dbo"."Test QVD_SLQV"; But the view has the following syntax: CREATE VIEW [dbo].[Test QVD_SLQV]-- Copyright 2011 timeXtender a/s-- All rights reserved---- This code is made available exclusively as an integral part of-- timeXtender. You may not make any other use of it and-- you may not redistribute it without the written permission of-- timeXtender a/s. ASSELECT [KPI] AS [KPI] ,[Target] A

Hi everyone, I’m coming across some specific drawbacks of using the semantic models in TimeXtender in combination with PowerBI. I hope this is due to my lack of understanding or design choices and hoping it can be fixed. While working OT(A)P (DEV / TST / PRD) we have found that looking at the development environment with PowerBI is too much of a hassle, too many changes, wrong data, just too much development to keep up in the semantic models and PowerBI is not flexible when it comes to name changes etc. We decided to delete the semantic models from DEV and start building the model in TST. (For early data exploration we can still build the model in PowerBI itself on the MDW). In PowerBI we use the pipelines and we can connect TST-TST and PRD-PRD. But what would be even better is connect a PowerBI DEV workspace to TST, and the PowerBI TST and PRD workspaces to the PRD endpoint so that we can test the dashboard on production data, give it the green light and there is no risk of any differ

Dear Sir, Our customer has an issue for scheduled semanctic models. ODX and DWH instances run succesfully when scheduled, but the semantic models are not running.The semantic model is running successfully by hand, but when the package is automated in a scheduled setting the package execution fails. Execution overview Semantic Error semantic Hopefully you can shine a light on this issue. Our client is running TimeXtender version 6436.1. Regards, Arthur van RijnFourpoints