KB10715: When editing attributes, no attribute forms are displayed even though the attribute works in a report on MicroStrategy Developer 9.4.x-10.x

SYMPTOM:
A user edits an attribute and notices that the attribute forms are missing.  In particular the attribute ID forms are gone.  Placing the attribute on a report runs successfully and the SQL is correct; however, users cannot remove the linked attribute forms from the attribute object.
 
CAUSE:
This issue occurs because the ID form has become hidden and is not visible to users even though users have the "Display Hidden Objects" preference enabled through Strategy Developer Preferences > Browsing option.  Users must take note of Form manipulations that led to this especiallly if the condition appears to happen suddenly.
 
ACTION:
To make the ID form object visible, perform the following steps:

1. Close Strategy Developer and edit the registry by going to Start > Run > "regedit."
2. Navigate to HKEY_CURRENT_USER\Software\MicroStrategy\DSS Agent\DSS Agent. Double-click on the key "ShowInvisibleObjects" and change this from "No" to "Yes."
3. Close the registry and launch Strategy Developer.
4. Ensure that the hidden objects are visible by going into the top menu options under Tools > Preferences.
5. Click the Browsing Options button and check the box to "Display hidden objects" and click OK.
   Now, when they expand the project, users should see a hidden folder called "System Objects."
   
6. Open the System Objects folder and go to the subfolder "Form Categories." View the elements in this folder and right-click on the ID object to go to Properties.
7. Uncheck the box in the bottom of the properties window to make the ID form un-hidden. Click OK.
8. Close Strategy Developer.
9. Go back to the regedit and change the registry key "ShowInvisibleObjects" back from "Yes" to "No." Close the registry.

Now, after launching Strategy Developer, the attribute forms of the type ID should be visible.
 
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of MicroSoft Windows NT. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using MicroSoft Windows NT, the user should backup the registry and/ or update an Emergency Repair Disk prior to alterations.