I think this is likely a niche issue only happening with some of our old views saved in a time where native views were different so adding this here in case anyone has the same issue.
When there is a .vue file containing “MEMBER_NAME” where it generates the row / column dimension as;
{[Measure].[Measure].[Measure1], [Measure].[Measure].[Measure2]}
PROPERTIES [Measure].[Measure].[MEMBER_NAME]
From something like;
7,Measure
270,0
274,MEMBER_NAME
275,129
{[Measure].[Measure].[Measure1], [Measure].[Measure].[Measure2]}
281,0
The extra PROPERTIES [Measure].[Measure].[MEMBER_NAME] isn’t generated in PAW or PAFE & creates an error in ARC. Awkwardly it also remains for the entire session so if you paste the fixed MDX it won’t work unless you specify a new alias or if you go into the dimension & pick an alias then remove it.
Once you know whats causing it, its easy enough to fix of;
- Copy / paste the mdx into MdxLab.
- Remove any lines containing: PROPERTIES [Measure].[Measure].[MEMBER_NAME]
- Reset the cube / view (so it doesn’t contain any aliases of any dimensions & just takes the MDX literally)
- Paste the updated MDX back in.
- Save the view
Update:
I’ve also replicated the issue with new views not just old native views.
Creating a view either in Arc or Pafe that contains mdx on the rows / columns that is saved as a native view generates the same properties statement & errors in Arc.
In this case the error occurs even when the .vue file doesn’t contain “MEMBER_NAME” but happens when the native view definition refers directly to a subset.
7,DimensionName
6,SubsetName
If you go into the view, add & remove an alias it will then change the native definition to refer to the mdx instead.
7,DimensionName
270,0
274,
275,239
{[Measure].[Measure].[Measure1], [Measure].[Measure].[Measure2]}
281,0
I think this means that there is a problem with how ARC is reading / translating native views.