EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB317835: Changes to the option "Allow joins across datasets based on unrelated common attributes" in dashboard properties cannot be saved in MicroStrategy Web 10.4


Community Admin

• Strategy


This document shows one issue that changes to the option "Allow joins across datasets based on unrelated common attributes" in dashboard properties cannot be saved in MicroStrategy Web 10.4. One possible cause is the definition of the system object "VLDB Select" is unexpected. The resolution is to migrate this object from a working metadata to the metadata in problem with Object Manager package.

SUMMARY:
This document shows one issue that changes to the option "Allow joins across datasets based on unrelated common attributes" in dashboard properties cannot be saved in Strategy Web 10.4. One possible cause is the definition of the system object "VLDB Select" is unexpected. The resolution is to migrate this object from a working metadata to the metadata in problem with Object Manager package.
 
SYMPTOM:
Changing the option "Allow joins across datasets based on unrelated common attributes" in dashboard properties cannot be saved in Strategy Web 10.4. 
 

ka04W000000OeMBQA0_0EM4400000025QK.jpeg

DSSErrors.log contains the following error:


Item "Join Across Datasets" is not found

 
CAUSE:
One possible cause is the definition of the system object "VLDB Select" is unexpected.
 
ACTION:
In order to track down the cause of this behavior, customers encountering this issue should make note of changes on configuration objects, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.
 
WORKAROUND:
Migrate system object "VLDB Select" from metadata of working environment or Strategy Tutorial metadata by following steps below:
1. In Object Manager, connect to project source which connects to metadata of the working environment or Strategy Tutorial metadata.
2. Create an object package.
3. Add one document into this package.
4. Click on "Add all used dependencies". All used dependencies including "VLDB Select" are added into the package.
5. Remove all other objects but keep only "VLDB Select" in the package. Change conflict resolution to "Force Replace". 
7. Click on proceed to generate the package.
6. Backup metadata in problem and then import this package.


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017