September 28, 2017 at 2:29 pm
I'm working with a tabular model in SSDT, just wanting to filter a currency column > $0
The only filter options I have are "is equal to" or "is not equal to". I can choose other options in the drop down, but I only actually get these two options in the "Custom Filter" dialog.
Is this a bug, or am I missing something? The Data Type and Format of the column is set to Currency.
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01038
Installed Version: Professional
SQL Server Data Tools 14.0.61707.300
Microsoft SQL Server Data Tools
September 28, 2017 at 7:04 pm
Im not quite sure what you are doing or where you are doing it ?
Can you provide a screenshot with what you are trying to do ?
Is it just in the Tabular solution you are trying to filter a measure you have created ?
Or is it something different ?
September 29, 2017 at 2:10 pm
Never mind, I guess SSAS is just chock full of bugs and inconsistency. I can't even get cut and paste to work right.
Is there a stable release of SSDT with regards to SSAS tabular, or are they all full of these stupid glitches?
1. Deployment models don't retain settings.. If you have separate DEV/PROD deployment configs, if you change the Server on one, you change it on both.. That was a nice find, because I didn't realize that the first time I accidentally blew away production. ugh..
2. The janky DAX editor is horrible, if you make any mistakes, it throws the whole thing out, and sometimes pasting from notepad works, sometimes it doesn't. I guess I'll have to get my typing skills up since I can't paste nor correct mistakes. ugh.. I've heard this is fixed in the new version, but SSMS 17 was so buggy, I had to roll back to SSMS 2016, so I'm reluctant to go to tip of SSDT.. bleh..
3. The filter feature is there, but doesn't work. If you simply click the down-arrow next to the column name in the heading, you will be presented with a long list of filter options, none of with work except equals and not equals, all the others are just to confuse you. Of course, any filter you do apply will only crash Visual Studio or otherwise cause it to start behaving erratically. I advise not using the broken filtering, at least not in SSDT 2015..
I think that Microsoft needs to sell off their BI solution to another company that can make it work right, then they can buy them out again and have a decent product. It seems like that's been a successful business plan for Microsoft in the past, at least..
October 4, 2017 at 9:24 pm
DAX Studio maybe?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply