Deliver

The use of PBI semantic models require to use XMLA endpoint, that’s mean that we need a Power Bi PPU license. That it’s ok.The question it’s why not use the deployment pipelines feature in PBI PPU?The principal problem that I found it’s that it’s not possible to parametrize the data source conections to use correctly this feature.Somebody has experience in this topic?

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?

Hi, We've setup a REST API web server according to the manual. On the resulting endpoints fieldnames always seem to start lowercase. The original fieldnames in the deliver instance start with a uppercase letter. Now, I know that there should be a way to edit this in the configuration of the web server.Is this something we can edit ourselves? I've tried looking up directions, but web servers are not my expertise and I am unsure if the source code for the web servers is available locally or only in the cloud repository? Vilsen, Luuk Bouman

In the new version 7257.1 What’s mean this symbol in some tables and fields? 

Hi TX Support, We're encountering a strange issue. We've setup an deliver instance of the REST API endpoint type. The model contains a dimension table. In the MDW layer this table contains 7844 records. Now when we pull the data from the REST endpoint we get 7844 as well, however the content is incorrect. Instead of the 7844 individual records we get 6974 records, 870 of those are duplicated and consequently 870 other records are missing. Example:DIM_Location TableLocation, Code, DW_Id Original MDW data LocationA, 123, 1LocationB, 345, 2LocationC, 678, 3 REST dataLocationA, 123, 1LocationB, 345, 2LocationB, 345, 2Missing Record in the REST dataLocationC, 678, 3Now I did tried everything I could think of in terms of troubleshooting. Everything is deployed, executed, refreshed and running. Going through the data I made an important observation. The set that is duplicated all are records that reside on the first page. They are then duplicated across the remaining pages. See the screenshot

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 | CommunityWe'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 TransferHas 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.1The 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 functio

I would like to test this new functionality.I’ve read: https://support.timextender.com/deliver-109/rest-api-endpoint-1808?tid=1808&fid=109But 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? 

HiI 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 DayWe 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 awesome!

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) Clickin

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 DefaultAdditionally, is there a way to select the type of processing it should use?Thank you!

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?