Skip to main content

Hello

we are actually doing a migration dryrun from ifs v8 to ifs cloud 24r1
we got issue with projections acp deployment.
We successfully imported the ACP, but we can not publish our custom projections.
We got the following error : invalid or missing procedure, function, or package name
 


Debugging the database package workflow leads me to this :
CUSTOM_PROJECTION_UTIL_API.Generate_And_Deploy_Projection___ try to generate and deploy projection.

It calls a method to generate the projection header based on the projection object from custom_projection_tab which not exists in it.
It result in a package header without lu name, and it must be the reason of the failure.

But how can I get the projection registered in custom_projection_tab as I perform an import and not a creation.

I had not this issue merging from dev env to cfg env.

The acp come from cfg env and we deploy it into a production environment (dry run).

Any idea ?


​​​​​​​

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

Terms & ConditionsCookie settingsAccessibility statement