Custom Projection not publishable

Hi ​@REOGIRARD,

When you import an ACP (Application Configuration Package), it doesn’t automatically register custom projections in custom_projection_tab. This registration typically occurs during creation, not import. So, while the ACP brings in the projection definitions, the system doesn’t recognize them as deployable because they’re not properly registered.

You may need to manually insert the projection metadata into custom_projection_tab. This ensures that the deployment utility can locate and process the projection correctly. However, this should be done cautiously and ideally with guidance from IFS documentation or support.

Ensure that your custom projections have all required dependencies defined. Missing LU names or incorrect component references in deploy.ini or solutionset.yaml can cause deployment failures. Refer to IFS Cloud 24R1 - new Custom Component | IFS Community for more information on this.

Thank you for your answer ​@ashen_malaka_ranasinghe 
The thing is we are not using the development tools.
We trying to use ifs personalization tools to remove some specific developments from IFS8, it works perfectly on our dev env.
These projections not publishable are projections made with IFS Cloud app.
We created an entity, we created a custom projection to link actions for exemple.
From 2 dev environments we could successfully import these, but on our dry run prod environment we fall on this issue.
I am not confident manipulating ifs system tables as I don’t know the whole process of projection integration.
We inspected the cache system and packages generation made by IFS but this is a huge part and understand the process from thousands lines of plsql is a real challenge in my opinion

So we took time to understand what’s going on and if you move your projection to another package, it will only move the “projection configuration” and not the “custom projection” which is not visible in the ACP, but it’s a linked item.

We found it checking APP_CONFIG_PACKAGE_ITEM, package_id field is different for the 2 items when you do the manipulation.

How to reproduce : 

You have ACP A and ACP B. Both empty
You add a projection into ACP A (a projection which never been in ACP)
You remove projection from ACP A without deleting ACP A, and you insert the projection into ACP B.

If you extract then ACP B you’ll get only “projection configuration”.
If you go back on your ACP A and try to extract it you will get the “custom projection” file but not the “projection configuration” (which is the item you manipulated, as “custom projection” doesn’t exists as item, or is not visible on the web app).

This is a bug on 24R1.

Is it fixed on a later SU / Release ?