As a general rule, we create custom attributes at the Investment level for shared attributes that will be used at the Idea and Project. Especially those that will be pulled into the Portfolio. However, it appears that those created at the investment level are unable to be enabled for the Rest API's and therefore unable to be setup to be pulled in as custom attributes for the new Blueprint option in 15.3. However, if configured in separate objects such as program manager in the idea and project, the data would transfer but show up as 2 columns in the portfolio as Program Manager (Idea) and Program Manager (Project). Can you force the API definition into the project on something that is in the odf_ca_inv table or are we now forced to decide whether or not the attribute should live in the Blueprint or in the portfolio? Thoughts? Or am I off base in these assumptions?