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

Document ID : KB000123020
Last Modified Date : 01/04/2019
Show Technical Document Details
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
This is caused by DE45950 
This is now fixed within and 15.6.
There is not workaround.

Note: If the user created the object and forgot to check the API Enabled checkbox, the user can update the object via XOG to enable API (for 15.5.0 or 15.5.1).
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=""/> 
<contentPack update="true"> 
<object code="Sub2" copyEnabled="true" apiEnabled="true" pageLayoutAttribute="page_layout" parentObjectCode="project" raiseEvents="false" source="customer" update="true"> 
<nls languageCode="en" name="Sub2"/>