I have built a data model in Timextender and with a Power Bi endpoint.
In the Power Bi report I see certain fields summarized by ‘Sum’. In the SSL layer I only get the option to change te name and I am missing the 'Summarize by’ and the ‘Sort by’ option.
What am I doing wrong?
Page 1 / 1
@boyclaesen which TimeXtender version are you using?
@Christian Hauggaard I am using Timextender 6284.1
@boyclaesen thanks for confirming. Is this the same for all fields in the table ERP_dim_address_customers (e.g. are you also missing the options for credit_limit)? What about fields in other tables? And how about fields in other SSL instances?
@Christian Hauggaard thank you for your reply. None of the fields show more options. Neither for ‘credit_limit’ or other tables.
This is the only SSL instance that can I use. The weird thing is that a couple of weeks ago I had the option to change the 'summarize by’ for example. I dont know what could be the cause of this change in settings. Any other ideas of checks that I can do?
@boyclaesen
It is probably due to the endpoint type not supporting it. Which one are you currently using?
I changed mine to look like this.
Then the fieilds looked like this when I clicked edit on them.
However, if I change it so I can see Tabular as well I get all these options.
Hi @Thomas Lind,
I am using the PowerBi Premium endpoint.
When switching to the Tabular endpoint I do get all the options.
Does this mean it is nog available to edit the semantic fields in combination with the PowerBi endpoint? Also, I have some tables in the DWH set to 'simple’. Could that have an effect?
@boyclaesen
That seems unlikely, but I do not know for sure.
A workaround could be to check the Tabular option to have the options at least.
I will see if I can work out if that is the case.
Hi Thomas, it seems to work when I set check the boxes for Tabular and PowerBi. I wouldn't expect this because I only use the ‘PowerBi Premiun endpoint’. Perhaps a bug on the TimeXtender side. For now I can proceed:).
Hi @boyclaesen
Yeah, it seems like it is a bug. I made an internal case about it, but for now your suggestion is my workaround as well.