Existing custom sub-objects that are API enabled through the UI can not be found on Blueprint Modules

Document ID : KB000123020
Last Modified Date : 30/01/2019
Show Technical Document Details
Issue:
STEPS TO REPRODUCE 
1. Go to Administration > Studio > Objects
2. Create a new object Sub1
   This is a subobject of the master project object
3. Check the API Enabled checkbox
4. Save the object
5. Create a new object Sub2
   This is a subobject of the master project object
6. Do not check the API Enabled checkbox
7. Save the object
8. Check the API Enabled checkbox
9. Save the object
10. Login to the new UX
11. Go to Administration > Blueprints
12. Open an existing blueprint
13. Go to Modules

Expected result: Both Sub1 and Sub2 subobjects are available to be added as modules
Actual result: Only Sub1 is available. The existing subobject that has been API enabled through the UI is not available for Blueprint Modules
Cause:
This is caused by DE45950 
Resolution:
This is now fixed within 15.5.1.1 and 15.6
Workaround (for 15.5.0 or 15.5.1): API enable the subobject via XOG
 
Additional Information:
XOG xml sample to API enable an object:

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_contentPack.xsd"> 
<Header action="write" externalSource="NIKU" objectType="contentPack" version="15.5.1.1"/> 
<contentPack update="true"> 
<objects> 
<object code="Sub2" copyEnabled="true" apiEnabled="true" pageLayoutAttribute="page_layout" parentObjectCode="project" raiseEvents="false" source="customer" update="true"> 
<nls languageCode="en" name="Sub2"/> 
</object> 
</objects> 
</contentPack> 
</NikuDataBus>