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

"Attribute form specified with an attribute was not found among the attribute's forms" Error Appears When Validating a New Derived Attribute in a Dossier


Vanessa Munoz

Cloud Support Expert I • MicroStrategy


This article describes an issue that occurs when validating a new derived attribute definition in Web 2019.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Symptom


In a project that has Internationalization enabled, when a user tries to create a new derived attribute in a dossier in Web, an error appears when clicking Validate:

ka0PW0000001JX7YAM_0EM2R000000h7HY.jpeg

The following error can be found in the DSSErrors.log file: "Attribute form specified with an attribute was not found among the attribute's forms".

Steps to Reproduce


These are the steps to reproduce the issue:

  • Create a new project with languages set as: English (default) and German.
  • Create an attribute that has several attribute forms with German and English translations.
  • Update Schema.
  • In Web, log in and change the preferred language for the user to German.
  • Create a new dossier and add the newly created attribute.
  • Create a derived attribute as follows: <new_attribute(german name)>@German Form Name>
ka0PW0000001JX7YAM_0EM2R000000h7I2.jpeg
  • Note that when typing @, the auto-populated suggestions shown display in German.
  • If the English form name is added instead, the derived attribute formula validates. 

Cause


This is a known issue in Web 2019 that is currently under investigation. 

Action


Contact Strategy Technical Support for an update on the status of this issue. 

Workaround


This issue does not occur when using the default language attribute form name instead.
This issue has been logged as TS316626 and DE136836. KB483306


Comment

0 comments

Details

Knowledge Article

Published:

May 22, 2019

Last Updated:

March 21, 2024