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

KB37583: "Invalid procedure call or argument" error message appears when clicking on an attribute relationship on MicroStrategy Developer 9.x and 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


"Invalid procedure call or argument" error message appears when clicking on an attribute relationship on MicroStrategy Developer 9.x and 10.x

SYMPTOM:
 
When a user clicks on an attribute relationship on Strategy Developer 9.x and 10.x, the following error is thrown:
 
Sample Code/Error
Invalid procedure call or argument
  
CAUSE:
 
This error is thrown as a result of a data modeling inconsistency which happens when an attribute relationship is defined through a table which doesn't support all components of a compound ID attribute form. An attribute relationship should always be defined through a table that is mapped as the source table of all compoments of the attribute's ID attribute form.
 
The following steps describe how to reproduce this data modeling inconsistency in any Strategy metadata:
 
1. Create an attribute with its ID form mapped to TableA. Create an attribute relationship with another attribute called RelAtt through TableA;
2. Create a copy of the attribute created in (1);
3. Create a new attribute form for the attribute created in (2) mapped to TableB;
4. Select the ID form of the attribute created in step (2) and group it with the attribute form created in step (3).
 
Strategy Desktop will allow users to save and close the new attribute, but it is now in an incorrect state because it has a relationship to attribute RelAtt through a table that is not supported by both elements of the compound ID attribute form.
 
ACTION:
When creating an attribute with a compound ID attribute form, users should ensure that attribute relationships are always defined through a tabls that are mapped as the source table of all compoments of the attribute's ID attribute form.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 6, 2017

Last Updated:

June 6, 2017