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

KB34945: "Type mismatch" error message appears when moving an attribute into the page-by section of a report in MicroStrategy Developer 9.4.x - 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


In MicroStrategy Developer 9.4.x - 10.x, "Type mismatch" error message appears when a user is attempting to place an attribute in the page-by section of a report due to an incorrect column alias set up at the attribute level.

SYMPTOM:
In Strategy Developer 9.4.x - 10.x, "Type mismatch" error message appears when a user is attempting to place an attribute in the page-by section of a report.

ka02R000000kcTPQAY_0EM440000002Dud.png

 


Type Mismatch

 
STEPS TO REPRODUCE:
Execute the following steps in the Strategy Tutorial project
1.     Create an attribute 'Order_Ship_Date' using the following expression as its DESC form
        

ka02R000000kcTPQAY_0EM440000002Dub.png


ApplySimple("#0||' - '||#1", [ORDER_DATE], [SHIP_DATE])

2.     Create a report with attribute 'Order_Ship_Date'
3.     Execute the report. The data returns correctly.
       

ka02R000000kcTPQAY_0EM440000002Duc.png

        When attempting to move the attribute into the page-by section, the following error occurs:
       

ka02R000000kcTPQAY_0EM440000002Dua.png

 
Note: The attribute expression used in the above example is specific to an Oracle database.
  
CAUSE:
The attribute form has an incorrect column alias defined. In the above example, the DESC form is designed to concatenate the Order_Date and Ship_Date as a string. However, its column alias is defined with the 'TimeStamp' datatype which causes the type mismatch.
ACTION:
Open the attribute editor and modify the DESC form. Select the column alias tab and create a new column alias. Specify the NVarChar data type as shown in the screenshot below
Save the attribute and update schema. User will now be able to move the attribute to page-by.


Comment

0 comments

Details

Knowledge Article

Published:

April 18, 2017

Last Updated:

April 18, 2017