Skip to main content

Filtering on endpoint name using deliver instance variables


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Use deliver instance endpoint name variable, in combination with data selection rules, to perform different data selections for different endpoints in the same deliver instance. This way, each department can get their own endpoint with a subset of data relevant to their division. This can help improve load performance, report performance and help manage costs by keeping individual models smaller. This also helps avoid creating multiple deliver instances for different departments.

How to filter use data selection rules for specific endpoints

  1. Create a Deliver instance with multiple endpoints
  2. Close all instances in TimeXtender Data Integration and then open the Deliver instance in TimeXtender Data Integration and click Tools > Instance Variables. Then click Add, and add an instance variable of type Destination Scope, setting the Value Filter to Endpoint and setting the Value to Name. Then click OK and close.
  3. Right-click the table you would like to create filter on and select Add Data Selection Rule. Then click on the table name in the right-hand Data Selection rule pane, and ensure Custom is selected as the operator and then click Add.
  4. Add the data selection rule. In my case I have 3 records in my table and would like Semantic DEV endpoint to only show the first record, Semantic QA endpoint to only show the second record and Semantic PROD to only show the third record. Therefore I add 3 separate custom data selection rules.
  5. Drag the column you would like to filter on from the right, and enter the value to filter on. Also, drag in the Endpoint Name instance variable, and enter the name of the endpoint you would like to filter on.
  6. Repeat this process for the other endpoints
  7. Then deploy and execute the deliver instance

The outcome

The end result is 3 endpoints, in my case SSAS tabular models, that each contain a subset of data from the deliver instance.

Did this topic help you find an answer to your question?

3 replies

rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Problem Solver
  • 222 replies
  • March 12, 2025

@Christian Hauggaard 

It’s seems complicated to setup, because if our model has several tables we must include the selection rule in each one and the first problem that we will find it’s that the selection field perphaps it’s not there.

 


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

@rvgfox if you have an idea on how to simplify please submit a product idea. which selection field is not there? please submit a support ticket with a video recording of the issue


rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Problem Solver
  • 222 replies
  • March 12, 2025

@Christian Hauggaard Perphaps it would be a solution setup the selection rule in a table and use the relationships to filter the rest of tables.

Related to the missing fields:

Using filters in SSL's tables


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings