Default Cube Deployment: Perspective not found

(0) Share

Report

Posted on by Community Member

I have created the custom cube under perspective and deployed the Dynamics AX initial database. I was about to modify the custom cube but I have wrongly deleted the custom cube directly from AOT perspective. Now I am trying to deploy the default cubes its showing the error message as “Perspective not found.” Please let me know if you have any resolution to resolve this issue.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Community Member on at

Like (0)

Report

RE: Default Cube Deployment: Perspective not found

Hi Michael,

I am running the Default Cube Update through SQL Server Analysis Services Project Wizard, after completing if i open the Dynamics Initial Project or Database, Roles are empty.

Was this reply helpful? Yes No
MichaelWC 136 on at

Like (0)

Report

RE: Default Cube Deployment: Perspective not found

Not sure I understand, are you missing the default roles from your project or the default cubes?

There was a trick you could do with AX2009 and run the default cubes creation wizard manually through SQL management studio as an XML query. Let me check the 2012 install media and see if it still exists. Perhaps others may know if this is still the case with 2012??

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Default Cube Deployment: Perspective not found

Hi Michael,

I have opened Dynamics Ax initial project through BIDS tool. Cubes and Dimension are available. But Default Analysis Services roles are missing. Please let me know how to get the default Roles.

Was this reply helpful? Yes No
MichaelWC 136 on at

Like (0)

Report

RE: Default Cube Deployment: Perspective not found

Hello Baska,

Not sure if you are trying this in AOT, if so, use SQL business intelligence development studio. Try processing the dimension on its own with Ignore Errors. You will probably need to examine the processed dimension and look for the duplicate entry if there is one. Check the data source of the dimension which may be a query and validate the required unique fields are present. If not, add them and reprocess. If you reprocess without ignore errors and the dimension fails due to key integrity, repeat the above steps using the error output to tell you where the violation is.

Please post your results.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Default Cube Deployment: Perspective not found

Thanks for Reply.

Issue is when I am deploying only my cube, it is working fine. But when I deploying with Standard cubes. I am getting below error message.

The object \\Data Dictionary\Views\BankChequePaymTransCube does not contain all of the fields that are required to build a unique index. The resulting dimension may cause duplicate key processing errors. To avoid the errors, make sure that a perspective includes all required fields.

Was this reply helpful? Yes No
Lance [MSFT] on at

Like (0)

Report

RE: Default Cube Deployment: Perspective not found

I'm not certain what's happening here, but what usually happens on the deploy project stage is that before the project is deployed, the wizard needs to add a filter to the data source view to filter the data by a single partition. To get the list of dsv queries it needs to filter it gets the list of cubes in the project and then tries to find a matching perspective for each of them.

If you previously updated the default project and it now contains a cube for which no perspective now exists, then perhaps you could removing the .cube file for that missing perspective from the analysis services project to see if it gets past the problem.

Another thing to check is to verify the property Usage on all the perspectives for cubes in the project is set to OLAP, otherwise the perspective is set as not valid for use with ssas, so the wizard won't consider it a valid match.

If you only have one AX partition, which is often the case, then you don't actually need this filter. If this is the case, instead of deploying through the wizard you could deploy the project through sql data tools. If there's some problem with the analysis services project sql data tools tends to give clearer error messages than AX.

Afterword deploying the project, there is a pair of tables in AX that hold the settings of what server to connect to and what database to connect to that may need to be updated. BIAnalysisServer and BIAnalysisServicesDatabase are the table names. Make sure there is a record in BIAnalysisServer that holds the name of the server. If you previously deployed the project, that record is probably already present. Also make sure there is a record in BIAnalysisServicesDatabase which is linked to the server record and which holds the name of the analysis services database. The IsDefault field should be true on both records.

If none of this works, I'd call tech support for this, as somebody there could likely debug it with you.

Hope this helps

-- Lance

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: SSAS Cube - Default Cube Deployment Issue

No

Was this reply helpful? Yes No