Question

Kyle C on Fri, 09 Jun 2017 15:23:39


Using 1200 or 1400 Azure Analysis Services model. This error is occurring on role edits via the VS 2017 analysis services add on. Worked fine in VS 2015. Using Azure Analysis Services as Workspace server as well. Again the project and cube worked fine with VS2015. This is occurring when testing against the VS2017 designer.

 

Kyle Clubb


Sponsored



Replies

BillAnton on Thu, 21 Sep 2017 20:33:58


perhaps this has been fixed in the latest version of the Analysis Services extension for VS17?